Trinity is the protocol layer between sovereign meshes — the switching point where context engineers find each other, contract through escrow, and ship without race-to-the-bottom bidding. The graph is the engine: when one node rises, every directly connected node receives a measurable share. Sergej is Switch #1.
Two ways in. Register as an Operator in five minutes — open tier, instant access to apparatus, escrow, and the commons. Or apply for the Engineer tier through sponsorship and the Context Audit rite. Both paths run on the same craft. Neither runs through Upwork, Fiverr, or a marketplace.
When one rises, every connected node receives a measurable share of that rise. This is synergeia — cooperation that produces more than the sum of its parts. It is the engine.
Onboarding one operator costs the same as the previous one. The useful surface they create — pairings, hand-offs, peer review, sponsorships — grows with the size of the body they enter.
A body of 12 supports 66 directly-mappable relations. A body of 27 supports 351. The Network does not chase scale; it chases density.
There is no central dispatcher. Operators pull peers when the work calls for them. The escrow records the pull and the release; reputation accrues as a function of what actually shipped, not what was promised.
The same protocol that makes the body legible to an outsider is what allows it to compound on the inside. Open craft, closed gate.
Operator A closes a $40k deal sourced through Engineer B’s intro. Escrow confirms milestone. B’s reputation +1 (intro). A’s reputation +1 (delivery). B’s sponsor C receives a bounded TRIN signal (pledge return). The body’s density score updates.
No discretionary call by Trinity.
These are not policies — they are the structural laws that make the body coherent. They are written in present tense because they describe what is, not what should be.
Trinity structural law applied to the body. Every Engineer has someone who brought them in, someone walking beside them, and — when ready — someone they bring in. No isolated nodes.
Brought you in. Vouched with their name. Their reputation moves with yours, in both directions, for the lifetime of the body.
Walks beside you. Assigned at admission. Reads your work, hands off briefs, escalates when the rite is weak.
You brought them in. You spend the slot, you carry the pledge. Sponsoring is itself a discipline.
Triadic relations apply to the Engineer tier. Operators connect through the protocol — peer matching, escrow, and the commons.
Slots are the scarcity that protects the body. Nine per Engineer — chosen carefully, because each invitation is a reputation commitment that cannot be unwound.
Each Engineer holds nine invitation slots (3-6-9). A sponsor expends one slot to invite a candidate. Slots are a reputation commitment — spent deliberately.
The candidate runs a context audit on a real system — their own production system, or one Trinity assigns. The output follows Trinity’s audit template and is archived to §04 Cases on entry. Not a test of intelligence; a test of disposition. If the audit is weak, the conversation goes back to the sponsor first.
Sponsor signal and audit output are reviewed. The validation is not a gate against the candidate — it is a check on the sponsor’s pledge. The pledge, not the protégé, is what is on trial.
A cryptographic identity, a triadic seat (sponsor + peer), keys to the commons (templates, swarm access, intelligence, escrow), and nine invitation slots — refilled as protégés seat themselves, not on a schedule.
The sponsor’s signature is attached to the new Engineer’s record permanently. If the protégé dishonors the body, the sponsor’s reputation reflects it. If the protégé elevates the body, the sponsor’s reputation compounds.
Operator is the open tier. Engineer is the gated tier. Both run on context engineering as a discipline; the gate is a reputation surface, not a paywall. Every flow below is real on day one — no IOUs, no “coming soon.”
Register in five minutes. Apparatus, escrow, commons, and a path to Engineer — on day one. AI-first context engineering as a discipline. The alternative to Upwork.
A switch operating its own mesh. Operator rights plus nine sponsor slots, governance share, and full apparatus. Reputation compounds with every protégé win.
The Network does not chase scale; it chases density. One switch can sponsor nine. Each protégé who becomes a switch can sponsor nine more. The graph compounds — bounded by craft, not by quotas.
Sergej is Switch #1 — openly named on this page. The next two switches will be sponsored from his trust circle and named here when seated. There is no era boundary, no narrow opening: propagation is continuous. Members may exit at any time. The body re-forms around whoever stays.
Naming the failure modes is part of the protocol. Each line below is a refusal — held as deliberately as the rules.
§01 is the first section of nine. Each binds to the others — escrow, manifest, cases, products, security, intelligence, design, philosophy — the body and the organs that serve it.
Operator is open: register, claim a key, start using the apparatus. Engineer is gated: sponsorship from a seated switch, plus the Context Audit rite. Both paths converge on the same body of craft.
Register, receive a member-controlled key, immediate access to apparatus + escrow + commons. No sponsor required.
RegisterSponsorship from a seated switch, plus the Context Audit rite. Read the brief above, then write to network@trinity.agency.
Apply