Layer 6 — Connector & Integration Layer
Connector registry, base connector telemetry, production connector partition, beta/demo connectors, and external ERP/CRM systems.
The registry-driven external connectivity surface of the seven-layer code architecture. A canonical connector registry is the single source of truth for what ships and how it is wired: the production partition (NetSuite, Salesforce, Business Central, HubSpot, ShipStation — production-credential-tested, with Oracle at beta), plus demo-mode and stub connectors, all clearly labeled by source-level status declarations that CI audits against the code. Connectors in this layer are purely executors, not decision-makers — writes are gated upstream in Layer 3 and validated by Layer 5 before a connector ever executes them.
Questions this layer answers
- Which connectors are production, beta, demo, or stub?
- What is the connector registry source of truth?
Ask them live on the Code Architecture Dashboard — click the connector band of the infographic.
Documentation & evidence
- Production vs demo guide — the honest partition between credential-tested and scaffolded connectors
- Proof cards (per production connector): NetSuite · Salesforce · Business Central · HubSpot · ShipStation · Oracle (beta)
Related layers
- Layer 3 — Core Application Services — dispatches governed actions to these executors
- Layer 5 — Governance & Safety — validates every outbound write
- Layer 7 — Data, Evidence, and Publishing — publishes the connector status evidence
Last refreshed: 2026-07-06