Part 5 of 12 · 2 min read
A gate that fails closed, and reruns itself when something drifts
Checking evidence against the tier at release time, and re-checking whenever the tier, domain or evidence changes, turns compliance from a one-time memory into a standing CI step.
Think of a pre-flight checklist that a pilot runs again, in full, whenever the plane, route or crew changes. It is not a checklist ticked once at delivery and trusted forever after.
A compliance gate derives a system's required evidence from its tier and blocks the release if anything is missing, and a drift check re-runs that same gate whenever the tier, domain or evidence changes. That means the gate stays accurate instead of going stale.
A worked example. Of the ten sample systems, 4 pass the gate outright; the other 6 fail with named reasons -- cv-screener-no-oversight fails for one missing item (human_oversight), internal-summariser-undocumented fails for two (model_card, retention_policy), and both nudifier and emotion-scoring-hr fail immediately as prohibited, before evidence is even checked. Removing human_oversight from a passing system's manifest and re-running drift() reports exactly "evidence removed: human_oversight".
The key lines. From code/mini-compliance/compliance.py:
# from code/mini-compliance/compliance.py
def gate(s: System):
tier = classify(s)
if tier == "prohibited":
return False, ["prohibited practice: do not ship"]
reasons = [f"missing evidence: {o}" for o in required(tier) if not s.manifest.get(o)]
return (not reasons), reasons
Read it as: a prohibited tier returns immediately with one fixed reason, before the evidence loop ever runs. No amount of paperwork can turn a prohibited practice into a pass. That is the point of checking that case first.
Policy as code, compliance gate
- Policy as code: rules written as executable checks.
- Compliance gate: a release step that blocks until required evidence exists.
Example: gate() returning (False, ["missing evidence: two_person_signoff"]) for loan-triage is a to-do list a release engineer can act on immediately, not a vague "not compliant" verdict.