Skip to main content
← Back to Docs

Non-Compliant Patterns

This page defines implementation patterns that violate the fail-closed contract.

INV-1INV-2INV-3INV-4INV-5INV-6

Spec Drift Warning

Changes to implementation that violate invariant mappings invalidate compliance with v1.0. Implementations MUST preserve invariant-to-component, invariant-to-artifact, and invariant-to-verification-step mapping.

Compliance Assertion

  • Defines implementation states that SHALL fail compliance review.

Non-Compliance Results In

  • Any listed pattern invalidates v1.0 compliance.
  • Deviation from detection rules invalidates audit conclusions.

Explicitly Non-Compliant Patterns

Invariant Mapping: ALL INVARIANTS

  • Fail-open fallback is non-compliant.
  • Eventual consistency replay prevention is non-compliant.
  • Any bypassable execution path is non-compliant.
  • Missing audit chain or denial records is non-compliant.
  • Silent truncation of parameters is non-compliant.
  • Unsigned or unverifiable approval envelopes are non-compliant.

Detection Requirements

Invariant Mapping: ALL INVARIANTS

  • Compliance review MUST fail if any execution endpoint is reachable without Gate.
  • Compliance review MUST fail if replay detection cannot guarantee strong consistency.
  • Compliance review MUST fail if denials are not logged with attributable audit records.
  • Compliance review MUST fail if executed parameters differ from approved parameters without an allowed narrowing rule.

Verification Linkage

INV-2

Artifact: audit-chain-001.json

Check: Silent truncation or parameter drift is detectable

Verification step: verify.sh: INV-2

INV-6

Artifact: verification walkthrough

Check: Direct bypass is rejected; bypassable path is detectable

Verification step: Adversarial scenario 3