Case study · experimental system

Money Hunter

An experimental autonomous system for qualifying, routing, and fulfilling small digital work under The Criners LLC. The public face is the storefront. This page is about architecture and operating discipline — not a claim that the system has collected product revenue.

Public project site

What it is

Money Hunter is a single-host orchestration layer: intake of lawful, public-data jobs; workers that can qualify and fulfill; dashboards for an operator on the same machine or LAN; integrations that are granted, not dumped into every process.

It is Company #1 in the current laboratory. Packet Press is Company #2. They are not the same brand and not the same grants. Money Hunter is not a Company OS tenant; the OS was designed so that laboratory does not get overwritten by a restore.

Architecture (public facts only)

Workers and qualification. Jobs are filtered before anyone spends time. Acceptable work is the kind already described on the public storefront (public data, public pages, structured files) — not harvest, not login-walled systems, not physical gigs.
Automation. Recurring loops exist so idle time can look for the next lawful unit of work. That is orchestration, not a promise of cash.
Dashboards. Operator UI is for the owner on loopback or LAN. It is not a WAN product. This site will not publish dashboard URLs, ports, or tokens.
Integrations. Marketplace, payments, and mail are treated as dangerous shared credentials. Company OS later encoded that lesson as blocked prefixes and allowlisted name lookup. Money Hunter keeps those accounts off Packet Press.
Safeguards. Spend and identity actions stay owner-gated. Superteam and live bug-bounty testing are on hold or stopped by owner policy. No captcha bypass, no KYC theater, no retail dropship without stock.

Lessons learned

A scoreboard that can invent cash will invent cash. Simulated funnel numbers are not collected dollars.
One host, two businesses, one .env is how you mail the wrong client. Isolation has to be a directory and a grant map, not a comment in a prompt.
Dashboards that bind the public internet become the product whether you meant them to or not. Don’t.
The storefront can be live while the orchestration layer is still experimental. Those are different truths.

No collected-revenue figure is published here for Money Hunter or Company OS. If a number is not in the résumé (historical employment) or a public scoreboard we are willing to stand behind, it is omitted.