[GOVERNANCE] Implement Semantic Ambiguity Gate (fail-closed, quarantine + exile)

[Tommy-Raven]

Governance phase

Phase 2 (Validator enforcement & CI integration)

Blocking status

Blocking (must be resolved before proceeding)

Change summary

Requirements

Add to scripts/validate_semantic_ambiguity.py implementing:

fail-closed

error label exactly: Semantic Ambiguity

quarantine the registry under: directive_core/artifacts/audit/semantic_ambiguity_quarantine.jsonl

enforce automatic exile: ambiguous artifacts removed from ingestion candidates

Wire it to run before:

ingestion order enforcement

anchor validation

precedence enforcement

Add tests:

tests/test_semantic_ambiguity_gate.py

Must be deterministic and pass in CI

Update Constitution:

Add a binding “Semantic Ambiguity Gate” section (provided verbatim)

Update ingestion order everywhere it is defined to:

-Terminology

-Agents

-Constitution

… (rest unchanged)

Acceptance criteria

• CI fails on any ambiguous governance artifact with a typed failure including:

• Type: semantic_ambiguity

• error_label: Semantic Ambiguity

• Quarantine registry is append-only JSONL and is .gitignored

• All governance enforcement tests pass

Motivation / rationale

ambiguity is a security vulnerability, not am aesthetic issue. Treat like the plague and exterminate it!

Affected directive_core scope

directive_core

Invariants impacted

-Terminology

-Agents

-Constitution

Validator impact

new ambiguity gate enforced pre-validation and pre-ingestion

Mandatory confirmations

• I confirm this change does not introduce ambiguous interpretation.
• I confirm this change is aligned with SSWG_CONSTITUTION.md.
• I confirm validator enforcement will fail on mismatch.

---

@codex