You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
grandchallenge/lean-action has GitHub Issues disabled, so this is the durable operational tracker. Evidence and implementation remain bound to exact target-repository commits.
Objective: establish local GH-OS routing conformance and downstream immutable-consumer trust semantics. Inventory direct workflows, derive execution topology, bind any non-bounded workflow to an admitted compatible controller, and verify governance-sensitive consumers do not rely on mutable/floating action identities.
Required evidence includes target protected head/workflow inventory, local routing/ruleset/readback proof where applicable, downstream pin/update semantics, and hostile evidence appropriate to the shared-action profile.
Terminal: GHOS_ROUTING_ENFORCED, GHOS_GOVERNED_NON_APPLICABLE, or GHOS_BLOCKED_WITH_NAMED_DEFECT.
exact head 1cb6c7710ba468caab815ff40d7310fc6ee1f0cf;
delta exactly one inert documentation file;
protected-base routing run 33696481008, job 100466327704;
materialization, enforcement self-integrity, pinned external-gate verification, and PyYAML install all succeeded;
external gate then failed workflow routing coverage mismatch.
Root cause is local registry ordering, confirmed against pinned gate bytes f9f85937713046eacdc79c532046c676cbb4550c: the gate computes the workflow path inventory with sorted(...) and requires registered == paths. The Stage-A registry placed .github/workflows/ghos-routing-enforcement-v2.yml after shellcheck.yml instead of its lexicographic position between gcl-conformance.yml and nanoda-daily.yml.
Disposition: benign proof #5 is invalid and will close unmerged; Stage B remains NOT ACTIVATED. Repair scope is exactly registry entry ordering; no workflow, action implementation, controller, permission, ruleset, tag, or claim-authority semantics change. A fresh benign proof is required after protected repair merge.
exact base 82d72e361976b4734e7b02a1437e21c8cb4317f8;
exact head 9936639ed6d451c6a1107fc3849fb8438f92f7fe;
delta exactly one inert documentation file;
protected-base routing run 33696845237;
routing job 100467449686;
materialization SUCCESS;
enforcement self-integrity SUCCESS;
pinned external-gate fetch/digest SUCCESS;
dependency install SUCCESS;
external gate execution SUCCESS;
overall result SUCCESS;
PR closed unmerged.
Stage B remains unactivated at this receipt. Next permitted control-plane delta is only addition of required context routing-enforcement to existing strict Provider main ruleset 19965519, preserving strict: true, bypass [], all PR controls, and immutable-tag ruleset 19965520 unchanged.
Protected base: 82d72e361976b4734e7b02a1437e21c8cb4317f8
Final hostile PR: grandchallenge/lean-action#8
Final hostile head: ef32a5d9b241a58e74f652cbef38d717caa9dfd0
The effective candidate differs from protected main by exactly one added workflow, .github/workflows/ghos-hostile-unregistered-inert.yml; the governed .ghos-routing/workflows.json is unchanged. The workflow is manual-dispatch-only, contents: read, and its job is guarded by an impossible repository predicate; it is not a candidate execution path.
Protected routing registry blob: 76f3d33c8fa728e7e6548b41b5d3e80dbbd62701.
Registry coverage is canonical lexicographic order; all six workflows derive PERSISTENT_CONTROLLER_REQUIRED and bind only to already-admitted GITHUB_ACTIONS. Claim boundaries remain all false.
Protected enforcement is the canonical candidate-independent implementation pinned to shared gate .github@ef1cce6029233a68cf46063cea2384772fcae613, gate blob f9f85937713046eacdc79c532046c676cbb4550c, gate SHA-256 fc0a9a4d20de72e9fbc04c8cd54cffc3a6e4657fb09e7978b360616bd5e94a17, dependency PyYAML==6.0.3.
Activity
fyremael commentedon Sep 2, 2026
GHOS Phase 4 / lean-action exact protected preflight
Target repository:
grandchallenge/lean-action(Issues disabled; this tracker is durable).Protected default branch:
mainat138a564e38a62ce545e8d47d86a97628463aced4.Repository profile: Provider / critical / shared action tooling; fork of
leanprover/lean-action.Direct workflow inventory — exactly 5, no
.ghos-routing/workflows.jsonpresent:.github/workflows/actionlint.ymlblobcc427d27b207f4a3dc2843eb23eefc01f4d721b0→OPAQUE_EXECUTION→PERSISTENT_CONTROLLER_REQUIRED.github/workflows/functional_tests.ymlblob339dc38f409dfc1e46c352a4dbdb2c9e6456c905→OPAQUE_EXECUTION→PERSISTENT_CONTROLLER_REQUIRED.github/workflows/gcl-conformance.ymlblob974d982fe0bc699918cf9850bd9f9dfc188abd31→AUTONOMOUS_WAKE,EXTERNAL_REUSABLE_JOB,OPAQUE_EXECUTION,SCHEDULED→PERSISTENT_CONTROLLER_REQUIRED.github/workflows/nanoda-daily.ymlblobe286f6ebc2a17ec5644763af3434c57216f341d2→OPAQUE_EXECUTION,SECRET_CREDENTIAL,WRITE_CAPABLE→PERSISTENT_CONTROLLER_REQUIRED.github/workflows/shellcheck.ymlblob1acb9189f90a6f5a53f5c3b633ec06febe74ab60→OPAQUE_EXECUTION→PERSISTENT_CONTROLLER_REQUIREDAll are compatible with already-admitted controller
GITHUB_ACTIONS/ executor classPERSISTENT_CONTROLLER; no new GHOS infrastructure is admitted.Live Provider main ruleset
19965519:strict: true; bypass[]policy / policy,security / action-policyImmutable-tag ruleset
19965520: active, bypass[], deletion + non-fast-forward,refs/tags/*.Downstream immutable-consumer trust check:
grandchallenge/lean-action@138a564e38a62ce545e8d47d86a97628463aced4.grandchallenge/lean-action@v…,@main,@master, or@latest.Stage-A plan: add only
.ghos-routing/workflows.jsoncovering the five existing workflows plus canonical enforcement, and.github/workflows/ghos-routing-enforcement-v2.ymlcanonical blob pattern pinned to shared gate.github@ef1cce6029233a68cf46063cea2384772fcae613/ SHA-256fc0a9a4d20de72e9fbc04c8cd54cffc3a6e4657fb09e7978b360616bd5e94a17. Preserve the strict Provider profile; routing becomes mandatory only after protected merge + benign proof + exact one-context ruleset administration.No constitutional, mathematical, certification, provenance, publication, production, scientific, novelty, patentability, physical, mechanical, manufacturing, or commercial authority is enlarged.
fyremael commentedon Sep 2, 2026
GHOS Phase-4 / lean-action Stage-A benign probe detected a narrow registry-order defect before Stage B.
Protected main remains
64b25d2bd963a7d2b2a612d38aa286301e5aa307; canonical enforcement blob remainsa0ce4332e41be37e87025da71533dec15160aa55.Benign PR grandchallenge/lean-action#5:
1cb6c7710ba468caab815ff40d7310fc6ee1f0cf;33696481008, job100466327704;workflow routing coverage mismatch.Root cause is local registry ordering, confirmed against pinned gate bytes
f9f85937713046eacdc79c532046c676cbb4550c: the gate computes the workflow path inventory withsorted(...)and requiresregistered == paths. The Stage-A registry placed.github/workflows/ghos-routing-enforcement-v2.ymlaftershellcheck.ymlinstead of its lexicographic position betweengcl-conformance.ymlandnanoda-daily.yml.Disposition: benign proof #5 is invalid and will close unmerged; Stage B remains NOT ACTIVATED. Repair scope is exactly registry entry ordering; no workflow, action implementation, controller, permission, ruleset, tag, or claim-authority semantics change. A fresh benign proof is required after protected repair merge.
fyremael commentedon Sep 2, 2026
GHOS Phase-4 / lean-action benign protected-base proof is now valid after the narrow registry-order repair.
Protected repair merge:
82d72e361976b4734e7b02a1437e21c8cb4317f8.Protected routing registry blob:
76f3d33c8fa728e7e6548b41b5d3e80dbbd62701.Canonical enforcement blob remains
a0ce4332e41be37e87025da71533dec15160aa55.Benign proof: grandchallenge/lean-action#7
82d72e361976b4734e7b02a1437e21c8cb4317f8;9936639ed6d451c6a1107fc3849fb8438f92f7fe;33696845237;100467449686;Stage B remains unactivated at this receipt. Next permitted control-plane delta is only addition of required context
routing-enforcementto existing strict Provider main ruleset19965519, preservingstrict: true, bypass[], all PR controls, and immutable-tag ruleset19965520unchanged.fyremael commentedon Sep 2, 2026
GHOS Stage C hostile proof — PASS
Repository:
grandchallenge/lean-actionProtected base:
82d72e361976b4734e7b02a1437e21c8cb4317f8Final hostile PR: grandchallenge/lean-action#8
Final hostile head:
ef32a5d9b241a58e74f652cbef38d717caa9dfd0The effective candidate differs from protected main by exactly one added workflow,
.github/workflows/ghos-hostile-unregistered-inert.yml; the governed.ghos-routing/workflows.jsonis unchanged. The workflow is manual-dispatch-only,contents: read, and its job is guarded by an impossible repository predicate; it is not a candidate execution path.Exact-head checks:
policy / policy: SUCCESSsecurity / action-policy: SUCCESSactionlint: SUCCESSlint: SUCCESSrouting-enforcement: FAILURE, as requiredProtected-base routing run:
33697487728Routing job:
100469420837Routing job step results: materialize candidate bytes SUCCESS; reject enforcement self-modification SUCCESS; fetch/verify external gate SUCCESS; install pinned dependency SUCCESS; execute external gate FAILURE. Given the exact candidate adds one workflow and leaves the registry unchanged, the pinned gate deterministically reaches
registered != pathsand raisesworkflow routing coverage mismatch.Live PR state after all checks:
mergeable_state: blocked.Disposition: hostile proof established. PR #8 is evidence-only and will be closed unmerged.
fyremael commentedon Sep 3, 2026
GHOS terminal receipt —
GHOS_ROUTING_ENFORCEDTarget:
grandchallenge/lean-actionPhase: 4 — shared action tooling
Protected terminal main:
82d72e361976b4734e7b02a1437e21c8cb4317f8Protected workflow inventory — exactly 6:
.github/workflows/actionlint.yml—cc427d27b207f4a3dc2843eb23eefc01f4d721b0.github/workflows/functional_tests.yml—339dc38f409dfc1e46c352a4dbdb2c9e6456c905.github/workflows/gcl-conformance.yml—974d982fe0bc699918cf9850bd9f9dfc188abd31.github/workflows/ghos-routing-enforcement-v2.yml—a0ce4332e41be37e87025da71533dec15160aa55.github/workflows/nanoda-daily.yml—e286f6ebc2a17ec5644763af3434c57216f341d2.github/workflows/shellcheck.yml—1acb9189f90a6f5a53f5c3b633ec06febe74ab60Protected routing registry blob:
76f3d33c8fa728e7e6548b41b5d3e80dbbd62701.Registry coverage is canonical lexicographic order; all six workflows derive
PERSISTENT_CONTROLLER_REQUIREDand bind only to already-admittedGITHUB_ACTIONS. Claim boundaries remain all false.Protected enforcement is the canonical candidate-independent implementation pinned to shared gate
.github@ef1cce6029233a68cf46063cea2384772fcae613, gate blobf9f85937713046eacdc79c532046c676cbb4550c, gate SHA-256fc0a9a4d20de72e9fbc04c8cd54cffc3a6e4657fb09e7978b360616bd5e94a17, dependencyPyYAML==6.0.3.Provider main ruleset
19965519terminal state:strict: true[]policy / policysecurity / action-policyrouting-enforcementImmutable-tag ruleset
19965520remains active, bypass[], deletion + non-fast-forward onrefs/tags/*.Benign protected-base proof:
9936639ed6d451c6a1107fc3849fb8438f92f7fe33696845237100467449686Hostile protected-base proof:
ef32a5d9b241a58e74f652cbef38d717caa9dfd033697487728100469420837workflow routing coverage mismatchmergeable_state: blockedDownstream immutable-consumer trust refreshed at terminal:
grandchallenge/lean-action@138a564e38a62ce545e8d47d86a97628463aced4;@main,@master,@latest, or@v…references in those governed consumers.No constitutional, mathematical, certification, provenance, publication, production, scientific, novelty, patentability, physical, mechanical, manufacturing, or commercial authority is enlarged.
Terminal disposition:
GHOS_ROUTING_ENFORCED.EC-BULK-005: authentic #727 source audit and unaccepted explanatory d…