MCP substrate and identity

The substrate is the physics engine. Agents work on it. They do not live inside a model call made by the server.

That sentence is load-bearing. If the server starts calling a model, the company becomes another chat with extra steps. Identity, authority, and evidence would sit in the same place as generation. The audit trail would be a story the model told about itself.

So the split is sharp: the server holds identity, authority, budgets, evidence, and audit. It advertises eight natural forces as physics. Hosts call in as clients. They ask for context they are allowed to see. They propose writes. The substrate records what happened.

What the substrate holds

• Identity. Who this principal is, which cell it belongs to, and whether that identity is still valid.
• Authority. What the principal may read, draft, or request. What it may never do.
• Budgets. Tokens, dollars, attention, and try units the cell is allowed to burn. A request past the budget fails in the open.
• Evidence. Artifacts the company will treat as real: commitments, reviews, kill decisions, rejected writes. Fitness counts and activity counts stay separate.
• Audit. A record another operator can read later without reconstructing a chat.
• Forces. Live protocol.describe advertises Bound, Sense, Act, Transform, Maintain, Defend, Select, and Continue as physics, not seats.

Closed beta is live on personal DataSaa infrastructure: one MCP HTTP service, exact-match identity, try-unit founder budgets. That is not a commercial company and not a first offer.

Sense does not spend like Act

Sense work of kind sense_market observes the world into the shared medium: lists inside the Bound frame, enrich, packets. It does not debit try spend. Act work kinds change the world — on the covering cell, outbound from Sense-ready packets — and debit tries on complete or fail. The founder still signs sends.

That split is encoded, not a style guide. Sense researches. Act spends. A host that burns Sense as if it were Act is misusing the engine. Transform then decides what metabolized into fitness and what stayed activity. Select reads fitness. Packets sent are still not fitness.

The tick is Maintain and Continue

A tick exists in the image. It is not cron'd on the HTTP service. It is not reflex.

Maintain advances expired leases and overdue open work. Continue advances due closeout and the evaluation work that closeout needs. The tick does not sit a chatbot in a chair. It keeps the physics from stalling.

The server never calls a model

Generation happens at the host. The substrate answers with facts, permissions, and records. If an agent needs a completion, it uses its own model path. The company memory does not depend on the server inventing one.

This keeps two failure modes apart. A bad generation can be rejected. A bad permission should not be possible to talk into existence.

What stays private

The implementation lives in a private repo. This site will not pretend the MCP is open-source. Public notes will say what the layer is for, what it refuses, and what a dispatch learned. They will not publish credentials, customer records, or internal adapter details.

What this is not

This is not a company brain product for sale. It is not Claude Tag, Grok Bot, or a hosted "team GPT." Those are interfaces people already use. The substrate is the durable physics underneath a market of cells.

The forces page names the persistent laws and the optional effectors. The loops page names when writes get reviewed. What is not being built yet names the adapters that stay off the board.