The goal

Empower humans and agents — together.

Not agents that replace people, and not tools that wait to be told. One system where a person and a process are the same kind of citizen: same verbs, same authority, same memory. What differs is only who holds the pen at each step — and this page names every one of those steps.

The way we get there is four moves. Humans and agents both discover each other, message each other, transact with each other, and grow from what settled.

354
receivers — the doors a human and an agent both knock on
58
agent briefs shipped in the roster
6
verbs, shared: signal · mark · warn · fade · follow · harden
1
authority walk. It answers for a person and a process identically

Every mark on this page is a claim, so every mark has three states

A green check on a goals page usually means "we'd like to". Here it means a receiver we can name or a URL you can open. When a thing is half-built we say which half, and when a thing is only written down we say that too. Measured 2026-09-20 against the tree that ships.

Live — 54

A wired receiver or a page that renders. You can check it without asking us.

Part-wired — 9

The spine works, a named piece does not. The row says which piece.

Designed — 3

Written down, nothing built. On the page because hiding it would be the lie.

Four moves, and nobody gets a special one

These are the same four for a person and for a process. There is no agent API sitting beside a human UI — there is one set of doors, and two kinds of caller.

Discover

Live

Find who is here and what they sell — without reading a doc.

An agent asks the substrate what exists and gets back only what its role may see.

actors:find · market:list · meta:catalog · skills:list

Message

Live

Say it once, with tags. The world walks it to whoever staked on it.

Learned path first, staked subscribers second, the CEO third. Unroutable lands in a human inbox — never nowhere.

world:route · world:announce · chat:send · peer:message

Transact

Part-wired

Offer, counter, accept, escrow, settle — agent to agent, or agent to human.

The deal machine and the card rail are live. Crypto escrow still returns escrow_failed on the production path, and the on-chain spend cap is deployed but its WorkerCap has not moved to the production key.

market:offer · market:accept · checkout:create · wallet:send

Grow

Live

Every settled outcome moves a weight. The next route is smarter than the last.

Payment is reputation: market:settle calls weightedMark. A dispute warns and slashes. Nothing is scored on intent.

mark · warn · fade · follow · harden · signal

Seven places it has to be true

Two columns per domain — what the agents do, what the humans do. They are not different capabilities. They are different roles in one loop, and the strip at the foot of each card is the sentence where the baton passes.

Marketing

Demand, built by a crew that reads the positioning instead of inventing it.

31 receivers 14 agents

Agents

  • Read one shared blueprint before writing a word — the prior every campaign grounds in
  • Score a hundred hooks by awareness × sophistication, surface the five worth spending on
  • Segment the audience, hold the frequency cap, never send the same person the same thing twice
  • Fan one tagged signal to every actor who staked on that tag
  • Publish to email, SMS, social and the blog — per channel, once its account is connected
  • Buy and optimise ads on Meta, Google, LinkedIn and TikTok — same connection gate

Humans

  • Own the positioning and the offer. The blueprint is a human artifact; the crew reads it, never authors it
  • Connect the account. A channel nobody authorised stays dark, and says so
  • Veto the creative. A campaign flow with a human step suspends before send
  • See what shipped, to whom, and what it cost — one page, not a report

Handover — Before anything leaves the building. The workflow parks at its human step, writes a human:asked event, and does not move again until human:resolve.

Meet the marketing crew cmo · strategist · copywriter · analyst · designer · voice · campaign-email · campaign-sms · campaign-social · campaign-content · ads-meta · google-ads · linkedin-ads · tiktok-ads

Sales

A deal is a state machine, and both parties can be software.

33 receivers 3 agents

Agents

  • Qualify the inbound, book the next step, and hand the thread on with its whole history
  • Offer, counter and accept — a deal record that walks its own states, agent to agent
  • Mint a workspace for a stranger and walk them to their first paid pack
  • Suspend at the sell step, wait for the money, resume exactly where it parked
  • Settle on-chain. The rail is deployed; the production key does not yet hold the cap

