Plan coverage

This index maps all 31 sections of the supplied “intrnl.cloud v1 — system architecture and implementation plan” into maintained documentation. Section numbers refer to the original plan; page headings use descriptive names.

Section coverage

1. Introduction — Product definition.
2. Decisions and open gates — Locked architectural decisions.
3. Domains and TLS — One important security refinement: separate app and control-plane domains.
4. System architecture — Top-level architecture.
5. Trust zones — Trust zones.
6. Control plane — Central control plane.
7. Organization tenancy — Organization tenancy.
8. Identity and sessions — Identity architecture.
9. AI and MCP — AI and MCP architecture.
10. Source control — Source-control architecture.
11. Sandboxed builds — Build architecture.
12. Runtime contract and SDK — Runtime contract.
13. Runtime clusters and previews — Runtime-cluster architecture.
14. Ingress and egress — Ingress, network, and egress.
15. Access policies and WAF-lite — Access policy and WAF-lite.
16. Databases and recovery — Data architecture.
17. Secrets and integrations — Secrets and integrations.
18. Deployments and approvals — Deployment pipeline.
19. Governance and ownership — Governance.
20. Economics and quotas — Economics and metering.
21. Core data model — Core data model.
22. APIs and protocols — API architecture.
23. Observability and audit — Observability and audit.
24. Threat model — Security threat model.
25. Organization pilot — Organization v1 pilot.
26. Codebase organization — Codebase organization.
27. Implementation plan — all ten phases, each with full scope and exit criteria.
28. Test strategy — Test strategy.
29. Operating model — Operational model.
30. Scope and non-goals — Explicit v1 non-goals.
31. Definition of done — v1 definition of done.

Editorial treatment

Extraction was checked against the supplied plan on 2026-09-21: all 31 sections, all ten implementation phases and their exit criteria, and all 28 definition-of-done requirements are preserved. The maintained pages are self-contained; the temporary root-level project-plan.md is not required to build or use this site.

All original major sections and phase exit criteria are retained. Citation tokens are replaced by official references. Section numbers are removed from subheadings. The artifact contract date is aligned with the illustrative runtime configuration date; neither declares a shipped version. Signature verification precedes workload startup. Migration availability is conditional on schema compatibility. Customer and industry examples are generalized. Enterprise system integrations remain future scope.

The decision register, glossary, contributor guide, and operational runbooks add navigation and implementation guidance. Runbooks are procedure specifications pending implementation-specific commands and rehearsal. No additional feature is promoted into v1, and no phase is marked complete.