Skip to content

Latest commit

 

History

History
49 lines (36 loc) · 2.66 KB

File metadata and controls

49 lines (36 loc) · 2.66 KB

Blackglass Evidence Index

Public evidence index for Blackglass Continuum runtime-assurance artifacts: measured bench results, claim boundaries, generated verification outputs, and procurement-safe summaries.

This repository is a sanitized proof shelf. It is intended for prime contractors, APEX counselors, DARPA/DIU reviewers, advisors, and technical evaluators who need a fast, bounded read of what Blackglass claims, what is measured, and what remains pending.

It does not contain raw private traces, live federal screenshots, secrets, source-controlled credentials, or unredacted procurement material.

Core Positioning

Blackglass Continuum builds deterministic runtime assurance, hardware safety boundaries, and audit-grade evidence systems for autonomous agents and mission-critical infrastructure.

Evidence Snapshot

Claim Anchor Boundary
Hardware arbitration-cycle timing 0.31 ms Measured sealed baseline only
GPIO interdiction response 420 ns DSLogic CH0 to CH1, event 131
GPIO pulse width 50 ns Event pulse duration only
Governance threshold 0.05V Tri-state variance gasket
Synthetic persistence validation F1 = 1.000, 0 FP, 0 FN across 5,000 scenarios Synthetic validation, not bench timing
Trajectory-level evidence capture Merged into baseline, PR #2 Software evidence layer, not hardware timing
Federal posture CAGE 17TJ5, SAM active, SPRS 110/110 Verify live before submission
Patent anchor U.S. provisional 63/992,753 Utility/PCT deadline 2027-02-27

Public Documents

Document Purpose
Evidence Density One-Pager One-page summary of current proof anchors and claim boundaries
Claim Boundary Register What is measured, synthetic, planned, or explicitly not claimed
DICE Abstract Public Draft Public-safe DARPA DICE abstract candidate
Runtime Assurance Positioning Market and technical framing

Claim Discipline

  • Generated evidence beats authored evidence.
  • Existing sealed manifests are not mutated to append new hashes.
  • BGC-BM-RUN-001 timing belongs only to the sealed baseline.
  • Trajectory-level evidence capture is merged into the software baseline; it does not extend hardware timing claims.
  • Watchdog firmware requires BGC-BM-RUN-002 before timing can be cited.
  • Synthetic validation numbers remain labeled synthetic.
  • Blackglass does not claim solved alignment; it claims enforceable, auditable control boundaries.

Contact

Blackglass Continuum LLC
Aurora, Colorado
colemanwillis@blackglasscontinuum.com