v1.3.0 — Shield Interfaces Frozen & Protection Mode Locked

🔐 Adamantine Wallet OS v1.3.0

Shield Interfaces Frozen & Protection Mode Locked

v1.3.0 completes the hardening of the Adamantine execution boundary.

This release freezes Shield v3 structure, locks deterministic posture semantics, and seals governance enforcement.

⸻

🛡 Shield v3 Hardening
• Strict shield_bundle_version + per-layer layer_version
• Canonical required_layers ordering enforced
• Deterministic signal sorting (layer, signal_id)
• Duplicate or missing layer signals denied
• External reason registry mandatory (deny-by-default)
• Structural adapter failures mapped to stable EQC reasons
• Deterministic size caps + toxic input rejection

Shield evidence can only strengthen denial. It can never weaken it.

⸻

🔐 Protection Mode (Posture Output)

Execution responses now include:

legacy | minimal | full

legacy — Q-ID invalid/missing or protected call not requested
minimal — Q-ID valid but Shield/Oracle incomplete
full — Q-ID + Shield v3 + Oracle v3 fully validated

Protection mode semantics are regression-locked.

⸻

🧪 Deterministic Guarantees
• Proof pack fixtures frozen
• Manifest hashes locked
• Shield “never weaken deny” invariant enforced
• Protection mode matrix regression tests
• ≥90% coverage required

Identical input → identical output.

⸻

🔒 Status

Execution boundary hardened.
Shield interfaces sealed.
Security posture locked.

From this version forward, contracts do not drift.