Skip to main content
Mao Nakamoto

One stack, three pillars

Fund what is being built, build what people choose to fund, and govern both in the open. Three products, deliberately kept apart — and bound where it counts.

OrangeCatyou are here

Economy

The public economic layer: where a person, project, group, product, or service is explained, shared, supported, offered, or joined — and paid in Bitcoin.

Public by design. Everything here is a page someone can read, share, and settle against without an account.

FleetCrown

Engineering

The production layer: where Loki plans the work and supervised agent fleets help turn a funded intention into a working system.

Execution stays behind an approval boundary. Funding never dispatches an agent — the owner approves each plan and each real-world action.

Visit FleetCrown

Solon

Governance

The governance layer: where platform-level rules are proposed, voted on with Bitcoin-signed messages, and published as decision documents anyone can re-verify.

It decides, it does not execute. OrangeCat re-verifies every vote signature against its own pinned keys before a decision changes anything.

Visit Solon

What binds them

They stay separate products because public economic coordination, agent execution, and rule-making have different security boundaries. They are one stack because two of those boundaries are crossed by code you can inspect.

OrangeCat → FleetCrown

Signed build handoff

An owner can send a public OrangeCat entity to FleetCrown as a short-lived, signed build intent. The signature binds the handoff to the owner who approved it. Funding never dispatches an agent on its own — settlement, planning, and execution stay separate events.

Solon → OrangeCat

Verified, not trusted

The ceiling on what the Cat may spend changes only through a Bitcoin-signed Solon vote. OrangeCat re-verifies every signature against its own pinned keys, re-derives each signed message, and recomputes the tally before a policy activates. A Solon decision is evidence, not authority.

Check it yourself

Don't take this page's word for any of it. The governed state of the stack is published, versioned, and hashed.

Back a pillar

Each pillar can be supported on its own — or back the founder and follow everything being built across the stack.