Layer 3 — Core Application Services
Integration orchestration, configuration, WorkflowCentral execution, ownership resolution, approval queues, audit logging, and module metrics.
The engine room of the seven-layer code architecture: this layer converts operator intent (from Layer 2) into governed, auditable actions against ERP connectors (Layer 6). The human-in-the-loop approval queue lives here — high-risk AI-proposed changes are enqueued for operator approval at this layer, never executed inline. Connector writes are gated here through ownership resolution before any connector executes them.
Questions this layer answers
- What services form the core runtime?
- How are approval queues and audits connected?
Ask them live on the Code Architecture Dashboard — click the third layer of the infographic.
Documentation & evidence
- Source-of-truth model — how ownership resolution decides which system wins
- Proof card: WorkflowCentral operator
- Proof card: Flow templates
- Proof card: Audit service
Related layers
- Layer 2 — HTTP-API Edge — the validated requests this layer acts on
- Layer 5 — Governance & Safety — invoked inline at this layer’s decision points
- Layer 4 — AI & Intelligence — whose validated outputs this layer executes
- Layer 6 — Connector & Integration Layer — the executors this layer dispatches to
Last refreshed: 2026-07-06