Publish Flow 1.31 evidence and enforce maturity boundaries - #286
Draft
abrichr wants to merge 1 commit into
Draft
Conversation
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.
What changed
Why
The daily evidence-freshness workflow had failed after Flow 1.31.0 replaced Flow 1.30.0 on PyPI. The registry also did not express whether a current campaign was production acceptance. This made a release-fresh label easy to read as a broader maturity claim.
Evidence and impact
The comparison and replication each ran 27 trials: three arms, three conditions, and three trials per condition. Compiled replay was correct in 18 of 18 trials across both complete runs, with zero silent incorrect successes, zero wrong actions, zero over-halts, and zero model calls.
The transaction probe ran 30 trials. The remote-lease probe ran 9 trials. They validate bounded safety contracts, but they do not count both required production reliability metrics. Their manifests therefore state
production_acceptance: false.This PR does not claim hosted, customer-workflow, native desktop, RDP, or Citrix production acceptance. The new readiness document names the exit conditions for those tracks.
Validation
31 passedintests/test_published_evidence_freshness.pygit diff --checkpassed