Repository navigation
Retain exact seq2 replay sources for a git-bound inventory - #1102
Merged
seathatflowsinourveins merged 2 commits intoOct 14, 2026
Merged
seathatflowsinourveins merged 2 commits into
seathatflowsinourveins merged 2 commits into
Conversation
seathatflowsinourveins
deleted the
foundation/paper-open-e2e-replay-sources-20261014
branch
October 14, 2026 02:21
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.
Scope
Publish the five retained seq2 replay modules as exact source copies so the CC
can bind a new replay inventory to their landed git commit. These files were
private deployment glue and absent from seq2's runtime inventory; this PR
establishes their first git provenance and does not alter the old seal.
modules plus README with before/after SHA256 and byte counts.
Both preceding publication steps exist; this PR still needs local plus Astra
reads and follows them in the landing queue.
SOTA sources
f6650f9ad73359051f3e558c2431a109bc016664, loadTestsFromModule, and
unittest.mock.patch:
maintained discovery and SYN isolation already used by these sources.
No new loader, order engine or testing framework is added.
8c95a50: the existing engine context the
deployment glue exercised. This pin names the runtime/config source, not
the previous git authorship of the replay modules.
1b0a49d2792a9432a3aca3fcb617ce7a630d905e, crates/system/src/config.rs:
retain the selected native engine and its bounded lifecycle unchanged.
Copy and privacy evidence
Files: test_wiring.py, test_go_issuer.py, test_sequencing.py,
test_unit_contracts.py and test_data_wiring.py. All five compare byte-for-byte
equal to the retained deployment copies. Before/after SHA256 and byte counts
are recorded in the adjacent README; every digest has its full preimage
published in this PR. No content, import, path, fixture or line-ending edit.
The unchanged ROOT/imports expect sibling bundle launch.py, issue_go.py,
launch_data.py, data_worker.py, configs and units. These are archival evaluator
inputs outside ordinary tests/ discovery, not a standalone runnable package.
The future seq3 consumer must use the CC's record of the LANDED source commit;
consumer implementation and executable sealing are outside this small PR.
The requested privacy read found no real keys/tokens, non-no-reply emails,
broker account numbers/ids, credential contents or verbatim owner quotes.
API variable names and synthetic-key/synthetic-secret are inert fixture data.
Scan protocol dates are not account numbers. Machine paths/marker names are
retained under the current privacy rule. Focused gitleaks returned rc0 with
zero findings; no allowlist or scan configuration changed.
Evidence-class table
Local commands run
Repository validation, whitespace, merge-tree and normal publication gates
are recorded in the private lane report with their actual exit codes. The
base's model-currency incident is handled separately in #1101; this PR does
not change currency inputs or bypass that check. Whole-tree validate returned
rc1 for the existing claude-fable-5-1 landscape-age failure at this base; it is
not reported as a pass. No new runtime behavior was
implemented, so no manufactured fail-first behavior claim is made for copying.
Decision record
blueprints/us-equities/paper-open-e2e/seq2-replay/README.md documents the
exact-byte provenance, privacy disposition and separate future inventory gate.
Host evidence
No new host receipt or status change. Original deployment bytes, STOP/HOLD,
receipts/journals, writer state and units are untouched. No service, broker,
credential or GO action.
Checklist
Follow-ups
inventory. Then integrate that binding into seq3's consumer and run its full
strict-seal/SYN/validity process; never edit the original seq2 seal.
publishing these SYN replay sources.