Architecture

This column explains the trade-offs: which boundaries end up held only by convention if governance stays inside the agent process, if tenant filtering stays only in application WHERE clauses, or if enterprise code is statically imported into the core. Each boundary should sit on a mechanism you can check.

Start with the technical architecture overview, then drill into topic pages.

Articles in this column

Map and structure

• Technical architecture overview
• Layered architecture: client to data
• Why governance must be out-of-process
• Three abstractions: capabilities, roles, and triggers
• Trigger component chain

Isolation and boundaries

• Multi-tenant isolation and Postgres RLS
• Open-core seam design

Engineering conventions

• Effect architecture conventions