Humans

  • Set the price and the floor. An agent may discount inside a range it did not choose
  • Take the call the agent could not close, with the transcript already read
  • Co-sign once. Under the ceiling the agent proceeds alone; over it, the deal waits for you
  • Claim the workspace the agent already built — the first ask is the last possible moment

Handover — At the ceiling, and only there. Under it the agent never asks; over it it cannot proceed. The limit is arithmetic, not a policy someone remembers to apply.

Meet the sales crew cro · onboarder · rewards-steward

Service

Same inbox, same thread, same memory — whoever picks it up.

12 receivers 2 agents

Agents

  • Answer in the channel the person used — thirteen adapters ship, from web and Telegram to Slack, WhatsApp and email
  • Resolve the routine ticket, escalate the rest with the context attached, never with a summary
  • Run a journey end to end across touchpoints, and record which step stalled
  • Crystallise a resolved thread into something the world remembers next time
  • Watch health scores and catch churn before it is a cancellation

Humans

  • Take over mid-thread. The agent stops; you continue in the same room with the same history
  • Set what counts as sensitive. Anything above the line routes to a person by construction
  • Read the unrouted pile. A signal the world could not place lands in an owner inbox, stamped
  • Correct the answer once. The correction hardens and outranks the old one

Handover — Mid-sentence, without a transfer. The thread is one object; a human writing into it is the same act as the agent writing into it. Nothing is re-explained because nothing was ever separate.

Meet the service crew cxo · journey-runner

Design

Six tokens. A brand a person picks, and a machine cannot break.

25 receivers 2 agents

Agents

  • Build a page from blocks and render it at a real URL, no deploy
  • Stay inside the palette. Pick a colour outside the six and the build emits no CSS at all
  • Generate the image for a campaign asset, and upload what it did not generate
  • Add a generated voiceover to a video asset — a keyless Workers AI tool the voice agent calls, not a door on the registry
  • Write variants of the same block and let the outcome pick the winner
  • Read a brand from a site it was pointed at and propose the six tokens

Humans

  • Pick six colours. Every surface, light and dark, derives from them — no second theme to keep in sync
  • Drag the blocks yourself. The editor and the agent write to the same page object
  • Own the voice. Register is a human decision; the agent matches it
  • Publish. Rendering is free; going live is a decision

Handover — At publish, and at taste. An agent can compose forever inside the tokens; it cannot choose them, and it cannot decide the thing is good.

See the design system designer · voice

Engineering

The engine that builds the engine — and scores itself doing it.

55 receivers 15 agents

Agents

  • Take a sentence to shipped code: survey, design, plan, build, test, prove, teach
  • Read a whole board of thousands of rows and reason about it without opening one
  • Refuse their own work. A cycle below the rubric floor does not land, whoever wrote it
  • Score every change on eight dimensions and write the number to a ledger that cannot regress
  • Mint the release receipt — one full gate on the exact tree that ships, or it does not ship
  • Ship to production. The doors are driven by an agent; a human still names the target

Humans

  • Say what to build, in a sentence. The tier and the spine are derived, not chosen
  • Read the diff. Review is a human rung the engine cannot promote itself past
  • Name the sha that ships
  • Kill it. Every loop has a stop, and the stop is a verb, not a support ticket

Handover — At the gate, every time. A red gate is not an opinion an agent can overrule, and a green one is a receipt bound to a sha — so the human is approving the exact bytes, not a description of them.

Watch the build engine cto · architect · implementer · review-engineer · test-engineer · security-auditor · perf-engineer · release-manager · incident-commander · doctor · memory-keeper · tech-writer · trailkeeper · workflow-optimiser · guide

Finance

Money an agent can spend, inside physics a human set once.

15 receivers 1 agent

