OTCS-0001 — Adopt the v0.1 registry seed records

Adopts the seven seed records in registry/projects/: three registered (founder-maintained, honest maturity profiles, independent validation 0) and four fictional example records covering enforcement, observability, evidence, and repair.

Clock demonstration: this is a registry_update proposal with a 3–7 day minimum deliberation clock (GOVERNANCE.md §3), started 2026-07-25. Unlike OTCS-0000, whose bootstrap waiver was disclosed as unavoidable, this proposal waits its clock out: ballots are cast, but no decision record may be written before 2026-07-28 at the earliest. The clocks bind the founder or they bind nobody.

Phase history

Objections

Objection 001 — the seed registry is founder-only

Raised: 2026-07-25 (self-raised; recorded as a material objection so the first external reader finds it already on the record).

Objection. Every registered record is founder-maintained. A registry launched this way could read as self-promotion wearing governance clothing — the exact pattern EVIDENCE-MODEL.md §7 says this system prevents.

Answer (2026-07-25). The condition is real and is mitigated by structure rather than denial: (1) record_state discipline — nothing here is observed or implied third-party participation; (2) every founder record carries independent validation 0, stated; (3) relationship edges among founder projects are marked self_asserted with the founder edge named in asserted_by; (4) each record's needs field openly solicits the external evaluation that would change those scores; (5) CHARTER.md §6 declares the conflict, §7 defines the exit from founder governance. The registry's founder-only state is disclosed as a stage, not laundered as an ecosystem.

Status: answered; carried on the record.

Ballots

Decision

No decision record exists — the clock binds the founder or it binds nobody.