claim-boundary-register.md

Claim Boundary Register

This register separates measured evidence, synthetic validation, design intent, planned work, and explicit non-claims.

Measured Bench Evidence

Claim	Status	Boundary
0.31 ms arbitration-cycle timing	Measured	BGC-BM-RUN-001 sealed baseline only
420 ns GPIO interdiction response	Measured	DSLogic CH0 to CH1, event 131
50 ns GPIO pulse width	Measured	Pulse duration only

Synthetic Validation

Claim	Status	Boundary
F1 = 1.000	Synthetic validation	5,000 adversarial scenarios, not bench timing
0 false positives	Synthetic validation	Autoresearch-derived harness
0 false negatives	Synthetic validation	Autoresearch-derived harness

Generated Software Evidence

Claim	Status	Boundary
Trajectory-level evidence capture	Implemented and merged	PR #2 baseline; software evidence layer only

Design Intent / Planned Evidence

Item	Status	Boundary
Verification harness	Proposed	Must generate run logs, verdict JSON, and SHA ledger before external claim
Watchdog path	Proposed	Requires BGC-BM-RUN-002 before timing can be cited
Demo shield/interposer	Planned	Must remain separate from sealed baseline until captured

Explicit Non-Claims

• Blackglass does not claim solved AI alignment.
• Blackglass does not claim deployment at a federal site.
• Blackglass does not claim the sealed baseline is fail-closed under silent telemetry.
• Blackglass does not migrate baseline timing claims onto modified firmware.
• Blackglass does not treat authored documents as evidence without generated or measured artifacts behind them.