feat: first Flow 1.34.0 remote-safe-synthetic qualification-release - #31
Merged
Conversation
Install the until-revoked signer registry and the signed Flow 1.34.0 object pairs under production-evidence/. The ledger row that binds these objects is the next commit, with registry_source_commit set to this SHA.
Bind the registered qualification-release/v2 object as the first ledger row. registry_source_commit is 6e28818, the commit that holds the objects. The row is until-revoked remote-safe-synthetic evidence. It does not derive seven-target Production.
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
1 participant
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.
This is a remote-safe-synthetic Flow 1.34.0 package admission, until revoked; not seven-target Production; not a MockMed production_acceptance flip; native DMG still unsigned.
#30 parked the signed objects under
local-candidates/. This PR copies them toproduction-evidence/, installs the until-revoked signer registry (innerqa-ed25519-9cf4bca214c01d79, outeroa-public-trust-ed25519-9cf4bca214c01d79), and appends the firstqualification-release/v2row for targetflowwith claim_scopeproduction_flow.Two commits, on purpose.
6e28818aholds the objects and registry. The ledger reference'sregistry_source_commitis that SHA. Don't re-sign; the nested refs inside the signed object still name the pre-registry commit they were built with.Bound PyPI files, checked live:
openadapt_flow-1.34.0-py3-none-any.whlsha256:56d32818989cb3a92830080ead39e10b08718c55e00988117f22cbfeaac98854openadapt_flow-1.34.0.tar.gzsha256:a941a70015fe91897e655bfc9bf83e6cf8fbcf8bd4e4c7206ffb133c505203f8validate_production_lifecycle.pyaccepts the row and still reports 0 active Production admissions. Synthetic evidence isn't enough to move Flow (or anyone else) into Production. The campaign is 1 cell x 3 trials per class. It isn't the MockMed evals set.Reviewer check: confirm the ledger kind is
qualification-release,expires_aton the signed object is JSON null, and the registry revision is exactly 2 against empty-v2 genesis.Opened by an agent session, not the founder.