Skip to content

Harden ACB collector with production guards and measured Windows controls - #27

Draft
echo-fleet-builder[bot] wants to merge 4 commits into
mainfrom
agent/acb-collector-review-20261003
Draft

echo-fleet-builder[bot] wants to merge 4 commits into
mainfrom
agent/acb-collector-review-20261003

Conversation

@echo-fleet-builder

@echo-fleet-builder echo-fleet-builder Bot commented Oct 3, 2026 •

Copy link
Copy Markdown

The historical HAMMER collector was bound to an obsolete ACB revision and could otherwise misrepresent isolated installation evidence as production acceptance. This source import now requires the reviewed ACB candidate d9ffe76ad63b71545d5378f154e15af10e4f7a9e, version 1.1.0+codex.20261003194149, and rejects isolated-canary evidence before any production collection or signing. It also rechecks the original evidence timestamps immediately before key access.

Acceptance requires three genuine installed QUENCH passes of 119 base assertions, six Windows rename controls, five Windows lock-acquisition controls, real 12-request/8-process router checks, three critical journeys and three fresh native Qwen canaries. HAMMER independently executes its 91 supported assertions and all router/control/journey commands three times. The collector preserves the DPAPI remote-session boundary, existing key identity, exact installed/cache/remote/PR identities, hosted App receipt, custody and output-ownership checks. Current V6 isolated installation evidence passed; it cannot authorize production signing. Prior failed candidates and the newly found failures remain preserved as evidence.

Only the collector, synthetic regression tests and its provenance/operations document are added to canonical main. This narrow draft supersedes closed broad draft #26; it preserves the original deployed-base and default-branch histories. The original source SHA and reconstruction are documented. No verifier, policy, trust store or target code is modified by this PR.

Validation: 689 tests passed, one skipped; 62 collector regressions passed, including scope-before-side-effects, stale-pre-key evidence and all five-control negative cases. P1 acceptance, exact-deliverable/commit secret scans and independent review passed. Fresh task-specific build preflight is READY. Release preflight remains NOT_READY for missing production/certification/deployment/rollback evidence. The separately recovered hosted receiver has not produced an authentic exact-candidate webhook receipt.

Held diagnostic source only: no owner signing key read, envelope signing, trust enrollment, service deployment or production promotion. Production use still requires measured production installation plus an authentic hosted receipt and separately verified consumer/admission. Ordinary CI and an isolated native canary do not establish production acceptance.

@echoomegaprime echoomegaprime changed the title Harden ACB collector and bind repaired Windows acceptance Harden ACB collector with production guards and measured Windows controls Oct 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant