docs: update meta documentation links

docs/DOCUMENTATION_MAP.md

@@ -43,9 +43,9 @@ operator, and roadmap pages.
 | Topic | Canonical document | Notes |
 | --- | --- | --- |
 | Product roadmap and module routing | `GOVOPLAN_MASTER_ROADMAP.md` | Product-level sequencing, implementation gates, issue routing, and missing-module decisions. |
-| Stable platform ideas | `govoplan/docs/PLATFORM_CORE_IDEAS.md` | Cross-product thesis, canonical distinctions, product experience rule, maturity rule, and decision test. |
+| Stable platform ideas | `govoplan/docs/strategy/PLATFORM_CORE_IDEAS.md` | Cross-product thesis, canonical distinctions, product experience rule, maturity rule, and decision test. |
-| Current cross-product reconciliation | `govoplan/docs/STRATEGY_STATUS.md` | The only current prose status source; generated evidence and Gitea remain authoritative inputs. |
+| Current cross-product reconciliation | `govoplan/docs/strategy/STRATEGY_STATUS.md` | The only current prose status source; generated evidence and Gitea remain authoritative inputs. |
-| Institutional governance target | `govoplan/docs/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md` | Cross-product semantic layers, source-authority modes, candidate Mandates/Services/Parties/Decisions boundaries, and migration sequence. |
+| Institutional governance target | `govoplan/docs/architecture/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md` | Cross-product semantic layers, source-authority modes, candidate Mandates/Services/Parties/Decisions boundaries, and migration sequence. |
 | UI/UX decisions | `UI_UX_DECISION_LEDGER.md` | Binding guided-UI decisions, open decisions, impact index, and review checklist. |
 | Core interface migration | `INTERFACE_PATTERN_MIGRATION.md` | Core-owned settings, credential, retention, lifecycle, and shared-component evidence for the product pattern language. |
 | Interface ethics and design doctrine | `INTERFACE_ETHICS_AND_DESIGN_DOCTRINE.md` | Product-level doctrine for context, decision, consequence, contestability, responsibility, and traceability. |

docs/EXTERNAL_REFERENCES_AND_INTEGRATION_MATURITY.md

@@ -40,7 +40,7 @@ must not imply that GovOPlaN holds an authoritative copy.
 Integration maturity states what an adapter is capable of doing. It does not
 decide which system owns truth for a configured object or field group. A
 binding separately selects one of the source-authority modes defined by the
-[institutional governance target architecture](../../govoplan/docs/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md):
+[institutional governance target architecture](../../govoplan/docs/architecture/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md):
 
 - `native_authoritative`
 - `external_authoritative`

docs/GITEA_ISSUES.md

@@ -13,4 +13,4 @@ tools/gitea/gitea-sync-wiki.py --help
 
 Canonical documentation:
 
-- `/mnt/DATA/git/govoplan/docs/GITEA_ISSUES.md`
+- `/mnt/DATA/git/govoplan/docs/project/GITEA_ISSUES.md`

docs/GOVOPLAN_MASTER_ROADMAP.md

@@ -10,15 +10,15 @@ gates. Issues are the active backlog; this document is durable architecture
 planning context and should be mirrored to the Gitea wiki.
 
 The meta repository's
-[Connected Governance Platform Roadmap](https://git.add-ideas.de/GovOPlaN/govoplan/src/branch/main/docs/CONNECTED_GOVERNANCE_PLATFORM_ROADMAP.md)
+[GovOPlaN Roadmap](https://git.add-ideas.de/GovOPlaN/govoplan/src/branch/main/docs/strategy/ROADMAP.md)
 describes the corresponding cross-product stakeholder visions, configurable
 service and operating configurations, connected outcome stories, and
 capability horizons. The selected five-stage delivery sequence and its gates
 are in the meta repository's
-[Reference Journey Program](https://git.add-ideas.de/GovOPlaN/govoplan/src/branch/main/docs/REFERENCE_JOURNEY_PROGRAM.md).
+[Reference Journey Program](https://git.add-ideas.de/GovOPlaN/govoplan/src/branch/main/docs/strategy/REFERENCE_JOURNEY_PROGRAM.md).
 The semantic target, source-authority modes, and reconciliation with the
 implemented platform are in the meta repository's
-[Institutional Governance Target Architecture](https://git.add-ideas.de/GovOPlaN/govoplan/src/branch/main/docs/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md).
+[Institutional Governance Target Architecture](https://git.add-ideas.de/GovOPlaN/govoplan/src/branch/main/docs/architecture/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md).
 Those product documents are canonical; this Core roadmap remains their
 technical sequencing and module-routing companion.
 

docs/MODULE_ARCHITECTURE.md

@@ -16,7 +16,7 @@ The experimental remote WebUI bundle loading design is tracked in
 The cross-product semantic layers, source-authority modes, and candidate
 Mandates, Services, Parties, and Decisions boundaries are canonical in the
 meta repository's
-[`INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md`](../../govoplan/docs/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md).
+[`INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md`](../../govoplan/docs/architecture/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md).
 
 ## Layer Model
 

docs/SECURITY_AUDIT.md

@@ -12,4 +12,4 @@ tools/checks/security-audit/run.sh --mode full --scope govoplan
 
 Canonical documentation:
 
-- `/mnt/DATA/git/govoplan/docs/SECURITY_AUDIT.md`
+- `/mnt/DATA/git/govoplan/docs/operations/SECURITY_AUDIT.md`

docs/STATE_AND_RECOVERY_CONTRACT.md

@@ -140,7 +140,7 @@ Core does not create production database backups. The deployment owner must
 provide backup, retention, encryption, restore verification, and recovery-point
 coordination for PostgreSQL, object storage, and encryption keys. The canonical
 operator procedure is documented in
-`govoplan/docs/RECOVERY_AND_ROLLBACK_GUARANTEES.md`.
+`govoplan/docs/operations/RECOVERY_AND_ROLLBACK_GUARANTEES.md`.
 
 ## Verification