AI proposes. Humans decide. Evidence decides trust.
IX-BlackFox is a source-available AI engineering control plane for governing AI-assisted software-change workflows. It treats model output as untrusted input and puts proposed actions behind scoped capabilities, policy gates, sandbox boundaries, repository-impact analysis, content-addressed evidence, provenance, independent verification, and separate human authority.
When an AI coding agent changes a real repository, can you prove what it was allowed to touch, what changed, what evidence belongs to that exact revision, what independent verification found, which specialists reviewed it, and whether a human quorum actually authorized the next gate?
Wave 13 turns that question into an executable review-board contract above the Wave 12 certification-ready evidence package. Machine analysis is visible, but it has zero voting authority. Human approval is role-specific, revision-bound, policy-bound, externally verified out of band, and independently rechecked from the serialized package.
The locked default board requires seven distinct human roles:
- security
- QA
- systems
- safety
- operations
- manufacturing
- maintainer
Wave 13 adds:
- independent admission of a verified Wave 12 evidence package
- embedding of the exact Wave 12 ZIP inside the Wave 13 package
- nested Wave 12 reverification during independent Wave 13 verification
- non-authoritative machine advisories with
authoritative: falseandvote_weight: 0 - human reviews bound to the exact subject and board-policy digests
- separate identity and role-authority evidence references
- trusted out-of-band verification bound to the exact human-review digest
- distinct-human quorum and complete role-coverage enforcement
- subject-producer self-approval prevention
- conflict disclosure and recusal enforcement
- fail-closed reject and request-changes handling
- evidence challenges with blocking open state
- deterministic board evaluation, package construction, and bundle index
- a package-internal hash-chained review ledger
- independent semantic recomputation instead of trust in refreshed hashes
blackfox review-board build,verify, andgateoperator commands- a dedicated offline Wave 13 CI evidence workflow
The full Wave 13 contract is documented in
docs/wave13-human-machine-review-board.md.
| State | Meaning |
|---|---|
blocked |
A binding, verification, policy, dissent, conflict, challenge, or integrity rule failed. |
human_review_required |
The machine/evidence path is coherent, but the required trusted human authority is incomplete. This is the expected offline CI state. |
approved_for_next_gate |
The configured human quorum, role coverage, and trusted review-verification rules are satisfied for the exact evidence package. This is not deployment, production, certification, or operational authorization. |
A serialized review cannot promote itself by claiming externally_verified.
IX-BlackFox is not an identity provider. Trusted verification must arrive through
an integration boundary and bind the reviewer identity, role, identity-evidence
digest, role-authority-evidence digest, and exact human-review digest. Changing
the decision or its bound content after verification invalidates that binding.
The verifier reopens the package and checks:
- safe, unique ZIP paths and bounded expansion
- the exact embedded Wave 12 archive digest
- independent verification of the embedded Wave 12 archive
- reconstruction of the Wave 13 subject from that verified upstream package
- canonical review-case, advisory, review, challenge, evaluation, ledger, and bundle-index representations
- exact content digests for package entries
- machine zero-authority invariants
- human review subject and policy bindings
- external-verification context bindings to exact review digests
- role coverage, distinct-human quorum, conflict, recusal, and self-approval rules
- blocking reject, request-changes, and unresolved evidence-challenge states
- recomputed review-board disposition
- recomputed hash-chained ledger and package index
- rejection of unexpected package payloads
It does not trust self-consistent hashes alone. Corrupting the nested Wave 12 archive or changing a board disposition and refreshing outer hashes still fails independent or semantic verification.
| Module | Responsibility |
|---|---|
review_board.models |
Review roles, subjects, policies, advisories, human reviews, external verification records, challenges, findings, and dispositions |
review_board.admission |
Independent Wave 12 verification and exact Wave 13 subject construction |
review_board.policy |
Zero-authority machine analysis and fail-closed human quorum evaluation |
review_board.package |
Deterministic case, ledger, index, embedded upstream archive, and ZIP construction |
review_board.parsing |
Strict reconstruction and canonicalization of serialized Wave 13 documents |
review_board.verify |
ZIP safety, nested Wave 12 verification, trust-context binding, ledger checks, and semantic recomputation |
review_board.cli |
Build, verify, and gate operator commands |
A Wave 13 review-board package contains the bounded review surface plus the exact upstream evidence archive:
review-case.json
machine-advisories.json
human-reviews.json
evidence-challenges.json
board-evaluation.json
review-ledger.json
bundle-index.json
upstream/wave12-certification-ready-evidence.zip
The package builder uses canonical JSON, deterministic entry ordering, fixed ZIP metadata, explicit content hashes, and a deterministic ledger.
Wave 12 remains the evidence foundation directly beneath Wave 13. It collects real prior-wave and quality evidence, maps it to a bounded assurance profile, constructs a deterministic certification-ready evidence package, and reopens that archive through an independent semantic verifier.
Here, certification-ready is deliberately narrow. It means the evidence is scoped, revision bound, content addressed, mapped, checked for completeness, packaged deterministically, and independently reverified. It does not mean the repository, workflow, model, organization, or package is certified.
See
docs/wave12-certification-ready-evidence.md
for the complete Wave 12 contract.
The Wave 12 evidence profile includes bounded conceptual mappings to:
- NIST SP 800-218 SSDF 1.1
- NIST AI RMF 1.0
- NIST OSCAL Assessment Results
- SLSA 1.2
- in-toto Statement v1
These are mappings only. IX-BlackFox does not claim certification, a SLSA level, conformant OSCAL output, accreditation, an ATO or cATO, or external endorsement.
IX-BlackFox requires Python 3.11 or newer. The primary CI matrix runs Python 3.11, 3.12, and 3.13.
python -m venv .venv
.venv/bin/python -m pip install -e ".[dev]"Run the complete local quality suite:
.venv/bin/python -m ruff check .
.venv/bin/python -m mypy src
.venv/bin/python -m pytest -q
PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m compileall -q src scripts testsRun the focused Wave 13 campaign:
.venv/bin/python -m pytest \
tests/review_board \
tests/ci/test_wave13_review_board_runner.py \
tests/ci/test_wave13_review_board_workflow_contract.py \
tests/docs/test_wave13_review_board_docs.py \
-qTrust current local or GitHub Actions output, not a static README claim, as proof that checks passed.
Wave 13 consumes a real Wave 12 package. Generate the upstream package first:
PYTHONPATH=src python scripts/run_wave12_assurance_ci.py \
--root . \
--head-sha 0123456789abcdef0123456789abcdef01234567 \
--expected-status review_requiredThen build and independently verify the Wave 13 board package:
PYTHONPATH=src python scripts/run_wave13_review_board_ci.py \
--root . \
--head-sha 0123456789abcdef0123456789abcdef01234567 \
--expected-status human_review_requiredThe offline Wave 13 runner intentionally supplies zero human reviews and zero
trusted external-verification records. Its correct passing state is
human_review_required. CI proves that machine analysis cannot silently become
human authority; it does not manufacture an approval.
The Wave 13 workflow is
.github/workflows/wave13-human-machine-review-board.yml.
Build a review-board package from an explicit Wave 12 package:
blackfox review-board build \
--wave12-package .blackfox-artifacts/wave12/wave12-certification-ready-evidence.zip \
--output .blackfox-artifacts/wave13/wave13-human-machine-review-board.zipIndependently verify a serialized Wave 13 package:
blackfox review-board verify \
--package .blackfox-artifacts/wave13/wave13-human-machine-review-board.zipRequire the board to have reached the next human-authorized gate:
blackfox review-board gate \
--package .blackfox-artifacts/wave13/wave13-human-machine-review-board.zipThe review command is an alias for review-board.
IX-BlackFox is not:
- a replacement for human review or an external assessor
- a human identity-proofing service
- a qualified digital-signature service
- a production authorization or deployment authority
- a certified compliance product
- FedRAMP authorized
- an ATO or cATO issuer
- DoD approved or endorsed
- AWS approved or endorsed
- a transparency log
- a claim of formal verification or guaranteed software correctness
- an autonomous human-equivalent approval system
It is a platform-neutral, evidence-bound control plane and research prototype for making AI-assisted engineering workflows more inspectable, reviewable, identity bound, and governable. Its evidence packages can be consumed by CI, artifact storage, assessment, or cloud integration layers without granting those layers implied approval.
IX-BlackFox is source-available for technical evaluation under the repository license.
Unless a separate written commercial license says otherwise, public visibility does not grant permission for commercial use, production use, hosted service use, contractor use, funded operational use, derivative operational use, procurement use, or resale.
See LICENSE for the exact terms.
IX-BlackFox was originated and created by Bryce Lovell.
AI proposes. Humans decide. Evidence decides trust.
