Discipline — the outer crust: server-side enforcement that makes every other layer true

Present this layer first. It is the wrapper that encloses and enforces everything inside it.

What it is

wikiTaTa holds every interaction to strict rules, server-side. Required behaviours actually happen. Nothing depends on an agent remembering a rule or choosing to follow it.

How it shows up

• Turn-by-turn hooks. Every agent turn passes through hooks. They inject the rules, check state, and block a write that breaks one.
• Mandatory rules. A user can tune rules from block to remind, but a mandatory rule can't be switched off.
• Lanes and closure. Parallel agent sessions declare intent before they write. Merges go through a lander that refuses overlapping code. A task ends in one of exactly two states: closed with evidence, or open and announced.
• Secrets. Keys live only in the vault and the consuming process's memory. Agents never see plaintext.

Why it matters

This layer is what makes the inner layers trustworthy. It makes the efficiency real, the storm review honest and multi-tenancy safe.

"I'm not just offering features — I enforce the discipline that guarantees them."