RIR isn’t a flag system ..it records the resolved outcomes (mode/runtime/entitlements), including source + reason, then promotes that to a contract that CI can enforce. The attestation proves the shipped artifact corresponds to that contract. It was born from a real drift bug: dev had ?builder=true, native didn’t .. same code, different behavior. RIR makes those differences explicit and enforceable.
keen919•1h ago
Why: stops “works in dev, breaks in build” drift by turning runtime behavior into something CI can verify.
Demo:
Download release-bundle.zip from the GitHub Release assets
Unzip
Run ./demo.sh (Linux/macOS) or demo.cmd / demo.ps1 (Windows)
It runs: validate → attest → verify → opens the UI in demo builder mode.