# Architecture Map

Status: current navigation map, 2026-09-11. This document summarizes and links; it owns no detailed architectural definition. Every detailed meaning belongs to the canonical document named below.

## Orientation

The [product definition](../product/definition.md) establishes Idiosyncrasy's business-adaptive purpose, four principles and ownership promise. Its [composition and extensibility](../product/definition.md#composition-and-extensibility) section defines Engine as a reusable execution responsibility/capability, not a class, module, database subsystem or service. It also owns the capability/application taxonomy and seven-question architectural test.

The [core object model and authority](../architecture/core-object-model-and-authority.md) defines the cross-cutting distinctions between actual object reality, definitions, derived State, history, workflows and explicit authority. The [object/type contract](objects-and-types.md) defines the one foundational addressable model. The [business-model contract](business-model.md) defines its connected Graph, relationships and Business DNA. No engine below owns a separate data universe. This is a summary of those contracts, not an alternative storage model.

## Conceptual Layer Routes

The eight layers from the architecture sources are views of concerns, not deployment tiers. Their details are authoritative only at the linked destinations.

| Source layer | Definition route |
|---|---|
| Cross-cutting object model and authority | [Core object model and authority](../architecture/core-object-model-and-authority.md) |
| A. Identity and tenancy | [Identity and governance](identity-and-governance.md) |
| B. Business model | [Objects and types](objects-and-types.md), [Business DNA and relationships](business-model.md), [semantics](semantics.md) |
| C. Business data | [Universal objects](objects-and-types.md), [shared business representation](business-model.md) |
| D. Knowledge | [Knowledge](knowledge.md), with platform-wide [retrieval](retrieval.md) |
| E. Events and workflows | [Time/events](time-and-events.md), [workflow and scheduling](workflows-and-automation.md) |
| F. Presentation | [Views and content](views-and-content.md) |
| G. Integrations | [Communication and integrations](communication-and-integrations.md) |
| H. Intelligence | [AI](ai.md), with [analytics and evolution](analytics-and-evolution.md) |

## Responsibility Map

Fourteen responsibilities are preserved. Their implementations may be combined or separated as justified; the [canonical engine definition](../product/definition.md#composition-and-extensibility) prohibits inferring fourteen rigid software units from this list.

| Responsibility | Canonical contract |
|---|---|
| Identity/Permission | [Identity and governance](identity-and-governance.md) |
| Object/Data | [Objects and types](objects-and-types.md) |
| Relationship | [Business model](business-model.md) |
| Event | [Time and events](time-and-events.md) |
| Workflow | [Workflows and automation](workflows-and-automation.md) |
| Knowledge | [Knowledge](knowledge.md) |
| Content | [Views and content](views-and-content.md) |
| View/UI | [Views and content](views-and-content.md) |
| Communication | [Communication and integrations](communication-and-integrations.md) |
| Integration | [Communication and integrations](communication-and-integrations.md) |
| Analytics | [Analytics and evolution](analytics-and-evolution.md) |
| Automation/Scheduling | [Workflows and automation](workflows-and-automation.md) |
| AI/Intelligence | [AI](ai.md) |
| Evolution/Optimisation | [Analytics and evolution](analytics-and-evolution.md) |

Structured retrieval is a platform-wide contract in [retrieval](retrieval.md), not an AI-only feature or a mandatory fifteenth module. Rules, policies, constraints, goals and decisions are defined in [semantics](semantics.md), not competing execution/storage foundations.

## Composition and Next Reads

The [equipment-servicing scenario](../product/capabilities.md#equipment-servicing-example) demonstrates composition from Objects + Types + Relationships + Knowledge + Workflow + Communication + Views, without requiring an EquipmentServicingEngine. The [enquiry scenario](../product/capabilities.md#website-enquiry-example) demonstrates shared objects across forms, CRM, sales, tasks, communication and analytics.

Consult the [roadmap](../product/roadmap.md) for the first executable milestone and Spearmint Design process, [implementation architecture](../implementation/architecture.md) for the chosen modular-monolith mechanisms, and [status](../implementation/status.md) for evidence. [D01-D10 are settled](../governance/decisions.md); implementation details are not new architecture decisions. Original and final-decision material is traced in the [source ledger](../governance/source-map.md).