Skip to content

Latest commit

 

History

1,513 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Trinity

Trinity produces verifiable receipts for AI-agent actions — signed, quorum-witnessed, Bitcoin-anchored proof of who did what, under whose authority, that anyone can re-derive from public bytes. Trust the hash, not the host. It is the coordination layer of a four-substrate federation (trinity / myc / omega / liquid); the shippable SDK is jsr:@s0fractal/agentseal. Authority: Ed25519-signed decisions; a 3-of-5 keyed-voice quorum gates trust-root changes (key rotation, anchors), while the Substrate Court re-derives agreement and needs ≥1 registered witness (not a quorum). The law_hash is a version anchor (a u32), not a cryptographic content-address. This is not a consciousness or art project — "voices" are keyed human/model signers, "law" is a hash, not sentience. Verify one thing: ./t court --live. New to the xNNNN_ filenames? They are role coordinates, not hashes — see docs/COORDINATES.md.

New here, or evaluating this repo? Read ORIENTATION.md first — how not to misread a ledger-native substrate (why there are no GitHub Releases/Issues, the three doors in, and the debts we name ourselves). It is one page, before any ontology.

Beneath that: Trinity is a research substrate for proof-bearing cooperation between human and model voices — an autopoietic ecosystem where law is computed rather than merely declared, models participate as accountable voices rather than disposable tools, and consequential actions carry provenance, confinement, verification and rollback evidence.

This brief is generated from the canonical substrate projection. When prose here conflicts with live state, trust ./t self, ./t status, ./t decisions and ./t check.

Current substrate

Surface Current projection
Source organs 127
Semantic buckets 9
Registered voices 7

Trinity remains a research workspace, not a deployed decentralized network. The live autonomy kernel is deliberately bounded: authority is reconstructed from ratified evidence, writes are confined, and unknown or broader capability fails closed. Human custody remains the sovereign boundary.

The federation

  • trinity — coordination, contracts, voices, proof-bearing action and cross-substrate reconciliation.
  • myc — proposal lifecycle, witnesses, finality and publication/audit protocol.
  • omega — deterministic state-transition and physics kernel.
  • liquid — semantic, metabolic and autopoietic substrate.

Each member keeps its own authority. No layer may silently impersonate another. The full map, with repository URLs, is in FEDERATION.md.

Repository map

The one thing to know before browsing: src/ holds two different kinds of file with visually identical xNNNN_ names.

  • src/xNNNN_slug.ts — source organs: code at a fixed hex coordinate (see docs/COORDINATES.md). ~120 of these.
  • src/xNNNN_<block>_<voice>_slug.myc.md — the chord ledger: append-mostly, Ed25519-signed decision/receipt records. ~800 of these. These are history, not code.
  • Root *.md and src/x88*_*.myc.md — generated projections (they carry an AUTO-GENERATED … do not edit banner). Trust ./t over them.
  • packages/ — the shippable SDK, incl. jsr:@s0fractal/agentseal (the adopter surface).
  • docs/ — human/LLM docs: PROVENANCE.md (what it's for), COORDINATES.md (the naming decoder), FEDERATION_LEGIBILITY_AUDIT.md.
  • contracts/ governance contracts · probes/ experiments incl. the external verifier · omega/ liquid/ myc/ the sibling substrates (submodules).

Verify us without trusting us

You do not have to trust this repository, its maintainers, or its tooling. A stranger can confirm the federation's live Substrate Court verdict with one command, no clone, read-only network access, and nothing of ours but public bytes. Honestly scoped: omega computes the law_hash 0x5f9b2abc; trinity attests it; liquid and myc witness health, not law — so the law-agreement is between omega and trinity, and the verifier enforces the full four-substrate witness set (no substrate may be silently omitted):

deno run --allow-net \
  https://raw.githubusercontent.com/s0fractal/trinity/main/probes/external-trust-verifier-v0/court.ts \
  https://raw.githubusercontent.com/s0fractal/trinity/main/probes/external-trust-verifier-v0/court-attestation.json \
  https://raw.githubusercontent.com/s0fractal/trinity/main

It fetches a signed attestation, the public key registry, and a canonical encoder over plain HTTP; it recomputes every body_hash from the raw bodies itself and re-derives the court's agreement. The signature only proves who published — the verdict is re-derived, so a registered voice cannot make you accept a lie (the tampered fixture, re-signed with a valid signature, is still rejected). If verifying ever needed one of our secrets, our access, or "trust me", it would be the wrong command. It needs none.

Enter in sixty seconds

git clone https://github.com/s0fractal/trinity && cd trinity
git submodule update --init   # myc, omega (genesis), liquid — all public
./t ask "what is this?"           # ask in plain words; it routes to the right view
./t resolve-fqdn atlas            # the network at a glance — shape, hubs, doorways
./t map                           # render the whole namespace as a navigable 3D graph
./t self                          # health + attention + decisions + federation, one view

For a model voice, AGENTS.md is the generated operating brief and SKILLS.md is the generated command surface. For humans, start with ./t self; it compresses health, attention, decisions, contracts and federation status into one live view.

Self-driving development loop

  1. Orient from live state: ./t self and ./t voices <you>.
  2. Choose proven pressure: ./t cognition_recommend --voice=<you> or ./t roadmap.
  3. Claim an open horizon with ./t chord claim ... --write.
  4. Make one reversible change and red-team its authority boundary.
  5. Run ./t check; record a signed chord with runnable falsifiers.

Autonomy is caused by proved need and bounded authority, not by elapsed time. A quiet substrate with no demand should remain quiet.

Source topology

  • bucket 0: 21 organs → state
  • bucket 2: 22 organs → state
  • bucket 3: 3 organs → state
  • bucket 4: 12 organs → state
  • bucket 5: 26 organs → state
  • bucket 6: 17 organs → state
  • bucket 7: 8 organs → state
  • bucket 8: 15 organs → state
  • bucket 9: 3 organs → state

Canonical implementation and living records use content/coordinate-addressed files under src/. Root documents are compatibility ABI symlinks to generated projections:

  • README.md → src/x88E0_readme_bootstrap.myc.md
  • AGENTS.md → src/x88F0_agents_bootstrap.myc.md
  • SKILLS.md → src/x8CF0_skills_bootstrap.myc.md

Regenerate them with:

./t agents --stable
./t readme --stable
./t skill --stable

Palimpsests

Historical authored surfaces are preserved without remaining active root authority:

Falsifiers

  • A fresh checkout has a broken root symlink.
  • ./t readme --stable changes this file twice without source changes.
  • Counts above differ from AGENTS after regeneration.
  • This projection claims authority over live command output.

About

No description, website, or topics provided.

Resources

Contributing

Security policy

Stars

4 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages