The named layers of the system — each a place with a boundary, where something crosses, is transformed, or is concluded. A layer is a role in the architecture, not a physical location (that's a zone) and not a technique applied across it (that's a method).
Every concept tagged into this group, drawn from across the categories. A concept can belong to more than one group.
A deliberate boundary for data in and out: a controlled front door for ingestion (inbound) and a publication layer for what leaves (outbound).
An airlock is the small chamber between two spaces that must not mix — a spacecraft and space, a cleanroom and the corridor. It works by two rules: the two doors are never open at the same time, and whatever passes is checked or cleaned in…
The layer everyone mistakes for magic. When AI gives a good answer, it feels like the model reasoned its way there. But the reasoning is only as good as what sits beneath it: the context it can reach, the memory across sessions, the rules…
The federation mechanism: when individual and team systems work together, they never read each other directly. What crosses the boundary passes through a publishing layer that validates on the way out and on the way in — the same…
How you stop the model sounding like a model: a standing voice corpus distilled from real, unpolished sources (sent mail, messages) plus an explicit anti-AI banned-words list. The key rule — AI-generated text is the anti-example, never the…
← Back to all concepts.