eval(deltawire): integrate treatment-fidelity preflight - #106
Merged
Conversation
Pitot coding-agent E2EIntelligence Flow is the verification source; Pitot's public README carries the latest
Source commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
DeltaWire's benchmark preflight needed deterministic task contracts, binary parity, independent semantic verification, and fail-closed treatment attribution before any larger experiment could be considered.
This clean integration PR projects the reusable implementation from the conflicted experiment lineage onto current
main. PR #99 remains the provenance record for raw experimental evidence.What changed
c200dc0eb3c4dff0e4732cc4b2daa1cd535703e3.eval/deltawire-preflight-v4and PR eval(deltawire): prepare 72-run preflight and semantic oracles #99.Observed v4 outcome
The one authorized D1-only v4 probe passed semantic exact match and treatment-use fidelity. Harbor's verifier generated a passing environment receipt, but the receipt was not retained from the main task container. The fail-closed end-to-end status is therefore
fail; noprobe-release.v2was created and therange-large/r1pair was not launched.READY_FOR_72=false. No savings, cost, or benchmark claim is made.Validation
bash labs/20-deltawire/scripts/validate.sh