Sync Repo-docs-INSTITUTIONAL-GOVERNANCE-TARGET-ARCHITECTURE from project files

Repo-docs-INSTITUTIONAL-GOVERNANCE-TARGET-ARCHITECTURE.-.md

@@ -1,4 +1,4 @@
-<!-- codex-wiki-sync:1e1ef481f23c7d0c43f4d250 -->
+<!-- codex-wiki-sync:60762b311997fbf4c6199809 -->
 
 > Mirrored from `/mnt/DATA/git/govoplan/docs/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md`.
 > Origin: `repository`.
@@ -462,11 +462,15 @@ truthfully completed by adding generic platform code:
    protocol and product decisions for voter eligibility, custody, secrecy,
    recount, challenge, retention, and operational assurance. Equivalent future
    adapters must satisfy the declared provider and recovery gates.
+   Provider selection and certification are tracked in
+   [Committee #1](https://git.add-ideas.de/GovOPlaN/govoplan-committee/issues/1).
 2. **Target-produced maturity evidence:** `reference_ready`, `supported`, and
    `lts` cannot be generated from source code. An exact release and deployment
    must produce signed, expiring accessibility, privacy, security, operator,
    provider, backup/restore, rollback, and recovery-drill evidence. The verifier
    and schemas are implemented; the actual claims require those real runs.
+   The pinned-release evidence run is tracked in
+   [GovOPlaN #37](https://git.add-ideas.de/GovOPlaN/govoplan/issues/37).
 
 Forms and Forms Runtime no longer constitute an architecture gap. Remaining
 depth includes anonymous/public identity profiles, concrete file and signature