Fund what people build. Build what people fund.
A focused architecture for connecting public economic coordination on OrangeCat with supervised agent execution on FleetCrown.
01
Two seamless siblings
OrangeCat is the public economic layer: the place where an entity is explained, shared, supported, offered, or joined. FleetCrown is the production layer: the place where Loki plans work and supervised agents help turn the entity into something real.
They remain separate products because public economic coordination and local agent execution have different security boundaries. They should nevertheless feel like one journey: fund what is being built, and build what people choose to fund.
02
Bitcoin first
The first settlement rail is Bitcoin. Lightning gives ordinary users fast, inexpensive payments; on-chain Bitcoin supports larger or slower transfers. Both are non-custodial and can be independently verified.
Fiat is visible to banks but does not give the public a shared ledger. Privacy coins intentionally hide transfers from public view. Both may become useful later, but neither belongs in the first auditable fund-to-build loop.
03
Entities before special cases
A person, project, club, cause, product, service, or event is an entity with a public story, an owner, links, and optional Bitcoin support. The system should not need a special workflow for every kind of ambition.
When someone creates a club, for example, OrangeCat can suggest taking it to FleetCrown. Loki can propose a business plan, financial model, location research, permits research, a website, staffing, and launch communications. The owner approves the plan and controls every real-world action.
04
Accountability without premature automation
Confirmed Bitcoin contributes to the public ledger. Signed handoffs bind an OrangeCat entity to the owner who sends it to FleetCrown. Typed links preserve where a project came from and where it can be funded.
Funding does not automatically unleash agents. Settlement, project planning, and agent execution are separate events with explicit approval boundaries. This makes the first version understandable and reversible while leaving room for later escrow or milestone contracts.