docs: organize cross-product documentation

README.md

@@ -123,7 +123,7 @@ Synchronize module package workflows and inspect the registry release contract:
 
 Package publication, exact artifact locking, and the optional `govoplan`
 developer meta-package are documented in
-[Package Registry Releases](docs/PACKAGE_REGISTRY_RELEASES.md).
+[Package Registry Releases](docs/operations/PACKAGE_REGISTRY_RELEASES.md).
 
 For reproducible release artifacts, set `SOURCE_DATE_EPOCH` to the release
 commit timestamp (or pass an explicit timezone-qualified `--timestamp`):
@@ -170,19 +170,19 @@ Create and validate a private, declarative installation bundle:
 ```
 
 The current executable slice and remaining production gates are documented in
-[Installation and Deployment Architecture](docs/INSTALLATION_AND_DEPLOYMENT_ARCHITECTURE.md).
+[Installation and Deployment Architecture](docs/operations/INSTALLATION_AND_DEPLOYMENT_ARCHITECTURE.md).
 The canonical distinction between local source development, split source
 integration, immutable single-host rehearsal, one-host production and
 multi-host Kubernetes production is in
-[Deployment Profiles](docs/DEPLOYMENT_PROFILES.md).
+[Deployment Profiles](docs/operations/DEPLOYMENT_PROFILES.md).
 Same-host replica balancing and the multi-host promotion boundary are documented
-in [Scaling and Multi-Host Deployment](docs/SCALING_AND_MULTI_HOST_DEPLOYMENT.md).
+in [Scaling and Multi-Host Deployment](docs/operations/SCALING_AND_MULTI_HOST_DEPLOYMENT.md).
 Create, update, pause, resume, verify and remove a local or multi-hypervisor K3s
 VM target with the guarded lifecycle documented in
-[Kubernetes VM Test Lab](docs/KUBERNETES_TEST_LAB.md).
+[Kubernetes VM Test Lab](docs/operations/KUBERNETES_TEST_LAB.md).
 The recovery state machine, migration rollback boundary, and required restore
 drills are documented in
-[Recovery and Rollback Guarantees](docs/RECOVERY_AND_ROLLBACK_GUARANTEES.md).
+[Recovery and Rollback Guarantees](docs/operations/RECOVERY_AND_ROLLBACK_GUARANTEES.md).
 
 ## Configuration
 
@@ -195,47 +195,14 @@ such as `~/.config/gitea/gitea.env` and be passed with `--env-file`.
 
 ## Structure
 
-The repository categories are documented in
-`docs/REPOSITORY_STRUCTURE.md`. The machine-readable list lives in
-`repositories.json`; the clickable human-readable index is
-`docs/REPOSITORY_INDEX.md`.
+Start with the [documentation map](docs/README.md). It separates stable
+strategy, architecture, operations, project reference, pinned evidence, and
+historical records and identifies the canonical source for each question.
 
-Meta ownership and module install/contract boundaries are documented in
-`docs/META_REPO_SCAN.md` and `docs/MODULE_CONTRACTS_AND_INSTALLS.md`.
-Frontend layout principles for module pages are documented in
-`docs/FRONTEND_LAYOUT_PRINCIPLES.md`.
-The provider-neutral datasource boundary and reusable Dataflow/Workflow graph
-contract are documented in
-`docs/DATASOURCE_AND_DEFINITION_GRAPH_ARCHITECTURE.md`.
-The cross-product destination, stakeholder visions, configuration archetypes,
-connected outcome stories, and capability horizons are documented in
-the [Connected Governance Platform Roadmap](docs/CONNECTED_GOVERNANCE_PLATFORM_ROADMAP.md).
-The reconciled institutional semantics, source-authority modes, module layers,
-candidate Mandates/Services/Parties/Decisions boundaries, and migration
-sequence are documented in the
-[Institutional Governance Target Architecture](docs/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md).
-The selected Campaign-to-Postbox-to-data-to-collaboration implementation path,
-including stage gates and shared documentation expectations, is in the
-[Reference Journey Program](docs/REFERENCE_JOURNEY_PROGRAM.md).
-The administrator journey from a Core-baseline bootstrap through online module
-installation, scale-out, and reversible environment promotion is defined in
-[System Administrator Lifecycle User Story](docs/SYSTEM_ADMINISTRATOR_LIFECYCLE_USER_STORY.md).
-The corresponding host deployment compiler, managed/external component choices,
-reconfiguration semantics, and safe Web update boundary are defined in
-[Installation and Deployment Architecture](docs/INSTALLATION_AND_DEPLOYMENT_ARCHITECTURE.md).
-The concrete replica, worker-node, load-balancer, and shared-state topology is
-defined in [Scaling and Multi-Host Deployment](docs/SCALING_AND_MULTI_HOST_DEPLOYMENT.md).
-Durable deployment journals, Core recovery evidence, and the distinction
-between pre-migration configuration restore and post-migration forward recovery
-are defined in
-[Recovery and Rollback Guarantees](docs/RECOVERY_AND_ROLLBACK_GUARANTEES.md).
-The first Campaign-centric capability and infrastructure fit assessment is in
-`docs/CAPABILITY_AND_INFRASTRUCTURE_FIT.md`. Its rerun tooling can collect and
-verify a bounded installed composition; target, provider and production claims
-remain separate, expiring attestations signed by independently scoped proof
-authorities. The operational issuance, target-run, recovery-measurement, key
-custody, and promotion-gate procedure is in
-[Target Maturity Evidence Runbook](docs/TARGET_MATURITY_EVIDENCE_RUNBOOK.md).
+The machine-readable repository list lives in `repositories.json`; the
+clickable directory is the
+[Repository Index](docs/project/REPOSITORY_INDEX.md), and ownership boundaries
+are in [Repository Structure](docs/project/REPOSITORY_STRUCTURE.md).
 
 # GovOPlaN Docker