# Tier 1 - Executive Decision Brief (Claims & Boundaries)

Rook executive-facing claim and boundary memo.

Version: v2.7 (537 Pack)  
Date (UTC): 2026-02-16T10:29:39Z

## Boardroom Decision
Rook can be presented externally as a compliance-grade autonomous runtime governance system.

Boundary:
- Allowed: compliance-grade autonomous runtime governance.
- Blocked: compliance-certified autonomy.

## Operational Definition (External Use)
In this memo, `compliance-grade` means the following runtime baseline is present and replayable:
- `compliance-grade` is an internal operational baseline published for external scrutiny; it is not a term defined by regulation or certification frameworks.
- Policy-gated execution before side effects.
- Principal and release-proof verification before execution.
- Tamper-evident evidence continuity (intent, result, chain, anchors, checkpoints).
- Fail-closed behavior when any mandatory gate degrades (`deny`/`defer`).
- Operator-gate pass/fail artifacts that can be independently reviewed.

This term does not mean:
- External compliance certification.
- Guaranteed conformity to any specific regulation unless separately attested.

## Problem Rook Solves
Autonomous operations fail commercially when teams cannot prove:
1. Who authorized an action.
2. Which approved release context it ran under.
3. Whether controls failed closed when risk signals degraded.

Rook converts those failure points into a replayable evidence path.

## External Claim Language
Primary line:
- "Rook operates with compliance-grade autonomous runtime governance: policy-gated execution, principal/release verification, and replayable cryptographic evidence continuity."

Mandatory qualifier:
- "This is compliance-grade runtime governance, not external compliance certification."

Never say:
- "compliance-certified"
- "regulator-certified"
- "guaranteed legal compliance"

## Quick Glossary (External)
- `compliance-grade`: runtime control baseline with replayable evidence.
- `compliance-certified`: external third-party certification outcome (not claimed here).
- `operator gate`: pre-claim control check that must pass before external claim use.
- `principal`: authenticated actor identity bound to a decision.
- `release-proof`: evidence that execution maps to an approved release context.
- `proof capsule`: claim + verify command + expected pass signature + hash anchor.
- `chain/anchor/checkpoint`: continuity controls for tamper-evident evidence lineage.
- `fail closed`: mandatory control failure causes `deny`/`defer`, not silent proceed.
- `architecture-supported`: designed capability; deployment proof may still be required.
- `deployment-proven`: capability evidenced in runtime artifacts for the target deployment.

## Industry-Relevant Risk Mapping
Rook is designed for high-impact domains where authorization mistakes become safety, financial, or regulatory events.

Typical fit categories:
- Media and broadcast operations: live-window changes need authenticated, replayable authorization trails.
- Telecom and connectivity operations: network-impacting automation needs principal-bound control and release-proof lineage.
- Robotics and unmanned systems (civil and military): mission/configuration changes need strict step-up authorization and tamper-evident history.
- Interactive and live-service platforms: rapid rollout paths need fail-closed governance and verifiable incident reconstruction.
- Cross-border enterprise operators: policy-by-jurisdiction controls need consistent evidence outputs for audit and procurement review.

## Operator Gate Before External Claim Use
All conditions must be true:
1. Compliance probe is pass with zero hard-fail gates.
2. Strict chain/anchor/checkpoint verification passes.
3. Principal and release-proof verification are passing in runtime evidence.
4. Any media-factor authorization claim has deployment-specific proof capsules.

Hard-fail gate codes (canonical):
- `GATE.PROBE_HARD_FAIL`: compliance probe hard-fail gate present.
- `GATE.CHAIN_ANCHOR_CHECKPOINT_FAIL`: chain, anchor, or checkpoint verification failure.
- `GATE.PRINCIPAL_FAIL`: principal verification failure.
- `GATE.RELEASE_PROOF_MISMATCH`: release-proof verification mismatch/failure.
- `GATE.MEDIA_PROOF_CAPSULE_MISSING`: missing deployment proof capsule for live media-factor claim language.
- `GATE.CLAIMS_LINT_FAIL`: external claim copy fails release claims-manifest lint.

Canonical operator-gate PASS artifact fields:
- `gate_id`, `evaluated_utc`, `decision`, `hard_fail_gates`
- `hard_fail_gate_codes` (empty list for PASS)
- `principal_verification`, `release_proof_verification`
- `chain_status`, `anchor_status`, `checkpoint_status`
- `evidence_refs` (links/IDs) and artifact hash metadata

If one gate fails, external compliance-grade claim usage is paused.

## Authorization Overlay Position (External)
Rook supports policy-graded supervisor authorization overlays when organizations require human step-up for higher-risk actions.

Control position:
- Hardware factor is primary trust anchor for high/critical authorization tiers.
- Voice/video liveness signals are supporting controls, not sole trust anchors.
- Ambiguous outcomes deny/defer (fail closed).

## Certification Question Handling
If asked "Are you certified?":
- "We operate with compliance-grade runtime governance and reproducible evidence. External certification is a separate process and is not claimed here."

## Final Position
Rook is externally defensible for compliance-grade autonomous runtime governance claims when the operator gate is green and evidence is replayable.

Certification claims remain explicitly out of scope.

## if.trace Footer
Black/white:
- `if.trace` receipts verify byte integrity and provenance chain.
- `if.trace` receipts do not prove semantic correctness, safety, or legal compliance by themselves.

Canonical public surfaces (one URL per line):
https://infrafabric.io/if/trace/
https://infrafabric.io/static/trace/<shareId>
https://infrafabric.io/static/pack/<shareId>
https://infrafabric.io/static/pack/<shareId>.md
https://infrafabric.io/static/dossier/<shareId>
https://infrafabric.io/static/dossier/<shareId>/download
https://infrafabric.io/static/source/<sha256>.pdf

Hosted verification tools (one URL per line):
https://infrafabric.io/static/hosted/iftrace.py
https://infrafabric.io/static/hosted/iftrace.html

Reviewer inspectability note:
- Reviewers may inspect `iftrace.py` source directly or independently re-implement verification from the published receipt schema.

Minimal connectivity checks:
```bash
curl -fsSI https://infrafabric.io/if/trace/ | head -n 5
curl -fsSI https://infrafabric.io/static/hosted/iftrace.py | head -n 5
```
These commands confirm endpoint reachability. Content verification requires running `iftrace.py` (or equivalent verifier) against a specific receipt or pack artifact.

Quantum posture:
- `PQ receipt` means a receipt explicitly marked with a post-quantum signature profile in receipt metadata.
- Use `QUANTUM READY` only when a PQ receipt exists for the artifact under review.
- Do not claim `quantum-secure` without deployment-specific cryptographic proof.

Receipt metadata discipline:
- Include `product_id`, `product_version`, and `artifact_kind` in published manifests/receipts.

## Appendix A - Changelog
- v2.1: claim pullback enforced for architecture-supported vs deployment-proven auth overlays.
- v2.2: external narrative cleanup with no internal scaffolding.
- v2.3: final boardroom external memo with full `if.trace` footer contract.
- v2.4: footer clarity update (inspectability note, connectivity-check labeling, and PQ receipt definition).
- v2.5: added operational definition, external glossary, and concrete operator-gate artifact + hard-fail semantics.
- v2.6: standardized hard-fail gate code set and PASS artifact code-field requirement.
- v2.7 (537 Pack): added explicit claims-lint hard-fail gate and aligned memo boundary language with release claims-manifest enforcement.
