Repository navigation
ops: register AgentSPEX and AgentSilex as blocked wave pilots - #251
Merged
Merged
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.
Five-source wave registry reconciliation
The standing preparation stage requires all five fixed source identities to exist in the authoritative current-main workspace registry, even if individual members have blockers. In the current wave, Fara and Evidence Bench already have exact reverified packets from merged #249; agentUniverse is already present, but AgentSPEX and AgentSilex were pilot-only historical source experiments and absent from the registry. The correct one-use host preflight failed closed with
Wave source not in registrybefore any fork writes.This change adds two pilot-only source links to
data/contribution-workspaces/pilot-sources.json, backed by existing #116 and #115. It does not turn their historical native checks into fresh proof, assignAWAITING_EXTERNAL, claim an eligible patch hash, or replace members of the frozen five-source wave.Generated
registry.jsonandfork-bootstrap-proposal.jsonare synchronized. A negative contract test confirms that both sources have no stage-ready technical handoff.Local verification: 685/685 Python unit tests PASS, generated files match and
git diff --checkPASS.Next: repeat actor/policy/fork/source native preflight for the original five identities, then independently stage only the eligible two source-native packets under the bounded standing preparation mandate. No third-party writes performed by this PR. Related #6, #56.