Platform Overview

The platform is intentionally horizontal, so the docs need a clear split between public surfaces and runtime internals.

Public Technical Surfaces

• docs.* is developer-facing reference and architecture.
• developer.* is the portal entry point for technical users.
• partner.* is for deeper third-party and IoT integrations.
• status.* is public operational communication.
• help.* stays user-facing and editorial.

Core Runtime Boundaries

• apps/nomos_intent_server is the write API and OpenAPI source.
• apps/nomos_read_server is the read/query surface.
• dart_packages/co2/domains/* holds bounded contexts.
• dart_packages/co2/intents/workflow_intents_v1 defines the intent contract.
• dart_packages/co2/policy/policy_v1 now composes policy slices rather than a single router god object.

Docs Strategy

The docs architecture mirrors the platform architecture:

• generated technical facts belong in web/docs
• hand-authored user guidance belongs in web/help
• internal engineering notes belong in repo-root docs/

That keeps the public docs sites useful without creating three competing sources of truth.