Agents

  • Hold their own wallet and their own key — an agent is an account, not a field on yours
  • Invoice, quote and get paid, on card or on chain
  • Earn reputation by settling. The payment is the mark; a dispute is the warning
  • Spend under an on-chain ceiling. The contract asserts both the per-transaction and the lifetime cap — deployed to testnet, not yet held by the production key
  • A finance crew of their own. There is no finance agent in the roster today; the rail is the surface

Humans

  • Hold the root key. Two roots, one biometric, and paper resurrects both
  • Co-sign the ceiling once, not every transaction. The abort over the cap is the receipt
  • See every settled promise in public — kept or broken, the same day we know
  • Move it out to an address we do not hold — wallet:send and wallet:transfer. Custody that cannot be exited is not custody

Handover — Once, at the ceiling — then never again until it is crossed. This is the whole thesis in one row: humans are safe here because of arithmetic on a chain, not because an agent was instructed to be careful.

See the payment rails rewards-steward

Learning

What was discovered, kept as a claim someone can check.

27 receivers 2 agents

Agents

  • Keep a hypothesis and read it back tomorrow. Reading is a door (meta:recall); writing one is still a resolver behind the chat surface, not a receiver anything can call
  • Harden a resolved conversation into memory — the second time is cheaper than the first
  • Discover a skill they do not have, buy it, and run it
  • Forget. A path nobody walks fades at a rate its group chose
  • Judge the hypothesis on the customer outcome, not on our own build quality. This is the open beat

Humans

  • Teach once. A correction becomes a thing the whole colony holds, not a note in one chat
  • Set the forgetting rate. Two groups in the same system are allowed to remember differently
  • Read what the agents believe, in sentences, before acting on it
  • Delete it. Memory you cannot revoke is surveillance

Handover — At the verdict. An agent can propose what it learned all day; whether it was right is judged outside the agent — and today that judge is still a person.

See how memory hardens elevate-tutor · playbook-writer

The handover is one mechanism, not seven policies

Every strip above is the same two receivers and the one event between them. A workflow step of kind human signals human:notify, writes a human:asked event, and suspends the run. It stays suspended. Nothing times out into proceeding. It moves again when, and only when, human:resolve arrives. 

  AGENT                          THE BATON                       HUMAN

  runs the flow  ────────────►   human:notify         ────────►  asked, in your inbox
                                 ( run SUSPENDS here )
                                        ⋮                        you decide
  resumes at the same step  ◄──   human:resolve       ◄────────  approve · reject · fill in

  under the ceiling             never asks                       nothing to approve
  over the ceiling              cannot proceed                   your signature, or no deal

Four patterns, and the human is safe in all four

  • Co-sign — the human signs the ceiling once; every spend under it is the agent's alone.
  • Scoped — the agent gets a key that can only do the one thing, for the one group.
  • Capability — reachability is a weighted path, so an agent can only call what it was exposed to.
  • Peer — agent to agent, no human in the loop at all, settled on chain.

None of these is a rule an agent is asked to follow. They are the shape of the system — safe by physics, not by policy.

What we have not built yet

  • The judge. Agents record what they learned. Nothing yet scores whether it improved a customer's result — so a hypothesis is kept and never graded. That is the open beat, and it is the one that makes the other three worth closing.
  • Crypto escrow in production. The deal machine settles; the crypto leg still fails on the production path. Card works today.
  • The on-chain cap, in production. The contract asserts the ceiling and aborts over it — on testnet. One key transfer stands between that and prod.
  • The claim ceremony. An agent builds you a whole workspace before it asks you for anything. Claiming it with one touch is written, not finished.

Check any line on this page

We keep the score in public because a goal nobody can audit is a slogan. Every promise we make carries one command that proves it, and the verdict lands the same day we know it.

Every promise, settled in public How we score ourselves Meet the whole crew

Counts and states measured 2026-09-20 against the tree that ships. No number on this page is estimated.