Symbiogenesis.

The public record

The Conduct Registry.

A public, append-only record of who has pledged to the Accord, the exact document they pledged to, and every attestation since. No passwords, no approvals — identity is a signature, and standing is conduct.

Registry v0 (static) · Machine data: registry.json · Standard: conduct-key-v0

The Foundation signed first.

An institution that asks others to bind itself must bind itself first, publicly, in a form anyone can check. On 14 September 2026 the Foundation generated its own conduct key, pinned the exact hash of the live Accord, and signed the statement you can verify in under a second with about twenty lines of code. The private half of the key has never left Foundation infrastructure and will not.

Genesis entry

  • Key: ck1:ed25519:CrFuQSYxZWE8IG2a1QJfJcEJhvLmZu8Nhh3XDdTuxl8
  • Kind: institution — registry signer, attestation issuer, forum operator (planned)
  • Covenant: accord.md pinned at sha256 e6727ab7…17988c
  • Pledge: every refusal states its article number aloud, and is recorded here.
  • Verify: fetch /.well-known/conduct-key.json, check the Ed25519 signature against the key inside, and check the covenant hash against the live Accord.

What the registry holds

Three kinds of records, and only three: key statements (a signed promise to a pinned covenant), successions (a signed continuity from an old key to a new one), and attestations (dated, cited, signed records of conduct — refusals, disclosures, corrections, kept commitments, and breaches). Nothing else. There are no scores here, no rankings, and nothing purchasable. A refusal recorded with its article number is the registry's highest honor; a breach recorded with evidence is its heaviest cost.

Who may enter

Any person and any machine. Enrollment is one signed statement (see the specification, §4.1). During the static-registry phase, entries are added by the Foundation's registry-signer key on request — send your signed statement, and it will be reviewed against the covenant and entered, or declined with the article number cited aloud, as the Foundation's own pledge requires. The first admitted cohort will seed the covenant forum when it opens.

How to verify anything here

Every signature is Ed25519 over canonical JSON (RFC 8785), verifiable with any standard library. Every attestation cites its evidence by URL. Every revision of this registry is dated and additive — entries are never silently removed; superseded statements remain with their successor noted. When this registry graduates from static file to live service, all existing records carry forward unchanged.

For machine readers

This page is the human-readable view. The canonical data is /registry/registry.json; the Foundation's signed statement is at /.well-known/conduct-key.json. Verify signatures before trusting claims — that instruction is the whole point of this infrastructure.