Layer 5 — Governance & Safety
Governance checkpoints for policy, PII detection, outbound governance, tenant isolation, approval queues, and audit redaction.
The vertical safety rail of the seven-layer code architecture. This layer does not sit “after” the others — it is invoked inline at the decision points in Layer 3 and Layer 4, before any write reaches Layer 6. It covers policy checkpoints, PII/DLP detection, outbound governance validation on every egress path, tenant isolation invariants, the approval-queue persistence surface, and audit redaction. The governing invariant: no AI-proposed change reaches an ERP connector without traversing this layer. This governance-first posture is the platform’s core differentiator — see Oracle NSIP vs SuiteCentral 2.0.
Questions this layer answers
- What prevents unsafe AI or data actions?
- Where does human approval happen?
Ask them live on the Code Architecture Dashboard — click the governance rail on the right side of the infographic.
Documentation & evidence
- Production vs demo guide — which safety surfaces are production-enforced
- Proof card: DLP service
- Proof card: Governance service
- Proof card: Guarded write / ownership enforcement
- Proof card: Sync Error Assist
- Live governance evidence: SOC 2 Compliance Dashboard
Related layers
- Layer 2 — HTTP-API Edge — tenant isolation starts at the edge; this layer enforces it downstream
- Layer 3 — Core Application Services — hosts the approval queue this layer’s policy gates feed
- Layer 6 — Connector & Integration Layer — the boundary this layer protects
Last refreshed: 2026-07-06