Skip to content

GHOS Stage A repair: canonicalize routing registry order - #6

Merged
fyremael merged 1 commit into
mainfrom
governance/ghos-stage-a-registry-order-repair
Sep 2, 2026
Merged

fyremael merged 1 commit into
mainfrom
governance/ghos-stage-a-registry-order-repair

Conversation

@fyremael

@fyremael fyremael commented Sep 2, 2026

Copy link
Copy Markdown

Narrow repair for GHOS-ESTATE-ROLLOUT-001 / MATH-PROGRAMME#727 after benign proof #5 exposed a registry-order mismatch.

Exact protected base: 64b25d2bd963a7d2b2a612d38aa286301e5aa307.
Exact candidate head: 7e370412951f503289d3229a3e2a486c2a4320af.

Delta is exactly one modified file: .ghos-routing/workflows.json. The only semantic change is canonical lexicographic ordering of existing workflow entries: ghos-routing-enforcement-v2.yml moves between gcl-conformance.yml and nanoda-daily.yml, matching the pinned external gate's sorted(...) workflow inventory. No workflow bytes, action implementation, controller catalog, feature declarations, topology, permissions, rulesets, immutable tags, or claim boundaries change.

Expected protected-base routing result: success. Stage B remains unactivated until this repair is protected and a fresh documentation-only benign proof succeeds.

@fyremael
fyremael requested a review from a team as a code owner September 2, 2026 23:46
@fyremael
fyremael merged commit 82d72e3 into main Sep 2, 2026
4 checks passed
@fyremael
fyremael deleted the governance/ghos-stage-a-registry-order-repair branch September 2, 2026 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant