Architect

Documentation status: guide — see Maturity and evidence.

Jump straight to the task

• Layer boundaries
• Distributed architecture
• Services and communication
• DDD and context maps

Mission

Define application boundaries, Runtime topology, integration contracts, persistence, security, and evolution rules.

Structural decisions

• what belongs to the conceptual model and what remains a projection;
• local, remote, or hybrid Runtime use;
• service boundaries and publication responsibilities;
• isolation, multi-tenancy, and trust domains;
• persistence and synchronization strategy;
• compatibility, migration, and observability.

Principles

Separate business invariants from deployment choices. Prefer explicit capabilities, versioned contracts, and replaceable projections.

Private implementation details must not become architectural dependencies.

Read next

• Conceptual/Architecture-overview.md
• Architecture/home.md
• Architecture/Distributed-Architecture.md
• Bindings/home.md
• DevOps/home.md