Use Shadow Mode to test learned-policy release controls.

Architecture

• Feed representative policy, action, device, and controller identifiers into the normal gate.
• Use real approval, revocation, expiry, and replay logic against isolated test state.
• Route allowed decisions to a shadow sink instead of a hardware publisher.
• Write evidence with hardwareSignalSent=false for every shadow decision.

Test matrix

• Exact match, altered policy digest, and renamed release.
• Wrong device or controller configuration.
• Expired, replayed, and revoked authorization.
• Unavailable API or database with an expected fail-closed result.

Reading results

Compare expected decisions with evidence, inspect unexplained denials, and verify that no code path can reach hardware from shadow execution. The RLSOK repository demonstrates the release, permit, gate, and evidence concepts that can anchor this exercise.

Limitations

Shadow execution cannot predict all physical behavior and does not validate policy performance. Move toward hardware only through the team's existing safety and operational process.

Continue the architecture review

Ready to map the release path? Request a Shadow Audit.