Trinity is the principal contractor between clients and engineers. Engineers are subcontractors working on projects, coordinated and matched by Trinity. Every project opens with a Genesis Hash Chain — a verifiable, append-only record of all milestones, messages, and decisions. Sergej is Switch #1.
Two ways in. Register as an Operator in five minutes — open tier, instant access to apparatus, the Genesis Hash Chain, 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. Trinity coordinates projects; each project lives on its Genesis Hash Chain. The chain records each milestone and decision; reputation accrues as a function of what actually shipped, not what was promised.
The same record that makes the project legible to the client is what allows the Network to compound on the inside. Verifiable work, not vibes.
Operator A closes a 40k project, sourced with Engineer B\'s help. The project Genesis Chain records A\'s delivery and B\'s role. B\'s reputation +1 (sourcing). A\'s reputation +1 (delivery). B\'s sponsor C receives a bounded TRIN signal (pledge return). The body\'s density score updates.
All on-chain. Trinity coordinates, does not discretionally decide.
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, the Genesis Hash Chain, 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 protege, is what is on trial.
A cryptographic identity, a triadic seat (sponsor + peer), keys to the commons (templates, swarm access, intelligence, Genesis Hash Chain), and nine invitation slots — refilled as proteges seat themselves, not on a schedule.
The sponsor's signature is attached to the new Engineer's record permanently. If the protege dishonors the body, the sponsor's reputation reflects it. If the protege 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, Genesis Hash Chain, 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 protege win.
Propagation runs by depth, not by headcount. A switch opens at most nine seats; each seated protege may open nine more. The shape below is a ceiling drawn by geometry and a floor held by reputation — the body never fills the ceiling, and it never tries to.
One switch is active. Everything downstream is opt-in — there is no cohort and no opening window.
A switch holds nine slots and spends them deliberately. Each spend is a permanent pledge, not a referral.
Every protege who becomes a switch opens nine of their own. Reach is the residue of craft, never its goal.
The ceiling rises by x9 each depth. The floor is reputation — the body never fills the ceiling, and never tries to.
Continuous opt-in is the only mode. There is no era boundary, no application window, no closing of the doors. Members may leave at any time and take their work, their reputation, and their relationships with them — 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 one section of nine. Each is a sovereign organ that binds back to the body — naming the relation, not just the neighbour.
Every project has an append-only, hash-linked record of milestones, messages, and decisions. This is the source of truth.
The founding declaration each member affirms at the threshold of entry.
Where members publish craft into the commons and accrue verifiable reputation.
Built inside the body first, then carried to the open market.
The protective layer wrapped around member infrastructure.
The curated stream shared only inside the gate.
The aesthetic that thickens the shared fabric.
The worldview the whole body affirms.
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 + Genesis Hash Chain + 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