# Documentation Source Of Truth Map v1

Status: canonical-current
Owner: Platform Architecture
Last updated: 2026-06-11

## Purpose

This map identifies the current documentation authority after the Platform
Shared Services Model, Fairway, and v3 namespace cleanup work. It is the
handoff point for Docusaurus portal refreshes: portal pages should summarize
and link these sources instead of reconciling stale source docs themselves.

## Classification Rules

| Classification | Portal treatment |
| --- | --- |
| `canonical-current` | Safe to summarize as current authority. |
| `implementation-current` | Safe when cross-linked to the authority. |
| `migration-state` | Safe only with exit criteria or compatibility window. |
| `future-state` | Label clearly as target direction, not current behavior. |
| `superseded` | Do not expose as current; link replacement. |
| `historical-reference` | Link only as evidence or decision history. |

Generated inputs:

- `.fairway/artifacts/docs-pssm-inventory.yaml`
- `.fairway/artifacts/docs-pssm-classification.yaml`
- `packages/docs/static/portal/source-doc-inventory.json`

## Current Authority

| Area | Current source of truth | Supporting current docs | Migration / future-state docs |
| --- | --- | --- | --- |
| Platform shared services model | `doc/architecture/platform-foundation/Platform_Shared_Services_Model_v2.md` | `doc/architecture/platform-foundation/README.md`, `doc/architecture/platform-foundation/Platform_Code_And_Deployment_Architecture_v1.md`, `doc/architecture/platform-foundation/Platform_Shared_Services_Completion_Roadmap_v1.md` | `doc/architecture/Platform_Shared_Services_Model_v1.md` is superseded historical reference. |
| Shared platform governance and agentic engineering | `doc/architecture/platform-foundation/Shared_Platform_And_Governed_Agentic_Engineering_Model_v1.md` | `doc/operations/Fairway_Agent_Operating_Model.md`, `doc/operations/Fairway_Review_Operating_Model.md`, `doc/operations/Shared_Service_Lane_Worktree_Model_v1.md`, `doc/architecture/platform-foundation/Security_Architecture_Current_State_v1.md` | Portal pages should summarize this model as the current stabilization operating model and must not treat provider chat as authority. |
| Fairway coordination and active queue | `.fairway/platform-foundation-implementation-track.yaml` | `.fairway/platform-foundation-config.toml`, `doc/governance/Multi_Agent_Lane_Worktrees_v1.md`, `doc/governance/Agent_Orchestration_Tool_Extraction_Boundary_v1.md` | `doc/governance/Agent_Work_Queue.yaml` is legacy queue context, not active execution authority. |
| Ownership maps and boundary guards | `doc/architecture/platform-foundation/ownership-maps/README.md` | package, route, schema, event, frontend, worker, and v3 namespace ownership maps under `doc/architecture/platform-foundation/ownership-maps/` | Guard findings remain implementation-current until graduated to blocking gates. |
| IAM, department hierarchy, and billing attribution | `doc/architecture/Unified_IAM_Billing_Across_Products_v1.md` | `doc/architecture/IAM_Department_Hierarchy_Implementation_Plan_v1.md`, `doc/architecture/token-factory/IAM_Department_Layer_Readiness_v1.md`, `doc/architecture/Billing_Architectural_Invariants_v1.md` | Token Factory readiness docs are future/product-readiness inputs until product implementation starts. |
| Product onboarding and App SDK | `doc/architecture/platform-foundation/Product_Onboarding_Executable_Packet_v1.md` | `doc/architecture/platform-foundation/Product_Onboarding_Checklist_v1.md`, `doc/architecture/platform-foundation/App_SDK_Readiness_Matrix_v1.md`, `doc/architecture/App_SDK_Design_Principles_v1.md` | App SDK publishing and API playground research remain future-state until implementation tasks land. |
| Product registry, artifacts, and trust | `doc/architecture/platform-foundation/Platform_Registry_Contract_v1.md` | `doc/architecture/platform-foundation/registry/platform-registry.seed.yaml`, `doc/architecture/App_Artifact_Trust_and_Promotion_v1.md`, `doc/architecture/App_Platform_OCI_Registry_Baseline_v1.md` | Non-OCI artifact lifecycle docs are supporting future/migration references. |
| Policy, quota, capacity, and usage analytics | `doc/architecture/platform-foundation/Platform_Policy_Quota_Capacity_Composition_v1.md` | `doc/architecture/platform-foundation/Platform_Usage_Analytics_OLTP_OLAP_Boundary_v1.md`, `doc/architecture/Tenant_Admin_Quota_Delegation_v1.md` | Product-specific billing variants must route through shared attribution contracts before implementation. |
| Release profile gates and production readiness | `doc/architecture/platform-foundation/Platform_Release_Profile_Gates_v1.md` | `doc/governance/Platform_Control_Release_Promotion_Policy.md`, `doc/operations/Platform_Control_CI_CD_Multi_Environment_Model_v1.md`, `doc/operations/Platform_Service_Level_CI_CD_Operating_Model_v1.md` | Stress harness tasks are future implementation work until the scenario catalog and scripts land. |
| Evidence/status and observability | `doc/architecture/platform-foundation/Platform_Evidence_Status_Schema_v1.md` | `doc/architecture/platform-foundation/Platform_Runtime_Reconciliation_Evidence_Model_v1.md`, `doc/architecture/Observability_Architecture.md`, `doc/governance/Observability_Standards.md` | Evidence reports under `doc/operations/evidence/` are historical evidence unless promoted. |
| Security architecture current state | `doc/architecture/platform-foundation/Security_Architecture_Current_State_v1.md` | `doc/architecture/platform-foundation/Security_Architecture_Review_Triage_v1.md`, `doc/architecture/Platform_IAM_Model_v1.md`, `doc/architecture/IAM_MFA_Policy_and_Keycloak_Enforcement_v1.md`, `doc/architecture/PKI_Spec.md`, `doc/architecture/Node_Agent_Spec.md`, `doc/operations/Production_Platform_Baseline.md` | `~/Downloads/sec-review/Core42_GPUaaS_Cloud.pdf` is stale review input, not active architecture evidence. Regulated-profile claims require separate evidence. |
| Platform proxy and edge routing | `doc/architecture/Platform_Proxy_Provider_Neutral_Edge_Model_v1.md` | `doc/architecture/Platform_Proxy_Target_Architecture_v1.md`, `doc/architecture/Platform_Proxy_Compatibility_Route_Retirement_v1.md`, `doc/architecture/Platform_DNS_Cert_Endpoint_Model_v1.md` | Pomerium and old proxy retirement docs are migration-state unless explicitly promoted. |
| v3 namespace and route policy | `doc/architecture/platform-foundation/V3_Namespace_Retirement_Plan_v1.md` | `doc/architecture/platform-foundation/ownership-maps/v3-namespace-inventory.md`, `doc/architecture/API_Route_Modularization_and_V1_Freeze_v1.md`, `doc/architecture/API_Domain_Authoring_Model_v1.md` | `/api/v1/v3/*` remains compatibility only; portal should present canonical `/api/v1/*` paths. |
| Frontend IA and product surfaces | `doc/product/Product_Surface_IA_and_Role_Model_v1.md` | `doc/product/V3_Navigation_Journey_Contract_v1.md`, `doc/product/UX_Implementation_Spec.md`, `doc/product/UX_Journeys.md`, `doc/architecture/platform-foundation/Frontend_Module_Ownership_Split_v1.md` | Older v3 mock parity docs are migration-state or historical unless they describe current UI. |
| Terminal and node access | `doc/architecture/Terminal_WebSocket_Bridge_Architecture_v1.md` | `doc/architecture/adrs/ADR-011-terminal-node-websocket-bridge.md`, `doc/operations/runbooks/Terminal_Gateway_Incident_Runbook.md`, `doc/operations/runbooks/Node_Agent_And_Terminal_Preflight_Runbook.md` | Transport redesign docs are migration-state unless current implementation confirms the target. |
| Provider, provisioning, and node lifecycle | `doc/architecture/Provider_Lifecycle_And_Orphan_Reconciliation_v1.md` | `doc/architecture/MAAS_Bare_Metal_Lifecycle_v1.md`, `doc/architecture/Provisioning_BareMetal_MAAS_API_Boundary_v1.md`, `doc/architecture/Node_Agent_Spec.md`, `doc/architecture/Kubernetes_Runtime_Reconcile_Repair_v1.md` | Provider optimization and lab-specific reports remain implementation or historical references. |
| Documentation portal governance | `doc/PORTAL_SYNC.md` | `doc/product/GPUaaS_Documentation_and_Developer_Portal_Docusaurus_v1.md`, `doc/architecture/platform-foundation/Documentation_Archive_And_Portal_Refresh_Plan_v1.md`, `packages/docs/static/portal/source-doc-inventory.json` | Portal roadmap pages are portal-current only after `make docs-portal-check` passes. |

## Superseded And Historical Handling

| Document | Classification | Replacement / authority |
| --- | --- | --- |
| `doc/architecture/Platform_Shared_Services_Model_v1.md` | `superseded` | `doc/architecture/platform-foundation/Platform_Shared_Services_Model_v2.md` |
| `~/Downloads/sec-review/Core42_GPUaaS_Cloud.pdf` | `superseded review input` | `doc/architecture/platform-foundation/Security_Architecture_Current_State_v1.md` |
| `doc/governance/Agent_Work_Queue.yaml` | `historical-reference` for active execution | `.fairway/platform-foundation-implementation-track.yaml` |
| `doc/governance/archive/*` | `historical-reference` | Active Fairway queues under `.fairway/` |
| `doc/operations/evidence/*` | `historical-reference` unless explicitly promoted | Current readiness and release evidence docs under platform-foundation and operations runbooks |

## Portal Refresh Rule

Before updating `packages/docs/docs/**`, check this map and the classification
artifact. A portal page may link a migration, future-state, or historical doc
only when the page labels that status explicitly and also links the current
authority.