feat(engine): separate application and authoring workflows - #1
Merged
MrScripty merged 26 commits intoSep 25, 2026
Merged
Conversation
Run the existing locked Python verification on the dedicated implementation branch. Retain a source-only Git bundle for exact-candidate inspection when the implementation runtime cannot clone GitHub. The job has read-only repository permissions and uses no checkout credentials. This is M0 execution support, not standards-content migration or feature acceptance.
Require a host-selected purpose and generate purpose-specific wire contracts. Bind application exposure to reviewed material, retain reasoning in authoring-only provenance, and publish supporting changes through the existing workflow. Preserve the real standards corpus and begin with empty exposure declarations. The breaking Analysis 7 contract binds explicit preservation or change to the actual candidate revision. Installed locked-client qualification and independent review remain recorded in the plan.
Preserve Identity-v2 bytes while accelerating scalar and path encoding. Reuse bounded verified Git objects per exact-revision capture, and carry immutable analysis inputs across fresh decision evaluations without retaining authorization or publication state. Keep capture replay independent, accepted-main selection unchanged, and the transport/store lifetime per call. Repair disposable test clones to establish their own candidate main. Add behavioral regressions and paired performance evidence. Verification: 166 distinct Engine tests covered across the full run and four fixture reruns; 421 supporting package tests run with one existing interpreter-dependent skip; 73 structural suites / 121 checks. Local Python 3.13 evidence remains distinct from supported pinned qualification.
Carry one operation-owned verified base and exact proposal projection through focused preflight, prospective validation, analysis and result projection. Move Authoring preparation to the invocation boundary and preserve independent evaluations, lifecycle, revision, authorization, capture and publication checks. Verification: all 177 Engine tests passed in isolated module processes; 421 supporting tests (one existing interpreter-dependent skip); 73 structural suites / 121 checks. Paired three-sample measurements show approximately 2.3x faster proposal creation and 2x revision/resolution. Local Python 3.13 results remain distinct from supported installed qualification.
…ured inputs Keep Identity-v2 preimages and full integrity checks while using compact exact-byte storage. Separate authoritative input discovery from filesystem check execution so logical proposals derive the same manifest without temporary repositories or guessed file content. Reuse explicit test snapshots only within an accepted revision. Preserve actual candidate verification, publication, purpose, and recovery boundaries. Focused Identity and Verifier regressions, full-corpus manifest equivalence, paired source measurements, and the 73-suite/121-check structural checkpoint passed locally. Full committed-candidate qualification and retained measurement evidence follow separately.
Use the existing provenance-read-result authority field for the post-publication snapshot. Preserve fresh boundary captures and all exclusion and historical-read assertions; no runtime or public contract change.
Record same-corpus identity, read, proposal, allocation and full-publication measurements. Separate runtime gains from explicit-snapshot test reuse, preserve exact output oracles, and retain the final 616-test and structural evidence with supported-environment limits.
|
Important Review skippedToo many files! This PR contains 374 files, which is 74 over the limit of 300. To get a review, reduce the PR to 300 files or fewer by splitting it into smaller PRs or changing its base branch. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (26)
📒 Files selected for processing (374)
You can disable this status message by setting the Comment |
Owner
Author
|
All commits have been tested and proven in production. One thing to note, not all the graphs are being projected out of the sqlight db for git tracking. That is unimplemented and will be coming soon. |
MrScripty
deleted the
implementation/purpose-separated-standards-engine
branch
September 25, 2026 17:51
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
2 participants
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.
Summary
Selected Evidence
Verification
Existing committed evidence records supported Python 3.12.3 qualification, including:
These results belong to the specific candidates and environments documented in the linked reports. No new test run was performed while opening this PR.
Publication scope
This PR targets GitHub
mainfromimplementation/purpose-separated-standards-engine(26 commits ahead when opened).The separately applied standards migration, including the rewritten Markdown, provenance records, relationships, and coverage receipts, was published by the Engine to local
mainat72963ad590ca91040feb132243f3395b447fad3e. That commit is not on this PR's source branch and is not included here. Its GitHub publication remains a separate integration step.