You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build the runtime Policy framework that ADR 005 ("Doctrine and Policy Separation") specifies. Policies are adoptable strategic choices, distinct from doctrine, which is universal and CI-enforced. The framework lets a solution declare which Policies it adopts and evaluates them at runtime with auditable evidence.
Why
ADR 005 distinguishes doctrine (universal axioms, CI-enforced) from policy (adoptable strategic choices). Doctrine is already enforced via test_*.py files in core/doctrine/. Policy has no runtime mechanism — it is currently a written ADR with no enforcement. This Epic closes that gap.
What
Build the runtime Policy framework that ADR 005 ("Doctrine and Policy Separation") specifies. Policies are adoptable strategic choices, distinct from doctrine, which is universal and CI-enforced. The framework lets a solution declare which Policies it adopts and evaluates them at runtime with auditable evidence.
Why
ADR 005 distinguishes doctrine (universal axioms, CI-enforced) from policy (adoptable strategic choices). Doctrine is already enforced via
test_*.pyfiles incore/doctrine/. Policy has no runtime mechanism — it is currently a written ADR with no enforcement. This Epic closes that gap.Scope (in)
Scope (out)
Decomposition
Walking skeleton: a single Policy is defined, applied at runtime to a use case, and produces accept/reject with evidence.
Likely splits into walking skeleton, composability, audit evidence, docs. Deferred until pick-up.