Documentation Routing

NON-NORMATIVE. Use this page to find the right source quickly. Normative authority remains in root governance docs.

Use This When You Need

Need	Primary doc	Why this is the source
Public product overview	public/overview.md, public/what-is-morphism.md	Public-facing orientation for what Morphism is and how the docs are split by audience.
External adoption quickstart	public/quickstart.md	Canonical adoption guide for installing the toolkit, running the first audit, and wiring optional CI/MCP integration.
Canonical governance rules	../AGENTS.md, ../SSOT.md, ../GUIDELINES.md	These define authority, scope, invariants, and enforceable git/policy rules.
Copy-paste commands	reference/test-commands.md	Central command cookbook for validation and governance scripts.
Platform architecture	architecture/overview.md	Canonical runtime/module overview for the monorepo’s active implementation.
Research and mathematical foundation	research/comprehensive-overview.md	Long-form research-backed explanation of the problem space, theoretical basis, and competitive landscape.
External services and provider setup	reference/integrations/README.md	Consolidated entrypoint for provider ownership, service status, and auth setup notes.
Phased execution priorities	operations/roadmap-phases.md	Current staged implementation prompts and rollout sequencing.
Baseline required checks	../AGENTS.md	Short required TypeScript and Python validation commands.
Meaning of doc metadata and doc types	standards.md	Canonical taxonomy (normative, operational, etc.) and frontmatter schema.
Meaning of governance invariants and protocol	governance/morphism-kernel.md	Canonical definitions for I-1..I-7 and Read-Verify-Execute.
Branch/commit conventions and naming	../GUIDELINES.md, ssot/atoms/branch-types.md	Workflow conventions and canonical branch prefix list.
Operational workflows/prompts	operations/workflow-prompts.md, operations/prompts/README.md	Reusable workflow templates and session prompt references.
Proof review requirements	governance/proof-review-workflow.md	Review checklist and approval flow for formal proof work.
Session continuity and backlog	operations/current-handoff.md, operations/deferred-work.md	Current handoff state and the single deferred-work backlog.
Deploy/incident/repo operations	runbooks/	Runbooks for deployment, drift handling, incident response, and normalization.
Repair the docs system itself	governance/audits/documentation-remediation-spec.md	Active remediation plan for authority boundaries, target structure, metadata, and enforcement.
See the current docs inventory and move plan	governance/audits/documentation-inventory.md, governance/audits/documentation-migration-matrix.md	Concrete Phase 1 fact base and migration table for the docs cleanup.
Contributing process	../CONTRIBUTING.md, operations/onboarding.md	Setup, first PR checklist, and contributor workflow.
Docs-local contribution workflow + pruning	operations/docs-contributing.md	Docs-native contribution path, branch hygiene, and pruning commands.
CI failures and required check triage	runbooks/ci-triage.md	Maps check names to workflows, local repro commands, and first-response actions.
Release execution + evidence	../.morphism/workflows/release-readiness.md, governance/release-playbook.md	Operational release sequence plus the docs evidence required before tagging.
Incident execution + evidence	../.morphism/workflows/incident-response.md, runbooks/incident-response.md	Live incident handling path plus the authoritative docs that must be updated before merge.
.morphism/ consumer compatibility	../.morphism/docs/README.md	Narrow exception for .morphism/ consumer notes only; not live platform truth.
Archived historical docs	../archive/docs/README.md	Historical material only; do not use as the default source for current guidance.
“Where is X documented?” index	README.md, governance/index.md	Canonical docs entrypoints by domain.

Fast Path

1. Start with this file to route the request.
2. If the topic is policy/invariants, go to root governance docs first.
3. If the topic is execution, go to runbooks or test commands.
4. If pages disagree, treat root governance docs and canonical docs as authority.

Notes For Contributors

• Avoid duplicating normative rules in operational docs; link back instead.
• Prefer adding links to this page and existing indexes over creating parallel guidance.
• When release or incident behavior changes, route through the workflow docs and run python scripts/docs_contract.py --check --working-tree.
• Do not route contributors to .morphism/docs/ or archive/docs/ for current platform truth unless the request is specifically about consumer compatibility or historical context.