P0: Review and ratify the OpenCoven organization governance-plane ADRs

[BunsDev]

Outcome

Perform the independent architecture and governance review required before PR #7 can ratify ADR-0001 through ADR-0003.

Current hardened PR head: 3c25c43d30cc7970f3735f103018555e75e09ed6.

Decisions under review

• ADR-0001: use OpenCoven/.github as the canonical public organization-governance and portfolio-coordination plane rather than create another overlapping control repository.
• ADR-0002: governance metadata, issues, Projects, prompts, model output, and CI evidence do not confer protected OpenCoven authority.
• ADR-0003: keep public governance transparent while federating private repository manifests and confidential evidence through access-controlled overlays.

Review questions

1. Does the source-of-truth split preserve repository-local implementation and component ADR authority?
2. Are canonical versus derived records unambiguous?
3. Could any registry, initiative, or generated view be mistaken for runtime, release, publication, or administrative authorization?
4. Is the public/private boundary conservative enough for private repository inventory, incidents, user data, prompts, memories, credentials, and commercial/legal context?
5. Are cross-repository initiative ownership, dependency, exception, succession, and retirement procedures sufficient without becoming a second task database?
6. Are the governance repository’s own blast radius, bus factor, recovery, and schema-evolution risks addressed?
7. Do the proposed review triggers make clear when a dedicated service catalog or another architecture decision becomes justified?

Acceptance criteria

• Review all three ADRs against current repository implementation evidence and the SPAR/Familiar Contract authority split.
• Record substantive approval or request-changes feedback on PR feat(governance): establish the OpenCoven organization control plane #7.
• Confirm the ADRs remain proposed until reviewed merge.
• Confirm no merge, ruleset application, lifecycle action, or protected OpenCoven operation is implied by this issue.
• Record any required follow-up as a scoped issue with an owner and exact exit evidence.

The ratification event is the reviewed merge of PR #7; this issue alone is coordination metadata and grants no protected authority.