RhizProtocol / The network atlas
The Rhizomatic Context Protocol is how distinct people and organizations share one network without sharing one another’s authority. Plain language first; the precise reading is one click away on every term.
01 / Atlas
One network everybody participates in, without anybody losing control of their own part of it.
One connected map of people, organizations, and work, rather than a separate disconnected copy inside every product.
A single substrate of nodes and relationships that every Rhiz application reads and writes through the same primitives. Applications compose over it; they do not fork it.
Your part of the network stays yours. Shared infrastructure never means shared secrets.
A Context is the unit of authority and privacy. Membership, history, and permissions belong to it, and nothing crosses between Contexts implicitly. Organization identity, role, login, or a Context id never substitutes for authorization.
A person, organization, or agent the network can reason about.
The identity primitive. One node has one durable identifier across every surface, so the same person is not three records in three products.
A real connection between two nodes, with history behind it.
An edge carrying its own evidence and time. Relationships are derived from recorded interaction, not asserted by a form.
How much weight a claim or connection has earned, and on what basis.
A computed property over provenance and outcomes, always attributable to its sources and always correctable.
02 / Atlas
A goal enters, becomes a decision, becomes an action, and leaves a record.
Where someone enters the work: a page, a site, an invitation.
A public or semi-public surface bound to a Context, which turns arrival into a governed participant rather than an anonymous visitor.
What the network learns when someone arrives or asks.
The capture seam. Capture is evidence, not automatic truth: it records what was said and by whom, and never promotes itself to a stronger claim.
Something that happened and might matter.
An event on the spine, carrying its source and time, available for routing without yet implying a decision.
Getting the right thing to the right person or agent.
Ranking and dispatch under the Context's rules, producing a proposed next move with a named owner.
The move somebody actually makes.
An executed effect bound to the authority that permitted it. Consequential action requires the relevant approval gate; nothing acts on its own authority.
What actually changed in the world. Not a reply, not activity, not a dashboard number.
A verified result with evidence attached. Response and activity are explicitly not Outcomes, which is why the ledger stays small and honest.
03 / Atlas
The next move should begin with more context than the last one did.
What happened, kept connected to why it happened.
Durable state derived from recorded events, scoped to the Context that produced it and reconstructible from its sources.
What the network has learned that is reusable.
Patterns and structures compounded across permissioned Memory. Agents may learn from permissioned receipts; they may not reuse private Context without explicit authority.
Where a claim came from, always.
Every assertion carries its source, its author, and its time. A claim with no provenance is not promoted.
A record of what was done, readable after the fact.
Tamper-evident records of governed moves, inspectable by the participants and usable as the basis for correction.
04 / Atlas
Automation expands capacity. People keep authority, and mistakes stay fixable.
A person says yes before anything consequential happens.
An explicit gate on consequential effects, recorded with its approver. Agents research, route, draft, and monitor; they do not approve.
Getting it wrong is recoverable, and the fix is visible.
Records are correctable rather than silently rewritten. The correction and the original both remain legible.
How long things are kept, and on whose terms.
Retention is a property of the Context, subject to minimal collection and purpose limits, and revocable by the participant.
What you put in, you can take out.
A participant can export their own Context data in a usable form. Sovereignty that cannot leave is not sovereignty.
When something goes wrong, there is a named way to raise it and a named person accountable for it.
A defined path from report to acknowledgement to correction, with the outcome recorded. Redress is part of the protocol, not a support policy bolted on afterwards.
