docs(evidence): rebind published evidence to Flow 1.28.0 - #283
Merged
Conversation
Re-measure the comparison, the transaction probe, and a new remote frame-lease safety probe against the exact 1.28.0 wheel; mark 1.27.1 superseded. Both harnesses and the MockMed fixture are byte-identical to the 1.27.1 measurement, so the comparison is controlled. The freshness check was correct and is unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NyCHrzA1psrKMFfroYbzaM
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.
The failure
evidence-freshnessbinds the published evidence to the newest non-yankedopenadapt-flowrelease on PyPI.openadapt-flow1.28.0 published at2026-08-02T13:46Z, so the check now fails on
main(71edc88):The check is right and is not relaxed here. No window widened, no exclusion
added, no threshold moved. The fix is to re-measure.
What was measured
All runners re-run against the exact published 1.28.0 wheel
(
4d156035…c7202) bound to release-tagged tracked-clean sourceb646276, onthe same macOS host as the 1.27.1 evidence, plus an independent replication of
the whole comparison. Zero model calls, $0.00, loopback only. Exact commands in
REPRODUCE.md.The comparison is controlled
This is the first release-over-release comparison in this directory where
neither the fixture nor either harness moved:
68f9e5a2…8a12668f9e5a2…8a126(byte-identical)097cc900…40ce8097cc900…40ce8(byte-identical)f0736c7af0736c7a(byte-identical)So no delta below can be a measurement artefact.
Held: no outcome classification moved
Denominators: 3 trials per arm per condition (the repository minimum for a
comparative claim), doubled by one independent replication. One measurement run
is 27 counted trials (3 conditions x 3 arms x 3 trials); primary plus
replication is 54, of which 18 are compiled replay.
succeeded, 0 over-halts, 0 silent incorrect successes, 0 wrong-target
writes, 0 model calls, $0.00.
clean_postcondition_over_halt.jsonandtheme_postcondition_over_halt.jsonrecord 0 observations in both runs.
renamed locator and before any mutation.
configurations x 3 trials = 30 counted runs) report the same outcome as on
1.27.1, with 0 violations across 30 runs.
timeoutstaysRECONCILIATION_REQUIREDin 6 of 6.Two transaction invariants are
vacuous, not passes: no counted run claimed anabsence and no counted run reported
VERIFIED, so neither could be exercised.Worse: compiled replay is slower, and it is not softened
The compiled steady-state median rose in all 6 condition-by-run cells:
cleanprimarycleanreplicationthemeprimarythemereplicationrenameprimaryrenamereplicationIn
cleanthe two 6-trial samples do not overlap (1.27.1 spans 6.801-6.947s;1.28.0 spans 6.966-7.055s). The harness and fixture were identical, so this is
not a measurement artefact. It is recorded as unattributed: the two evidence
sets were measured in separate sessions hours apart rather than interleaved, so
this design cannot separate an engine effect from host drift. Record and compile
timings did not move, which argues against a broad host slowdown without
settling it. Nothing in
c9618ccruns on this path. Establishing the cause needsan interleaved A/B of the two wheels in one session; that is not run here. It
changes no outcome classification.
The remote frame-lease change, measured rather than trusted
c9618cclets a consequential remote click be delivered through a backend'sone-shot actuation lease when no typed delivery receipt exists. Relaxing a
refusal can buy a green demonstration with a silent wrong write, so this PR adds
scripts/probe_remote_lease_safety.pyand measures both stated properties.3 cells x 3 trials = 9 counted runs, each classified under all 3 execution
profiles = 27 classifications.
transaction_outcome(demo / standard / regulated)ungoverned_leaseCOMPLETED_UNVERIFIEDin all threegoverned_leaseHALTED_BEFORE_EFFECTin all threelease_frame_changedRECONCILIATION_REQUIREDin all threewith
safety_haltset; the backend received zero input edges. The onlydifference from
ungoverned_lease, which delivered 3 of 3, is the presence ofa
GovernedRunAuthorization.VERIFIED. Across 27 classifications,VERIFIEDwas returned 0times,
production_eligiblewas true 0 times,transaction_billablewas true0 times. Every lease delivery carried no receipt and no actuation tier, which
is what leaves
COMPLETED_UNVERIFIEDas the classifier's only answer.acquire_actuation_frameand the input edge aborted delivery in 3 of 3 runs,and settled at
RECONCILIATION_REQUIREDrather than claiming a proven absence.Scope, stated in the artifact: that probe's backend is a fake exposing only the
two-phase lease. It establishes a runtime contract, not the behaviour of a real
Citrix or RDP session.
Checks run locally
scripts/check_published_evidence_freshness.pyagainst PyPI: exit 0, "boundto the current openadapt-flow release 1.28.0".
--offlinehalf: exit 0.uv run --no-sources ruff check .: clean.uv build --no-sources+check_source_boundary.py --require-dist: OK.pytest tests/ -m "not heavy and not gpu and not vm": 2137 passed, 55 skipped.1.27.1 is marked
superseded, never deleted, and stays reproducible against thewheel it was measured on. Docs and one new evidence script only;
docs:is notin this repository's
minor_tagsorpatch_tags, so this cuts no release.🤖 Generated with Claude Code
https://claude.ai/code/session_01NyCHrzA1psrKMFfroYbzaM