Add Commander-governed native constraint core#3
Draft
FreshSoftware4 wants to merge 59 commits 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.
Purpose
Advance the execution-native Locus64 spine from two primitive operation classes to the first coherent constraint core, under an explicit Commander change chain.
Completed change chain
LOCUS64_CONSTRAINT_CORE_CHANGE_CHAIN.athensis closed with five evidence-gated links:The parent
LOCUS64_EXECUTION_COHERENCE_RAIL.athenshas advanced:Native capability added
u64L64R1 -> L64D -> L64R1 -> L64Dfixed points for discharged and unresolved guardsBurden control
No new registry, receipt family, solver object, string identity, JSON schema, or parallel authority graph was introduced. The public surface remains within the established caps:
Node <= 32 bytesPort <= 8 bytesDimension <= 8 bytesLarge implementation files were factored only at existing item boundaries to improve review locality without adding authority layers or changing canonical bytes.
Verification
Local isolated verification passed:
GitHub run
29990484222passed on source headcbcbfe5d9c4f34baf0ca54306c77a85ac970bd26:The commits after that green source head modify only the two Commander rail files and CI event deduplication; no Rust or CLI source changed.
CI coordination repair
Commander branches now run the native gate on
push; same-repository PR events skip the duplicate heavy job, while fork PRs retain pull-request coverage. Rail files are watched paths so governed state changes remain part of release identity.Remaining rail
The next stage is proof-producing congruence: equivalence may not merge without checked provenance. It is followed by incremental closure, native upper projections, and final legacy authority quarantine.