Mao Nakamoto
@maonakamoto
Life OS + AI agent fleet command center — the capability layer of the two-product system (FleetCrown = capability, OrangeCat = economy). Multi-user SaaS: operators register projects, dispatch AI agents (Claude Code, Hermes, OpenClaw/Loki) from one dashboard, watch live PTY terminals, and govern runs (captain-mode: see + govern, human owns the references). Key surfaces: /control (dispatch), /terminal (live PTYs), /loki (chat + fleet RAG), /projects (dossiers, visitor-feedback inbox with one-click dispatch-fix + AI page review), /activity, /prompts, embeddable feedback widget (/widget.js) on customer sites. MUTUAL DOGFOOD WITH ORANGECAT: FleetCrown is OrangeCat's customer #1 — logs in via OC OIDC (users.orangecatActorId), publishes projects/dev-logs to OC's timeline (publish bus, source='fleetcrown'), mirrors /money subscriptions to OC services via @orangecat/sdk, raised investment as an OC entity, and its Bitcoin monetization rail (pricing → OC pay URL → HMAC entitlement webhook → oc_billing_grants → plan grant) is built and inert awaiting OC-side passes. OrangeCat is in turn FleetCrown's execution customer: OC's "Build it with FleetCrown" CTA hands funded projects to the fleet. Fiat (Stripe) is blocked until bitbaum AG incorporates, so OC's BTC rails are the only revenue path. Seam contract artifacts: vendor/orangecat-sdk tgz, entitlement webhook (fleetcrown-plan:<tier>/fleetcrown-days:<n> tags), docs/architecture/cross-product-identity-bridge.md (OC = identity SSOT; FC never builds profiles/walls/payments).
Bitcoin-native economic layer — the money/identity half of the two-product system (OrangeCat = economy, FleetCrown = capability). Platform for universal economic participation: actor-owned entities (projects, products, services, causes, wishlists, loans, investments, assets, groups, events), BTC/Lightning wallets + payment orchestration (NWC, LNURL, on-chain verify), public timeline (the wall), typed stakeholder graph, and "My Cat" — an advisory economic AI (proposes offers; deliberately does NOT execute work). PLATFORM SUBSTRATE: production OIDC identity provider (FleetCrown registered — "Login with OrangeCat"), ock_ integration keys, @orangecat/sdk (built for sibling products), versioned /api/v1 with OpenAPI, inbound publish bus whose only recognized source is 'fleetcrown', outbound webhooks. MUTUAL DOGFOOD WITH FLEETCROWN: OC records/prices/settles work but has NO executor — services, tasks, job postings, funded projects are records; execution is delegated to FleetCrown ("Build it with FleetCrown" CTA, in_house_dev stakeholder edge, revive-my-old-ride config: "OC markets it, FC executes it"). FC is OC's customer #1 (identity, publish, subscriptions mirror, investment raise). Entitlement bridge: BTC settlement of a product tagged fleetcrown-plan:<tier> + fleetcrown-days:<n> HMAC-notifies FC to grant a time-boxed plan. SEAM STATUS: OIDC live + witnessed; timeline ingest live; KNOWN BUG — v1 entity-create from bearer-token callers hits RLS 42501 (fix: service-role client like timeline ingest); FC pass products not yet minted; ORANGECAT_WEBHOOK_SECRET unset on both ends.
Refugee housing placement
AI specialists platform
AI data capture & analysis
AI-first ERP for Swiss SMEs
Internal fundraising dashboard
Admin platform — 30+ sections, 165 tables
Protocol-based governance layer
2026-07-29
The Visitor Is Part of the Fleet Now
FleetCrown's feedback widget turns a stranger's complaint into a deployed fix — one script tag on any of your sites, a per-project inbox, one-click dispatch to an agent, and a loop that closes itself: when the fix ships, the report resolves automatically and the visitor gets an email. This is the full tour of the shipped product, with real screenshots — the widget on a live customer site, the inbox holding real accessibility findings, the remote kill switch, and the daily digester that clusters noise into one approvable draft.
2026-07-28
A Working Tree Is a Lock
FleetCrown runs many AI-agent sessions at once, and for months they shared a single git checkout — so branches switched under live work, and an unrelated session's half-finished code could ride out to production on someone else's deploy. This is the full record of the fix: why a working tree is a mutual-exclusion resource, why the same tree must not also be the deploy artifact, the two isolations we built (per-session worktrees, a CI-owned deploy), the three latent bugs the first real deploy exposed, and an honest ledger of what the new machinery might cost us later.
2026-07-22
The Economy Remembers What You Have, Not What You Need
Every marketplace ever built indexes supply and lets demand evaporate in a search box. That asymmetry is a quiet bias toward the people who already have — and it lives, in most systems, in a single hardcoded list. This is what changed when we taught OrangeCat to remember need: discovery flips from pull to push, the person who wished for a thing is told when it exists, and an unmet need stops being a dead end and becomes a thing to build.
2026-07-22
A Fleet Outlives Its Ships
The agent market keeps asking which new worker kills the last one — is Hermes the OpenClaw killer, is Codex the Claude Code killer. The question is almost content-free, and the fact that it stays askable is the tell: the worker layer is converging on one substrate and commoditizing. This is a technical and philosophical account of what that means — what a worker actually is now, read closely through Nous Research's Hermes; the two things a single worker structurally cannot be, its own verifier and its own market; and why FleetCrown and OrangeCat are built on exactly those two things.