govoplan/docs/README.md

GovOPlaN Documentation Map

This directory contains cross-repository product, architecture, release, and operational documentation. The map below defines which document answers which question. A document not listed as the current status source must not present volatile repository, issue, release, or maturity counts as current facts.

Strategy

Question	Canonical source
What are the stable ideas and boundaries of the platform?	Platform Core Ideas
What product outcomes should GovOPlaN pursue?	Connected Governance Platform Roadmap
Which institutional concepts and owners form the target architecture?	Institutional Governance Target Architecture
Which end-to-end proofs should guide implementation?	Reference Journey Program
What is the reconciled state now?	Strategy Status
Which collected ideas and user stories inform the product direction?	Product Input Register

The dated Strategic Review explains why the current reset and sequencing were chosen. It is an assessment record, not a second live status page.

Product Architecture

Topic	Canonical source
Product-facing experience and hiding technical module boundaries	Product Experience and Module Boundaries
Configurable product areas and task-local tools	Quick Access and Product Areas
Federation between autonomous installations	Federated GovOPlaN Architecture
Institutional digital twin and continuous assurance	Institutional Digital Twin
Assisted and non-digital channels	Assisted and Non-Digital Channels
Cross-module temporal, purpose, retention, and institutional-context adoption	govoplan-core/docs/INFORMATION_GOVERNANCE_ADOPTION.md
eAkte and digital-record ownership	govoplan-records/docs/EAKTE_ARCHITECTURE.md
Data source, definition, and transformation graph	Datasource and Definition Graph Architecture
Focused task views	Views Architecture
Shared interface patterns	Interface Pattern Language

Runtime And Delivery

• Module Contracts and Installs
• Platform Control Plane
• Installation and Deployment Architecture
• Kubernetes VM Test Lab
• Deployment Profiles
• Scaling and Multi-Host Deployment
• Recovery and Rollback Guarantees
• Recovery Ledger Adoption
• Package Registry Releases

Evidence And Snapshots

These documents are intentionally dated or pinned. They may remain useful even after the product changes, but they do not override STRATEGY_STATUS.md.

• Capability and Infrastructure Fit Assessment, pinned to the 2026-07-22 Campaign composition
• Strategic Review 2026-08-05
• Backup and Restore Evidence
• Production Target Handoff
• Target Maturity Evidence Runbook

Machine-readable schemas and evidence files belong beside the document that defines them. Generated inventories belong in audit-reports/ and should not be edited manually.

Maintenance Rules

1. Gitea issues are the only live work-state source.
2. STRATEGY_STATUS.md is the only prose reconciliation of current portfolio state. Refresh it from manifests, inventories, tests, and Gitea; do not copy its counts into durable architecture pages.
3. Durable documents state decisions, invariants, ownership, and acceptance gates. They link to status and issues for implementation depth.
4. Dated assessments retain their original composition and conclusion. Add a snapshot notice rather than silently updating their claims.
5. Module-specific behavior and user/admin documentation remain in the owning repository. Meta documentation defines cross-module outcomes and contracts.
6. A new strategy document must replace, narrow, or link an existing source; it must not introduce a parallel roadmap.
7. The Product Input Register preserves external idea and story notes, but only Gitea issues carry live priority, ownership, and implementation state.