What it is
DEC is the LockJaw enforcement core. It keeps compartments, doctrine, audit, and fail-closed refusal from drifting into operator narrative or product variation.
DEC / Truth Stack
Deterministic Enforcement Core
Deterministic enforcement of non-bypassable rules.
DEC is the LockJaw enforcement core. It keeps compartments, doctrine, audit, and fail-closed refusal from drifting into operator narrative or product variation.
What problem it solves
Ordinary systems weaken over time. Doctrine drifts, controls diverge by deployment, and supposedly hard guarantees become profile- or operator-dependent.
What it does
- Enforces the core behavior boundary for compartments, audit, sealing, and refusal.
- Provides the narrow cryptographic and enforcement spine shared across LockJaw deployments.
- Supports doctrine profiles that tighten posture without forking the core.
What it does not do
- It does not become a customer-specific edition or weaker product variant.
- It does not exist for workflow convenience, UI-first operations, or arbitrary extensibility.
- It does not allow hidden bypasses, debug security paths, or downgrade modes.
Who it is for
- Organizations that need one certified security core across different operational postures.
- Programs that cannot tolerate code forks, silent downgrades, or product-tier drift.
Where it fits
DEC sits beneath the rest of LockJaw. It is the hostile enforcement substrate, not a sibling convenience tool.
Typical deployment context
Used where the core security engine itself must stay constant while doctrine tightens by environment.
Primary source docs
- Executive positiondec/docs/foundation/executive_position.md
- Explicit non-goalsdec/docs/non_goals.md