Skip to content

GHOS-ESTATE-ROLLOUT-001/lean-action — shared tooling conformance tracker #727

Closed

Description

@fyremael

Umbrella: #724.
Target repository: grandchallenge/lean-action (repository ID 1316003821).
Phase: 4 — shared action tooling.

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.

Activity

  1. fyremael commented on Sep 2, 2026

    @fyremael
    ContributorAuthor

    GHOS Phase 4 / lean-action exact protected preflight

    Target repository: grandchallenge/lean-action (Issues disabled; this tracker is durable).
    Protected default branch: main at 138a564e38a62ce545e8d47d86a97628463aced4.
    Repository profile: Provider / critical / shared action tooling; fork of leanprover/lean-action.

    Direct workflow inventory — exactly 5, no .ghos-routing/workflows.json present:

    • .github/workflows/actionlint.yml blob cc427d27b207f4a3dc2843eb23eefc01f4d721b0 → OPAQUE_EXECUTION → PERSISTENT_CONTROLLER_REQUIRED
    • .github/workflows/functional_tests.yml blob 339dc38f409dfc1e46c352a4dbdb2c9e6456c905 → OPAQUE_EXECUTION → PERSISTENT_CONTROLLER_REQUIRED
    • .github/workflows/gcl-conformance.yml blob 974d982fe0bc699918cf9850bd9f9dfc188abd31 → AUTONOMOUS_WAKE, EXTERNAL_REUSABLE_JOB, OPAQUE_EXECUTION, SCHEDULED → PERSISTENT_CONTROLLER_REQUIRED
    • .github/workflows/nanoda-daily.yml blob e286f6ebc2a17ec5644763af3434c57216f341d2 → OPAQUE_EXECUTION, SECRET_CREDENTIAL, WRITE_CAPABLE → PERSISTENT_CONTROLLER_REQUIRED
    • .github/workflows/shellcheck.yml blob 1acb9189f90a6f5a53f5c3b633ec06febe74ab60 → OPAQUE_EXECUTION → PERSISTENT_CONTROLLER_REQUIRED

    All are compatible with already-admitted controller GITHUB_ACTIONS / executor class PERSISTENT_CONTROLLER; no new GHOS infrastructure is admitted.

    Live Provider main ruleset 19965519:

    • active; strict: true; bypass []
    • required contexts exactly policy / policy, security / action-policy
    • deletion + non-fast-forward
    • pull-request controls retained, required approvals 0, thread resolution required, merge methods merge/squash.
      Immutable-tag ruleset 19965520: active, bypass [], deletion + non-fast-forward, refs/tags/*.

    Downstream immutable-consumer trust check:

    • GCL consumers found in MATH-PROGRAMME, MATHCERT and MATHSOLVE use exact SHA grandchallenge/lean-action@138a564e38a62ce545e8d47d86a97628463aced4.
    • searches found no GCL uses of grandchallenge/lean-action@v…, @main, @master, or @latest.
    • local immutable release-tag protection is already active.

    Stage-A plan: add only .ghos-routing/workflows.json covering the five existing workflows plus canonical enforcement, and .github/workflows/ghos-routing-enforcement-v2.yml canonical blob pattern pinned to shared gate .github@ef1cce6029233a68cf46063cea2384772fcae613 / SHA-256 fc0a9a4d20de72e9fbc04c8cd54cffc3a6e4657fb09e7978b360616bd5e94a17. 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.

  2. fyremael commented on Sep 2, 2026

    @fyremael
    ContributorAuthor

    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 remains a0ce4332e41be37e87025da71533dec15160aa55.

    Benign PR grandchallenge/lean-action#5:

    • 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.

  3. fyremael commented on Sep 2, 2026

    @fyremael
    ContributorAuthor

    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

    • 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.

  4. fyremael commented on Sep 2, 2026

    @fyremael
    ContributorAuthor

    GHOS Stage C hostile proof — PASS

    Repository: grandchallenge/lean-action

    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.

    Exact-head checks:

    • policy / policy: SUCCESS
    • security / action-policy: SUCCESS
    • actionlint: SUCCESS
    • lint: SUCCESS
    • routing-enforcement: FAILURE, as required

    Protected-base routing run: 33697487728
    Routing job: 100469420837

    Routing 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 != paths and raises workflow 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.

  5. fyremael commented on Sep 3, 2026

    @fyremael
    ContributorAuthor

    GHOS terminal receipt — GHOS_ROUTING_ENFORCED

    Target: grandchallenge/lean-action
    Phase: 4 — shared action tooling

    Protected terminal main: 82d72e361976b4734e7b02a1437e21c8cb4317f8

    Protected 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 — 1acb9189f90a6f5a53f5c3b633ec06febe74ab60

    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.

    Provider main ruleset 19965519 terminal state:

    • active
    • strict: true
    • bypass []
    • deletion + non-fast-forward + existing PR controls preserved
    • required contexts exactly:
      1. policy / policy
      2. security / action-policy
      3. routing-enforcement

    Immutable-tag ruleset 19965520 remains active, bypass [], deletion + non-fast-forward on refs/tags/*.

    Benign protected-base proof:

    Hostile protected-base proof:

    • PR GHOS hostile unregistered workflow probe — DO NOT MERGE lean-action#8
    • final head ef32a5d9b241a58e74f652cbef38d717caa9dfd0
    • exact effective delta: one unregistered inert workflow only
    • policy/security/actionlint/lint SUCCESS
    • routing run 33697487728
    • routing job 100469420837
    • all routing setup/integrity steps SUCCESS; external gate execution FAILURE
    • deterministic class: workflow routing coverage mismatch
    • live PR state mergeable_state: blocked
    • closed unmerged

    Downstream immutable-consumer trust refreshed at terminal:

    • current MATH-PROGRAMME, MATHCERT, and MATHSOLVE uses remain pinned to exact grandchallenge/lean-action@138a564e38a62ce545e8d47d86a97628463aced4;
    • searches return no @main, @master, @latest, or @v… references in those governed consumers.
    • therefore the routing-only Provider change does not silently retarget downstream action execution; downstream updates remain explicit governed mutations.

    No constitutional, mathematical, certification, provenance, publication, production, scientific, novelty, patentability, physical, mechanical, manufacturing, or commercial authority is enlarged.

    Terminal disposition: GHOS_ROUTING_ENFORCED.

  6. added a commit that references this issue on Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions