FFFF Phase 3: define publication-profile proof authority and retained evidence · Issue #21 · Mnehmos/MathOS · GitHub
[go: up one dir, main page]

Skip to content

Phase 3: define publication-profile proof authority and retained evidence #21

Closed

Description

@Mnehmos

Product outcome

Create the production trust boundary that can turn an exact Lean result into authoritative proof or refutation evidence without allowing local workers, agents, or caller-authored reports to self-promote.

Scope

  • define and commit a closed publication verification request, policy, and report contract;
  • bind one exact formalization, environment, Lean module, declaration, accepted elaboration diagnostic, proof-closure scan, axiom audit, clean checkout identity, dependency closure, and retained artifacts;
  • distinguish proof from refutation explicitly;
  • enforce the publication profile in a fresh GitHub-hosted Linux job with pinned toolchains and no model or provider credentials;
  • document the exact memory and network controls that are enforced and any platform limitations;
  • retain canonical reports and complete diagnostic logs as workflow artifacts;
  • add a controlled ingestion or release path that verifies report provenance before creating authoritative evidence;
  • keep local workers and ordinary CLI or MCP callers structurally unable to manufacture authoritative evidence;
  • keep truth status unavailable until exact current fidelity evidence can be combined with authoritative proof or refutation evidence.

Acceptance criteria

  • Closed Rust types and committed JSON Schemas reject unknown fields and caller-authored authority.
  • Publication policy has a canonical hash and binds exact repository commit and tree identities.
  • The real pinned Lean declaration is rebuilt from a clean checkout with dependency closure, hole and unsafe scans, and axiom audit.
  • Publication proof and refutation outcomes are separate and bound to the exact formalization version.
  • Every retained artifact is SHA-256 addressed and included in a canonical report.
  • A local profile, model, raw JSON caller, or modified report cannot create authoritative evidence.
  • Report provenance is verified by an engineering control stronger than an environment variable or prompt instruction.
  • Retry, restart, stale input, altered artifact, altered policy, wrong declaration, wrong environment, and missing retained evidence fail closed.
  • CLI and MCP expose only the reviewed safe surface through the shared application service.
  • Adversarial tests prove local diagnostic evidence cannot cross the authority boundary.
  • Fresh Linux, Windows, storage, Python, and real pinned Lean CI pass on the exact remote tree.
  • Trust documentation and the implementation ledger state precisely what publication authority does and does not establish.

Explicit non-goals

  • derived source-claim truth status;
  • novelty;
  • pedagogy;
  • release publication;
  • a second proof assistant;
  • generic plugins or arbitrary command execution.

Activity

  1. Mnehmos commented on Jul 19, 2026

    @Mnehmos
    OwnerAuthor

    Issue #21 contract slice is published.

    This slice adds:

    • canonical publication policy hash 9cac0ae88eb00e84474ce9f7a2357b5b8677beb6e042d163f95c78a453c34a2b;
    • separate proof and refutation requests bound to exact evidence, formalization, environment, module, declaration, commit, and tree identities;
    • non-authoritative candidate reports that fail if required isolation, retention, workflow, runner, source, policy, or axiom controls are missing;
    • ADR-0006, which requires repository and workflow constrained GitHub OIDC and Sigstore attestation verification before promotion;
    • SHA-pinned actions/attest and artifact retention identities;
    • adversarial contract and schema tests.

    Validation passed: warnings-denied Clippy, 79 Rust unit tests, real CLI and MCP subprocess tests, pinned Lean integration, 39 legacy Python regressions, formatting, and patch checks.

    Remote commit: bb9cff8894bf43927c3106d8a452c9932c656460
    Exact local and GitHub tree: ac36221dfb268fc0b60e0aabaf70bd31bae57699

    No authoritative evidence or mathematical status exists in this slice. Protected candidate generation, attestation, verified ingestion, and promotion remain active.

  2. Mnehmos commented on Jul 19, 2026

    @Mnehmos
    OwnerAuthor

    Publication authority contract checkpoint passed GitHub Actions run 29706570941 on exact tree ac36221dfb268fc0b60e0aabaf70bd31bae57699. All five jobs succeeded, including fresh Ubuntu, fresh Windows, real storage, legacy Python, and the pinned Lean integration.

    Issue #21 remains open. This run validates the closed contracts and non-self-authority rules only. It does not establish isolated clean-checkout candidate generation, Sigstore attestation, verified ingestion, authoritative evidence, or mathematical status.

  3. added a commit that references this issue on Jul 19, 2026
  4. Mnehmos commented on Jul 19, 2026

    @Mnehmos
    OwnerAuthor

    Publication boundary checkpoint is now durable in draft PR #22.

    The slice runs a committed Lean theorem through a typed verifier command inside Bubblewrap with network isolation and an enforced address-space limit, emits a content-bound candidate report, and configures GitHub OIDC artifact attestation plus retained diagnostics. The candidate remains explicitly non-authoritative until attestation and policy ingestion are implemented.

    Remote commit: 367ff24ba0091009aaeeade1eda402838348b585
    Exact tree: 1cba96a24c6759c52216f7a626d2f0ef7ea93d51

    I am monitoring the hosted Linux result and will repair the boundary in place if adversarial CI exposes a platform assumption.

  5. Mnehmos commented on Jul 19, 2026

    @Mnehmos
    OwnerAuthor

    Checkpoint: the first protected main boundary is now independently inspectable. Publication run 29707995584 passed on merge commit 31ccfdda41d538bde7e01e061865580cab2f04e5 and retained artifact 8448453305 for 90 days. The archive digest is 0e3d0007da30460b1918d98fea39fad08cffda4b0249035a88bb9a1cd2d30896; the exact report digest is 08bead82cea25ffdfc3424084cb0878f2a648b3375317daa0c799395751dba40; and the Sigstore bundle digest is 5dd23a13fa66efef8885e2116bd994bce92244a290c3ce0d9467d5eeb6d5ac14. The DSSE subject matches the report, and the certificate binds the protected workflow, main, the exact source commit, push event, and a GitHub-hosted runner.

    This does not close #21. The retained smoke report is deliberately non-authoritative. Active work now pins GitHub CLI 2.96.0 by archive and executable digests, verifies the exact bundle under closed workflow/ref/commit/runner constraints, and emits a schema-closed verification record that also cannot self-promote. Controlled ingestion of a real publication_report/1 and authoritative exact evidence remain open.

  6. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Protected publication evidence for the merged correction:

    • PR head: d10cb27a620bf0f3b5c4881a55aeee53179b4a90
    • PR tree: e5b0bcbf4eacf9cb402d87b04b5dc9b0431134f2
    • merge commit/source commit: 6b4a0f22d3498a4cb0c8dab744da7f9a09993fd8
    • source tree: e5b0bcbf4eacf9cb402d87b04b5dc9b0431134f2
    • CI run: 29709569292 (all five jobs passed on the PR head)
    • protected publication run: 29709634846, attempt 1
    • publication job: 88251709818
    • retained artifact: 8448739399, publication-boundary-6b4a0f22d3498a4cb0c8dab744da7f9a09993fd8
    • downloaded archive SHA-256: a379d01a60157f6ad22de4d933e662a044684bc471ec528de6017e34519498af
    • smoke report SHA-256: 15a7a938504f8c57a8693bf57efec7692c1c4270d3325304bae61234fb203021
    • canonical report content hash: c8cbeb76cc2092ed4b537a0686c00f2ce80a5ba8598a5d7d1d744f51eccd3904
    • Sigstore bundle SHA-256: 2aa75b909c67fe44f464f1b5d78f8f19c36bab0df1d41ffd4121ea5f445ab7a1
    • raw verifier JSON SHA-256: fc47407047615b97ff25a1790ead1dfe090636202ab8ae779216040018b6cab4
    • constrained verification record SHA-256: de1ecfaa304bc403c76752a7fecd0906fe1ea1bfefdc7a94ed54e286e651bc4a
    • Rekor transparency timestamp: 2026-07-20T00:33:02Z
    • predicate: https://slsa.dev/provenance/v1
    • verified attestations/timestamps: 1 / 1
    • constrained record authority: false

    The retained subject digest exactly matches the report. The certificate binds Mnehmos/MathOS, .github/workflows/publication.yml, refs/heads/main, the exact merge commit, push trigger, and github-hosted runner. This is infrastructure evidence only; it does not create authoritative proof/refutation evidence or mathematical truth status.

  7. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Phase 3 publication-authority attack plan

    The current protected workflow proves the OIDC/Sigstore boundary but attests only publication_boundary_smoke/1. It is not a valid input for authoritative evidence. Work will proceed in closed mergeable slices:

    Slice A — canonical publication request preparation (starting now)

    • derive publication_request/1 from one exact stored formalization and exact current accepted elaboration, proof-closure, and axiom-audit evidence;
    • derive evidence hashes, environment, module, declaration, and committed policy hash inside the application rather than accepting caller-authored JSON;
    • recompute and verify every referenced CAS artifact before emitting the request;
    • retain canonical request bytes as a private generated CAS artifact with controlled provenance;
    • expose the same non-authoritative operation through CLI and MCP, with actor/idempotency/dry-run controls;
    • add retry, restart, stale/substituted/missing/corrupt evidence, wrong outcome, and no-authority tests.

    Slice B — real protected candidate closure

    • define a closed role-to-hash publication_closure/1 manifest;
    • add an exact Linux publication environment with enforced memory ceiling;
    • construct fresh canonical state from committed inputs after clean checkout, derive commit/tree at runtime, run Lean plus hole/unsafe/dependency/axiom audits in Bubblewrap, and emit a real publication_report/1;
    • attest the exact report and retain the full closure; every record remains authoritative: false.

    Slice C — controlled attestation ingestion

    • accept only registered CAS report and bundle hashes;
    • invoke only the internally configured, version/hash-pinned gh verifier with typed arguments;
    • parse and constrain raw output, recompute all closure hashes, reject altered/stale/missing inputs, and persist an idempotent non-authoritative verification receipt.

    Slice D — authoritative evidence gate

    • add one atomic Store path that can create only accepted + authoritative + lean_kernel_proof or lean_kernel_refutation for the exact formalization;
    • require the complete verified publication receipt and current canonical closure;
    • keep generic evidence insertion, direct proved/disproved mutation, and caller-authored authority impossible.

    Slice E — derived truth and Pilot A

    Trust decisions: do not ingest the existing smoke as authority; do not accept request/report JSON or verifier arguments from callers; do not relabel local diagnostic evidence as publication evidence; do not set authoritative_verification: true until Slice D is complete.

  8. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Slice A is implemented and published for review in #30.

    Exact candidate:

    This slice prepares canonical publication_request/1 artifacts from current formalization state and exact revalidated evidence. It adds typed proof/refutation intent, transactional current-head/idempotency enforcement, and shared CLI/MCP entry points. Requests remain private generated CAS artifacts and explicitly confer no mathematical authority.

    Still open in #21: protected real-candidate execution, complete retained closure, controlled attestation ingestion, authoritative evidence creation, and fidelity-gated derived truth status. The issue remains open intentionally.

  9. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Post-merge evidence for the exact merged tree:

    • merge commit: da33431a1061bb3f05db7a7d2473f1fb5b8059f2
    • tree: 620f2a3060290ffe37fb3051ff604fa4433679af
    • main CI: https://github.com/Mnehmos/MathOS/actions/runs/29711916515 (all five jobs passed)
    • publication run: https://github.com/Mnehmos/MathOS/actions/runs/29711916501
    • publication job: 88257002282
    • retained artifact: 8449114011
    • artifact archive digest: sha256:3f8b0567519521a29d302ab6dd4f229c59ce2d823ddbf144db01d07458e0fd31
    • smoke report SHA-256: b6edcfc92ed622e847444629ce2b38c1f20afb7b9e065bb75a65bdaa69cb3af9
    • canonical report content SHA-256: 43859d5dac0eb406c39b9dfd08862a8b874bf9102de6fec79d1c36b821864778
    • Sigstore bundle SHA-256: 58013a04bb8f10aac04d55402e605fc169c90abf11fcc22211e98fcbba23d759
    • raw verifier output SHA-256: 541b74172ae4c12f2ce2b31ce2330917a090214c0f1358a3795fcf15f8d99eb0
    • constrained verification record SHA-256: afdef248f30dd3b5d26ba7a342b9bba2a1e569a69fcf62145ee722c1cfd4e40a
    • smoke Lean module SHA-256: 7ac95b59d3c3ca102fc8893117b440477beaa057caa9162683406e9d0f04b4d8

    The downloaded record binds one attestation and one transparency timestamp to the exact protected workflow, commit, ref, and report subject. Both the smoke report and constrained verification record still state authoritative: false; this is infrastructure evidence, not proof authority.

  10. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Security precondition found while reviewing the retained-closure slice:\n\n- gh api repos/Mnehmos/MathOS/branches/main reported protected:false and repository rulesets were empty.\n- The first branch-protection update was rejected with HTTP 422 because personal repositories cannot carry user/team bypass lists; no setting changed on that attempt.\n- A corrected gh api update enabled branch protection on main.\n- Required checks: Rust (ubuntu-latest), Rust (windows-latest), Pinned Lean availability, Real storage smoke test, and Legacy Python regression evidence.\n- Strict checks, pull-request-only changes, stale-review dismissal, conversation resolution, and admin enforcement are enabled.\n- Required approvals remain zero for this single-owner repository; force-pushes and deletions are disabled.\n- A follow-up API read now reports protected:true.\n\nThe in-progress candidate slice also fails closed on GitHub's immutable GITHUB_REF_PROTECTED value, so removing branch protection prevents candidate generation before attestation.\n\nThis is a repository trust-boundary correction only. No proof or refutation authority exists, and all current reports remain �uthoritative:false.

  11. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Slice B is published for hosted verification:\n\n- draft PR: https://github.com/Mnehmos/MathOS/pull/31\n- commit: 7d4bbdc\n- tree: d4265e0ae408dae1a4c8b02c444bb2d216a32222\n- retained closure: 25 fixed roles, including protected Lean parser-derived dependency stdout/stderr\n- shared validator: exact canonical bytes, bounded contained files, Store/CAS replay, source→claim→formalization/evidence/job/report closure, local/protected axiom replay, and dry-run request rederivation\n- protected producer: clean checkout, actively protected main ref, Bubblewrap network/process isolation, cleared environment, timeout, 4 GiB address-space bound, 1 MiB output-file bound, structured failure retention\n- local evidence: 102 Rust tests, real pinned Lean lifecycle, 39 Python tests, warnings-denied Clippy, Bash/YAML/Actionlint, init/health/doctor, and two independent security reviews all passed\n\nThe PR is deliberately draft while the exact hosted Linux candidate path runs. All outputs remain �uthoritative:false; controlled downloaded-attestation ingestion and authoritative evidence creation remain open.

  12. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    First protected-main candidate run after merge failed closed and was retained:

    • source commit 55a0ae0fad9fe5cfd20ed0a5fbddf6b80a5303c1
    • tree 7508582f4ac01b6cd4533c135d7da5f238ad2149
    • publication run https://github.com/Mnehmos/MathOS/actions/runs/29716292659
    • job 88270125287
    • failed artifact 8450708477
    • archive digest sha256:29c70446a4ba089b44621b254bd6ff54ca3a109a836ff8c60a4525e8e7059c27

    The protected-ref workflow gate passed, as did smoke execution, smoke attestation, and the constrained smoke challenge. Candidate construction then exited 65.

    Root cause: the script's report constant RUNNER_ENVIRONMENT=github_hosted shadowed GitHub's immutable RUNNER_ENVIRONMENT=github-hosted, making the protected-only runner comparison unsatisfiable. PR #32 contains the two-line identifier repair and a matching/self-hosted fail-closed context test. No check is bypassed and no authority is created.

  13. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Protected candidate production is now complete and independently inspected.

    Exact merged source:

    Downloaded candidate audit:

    • canonical request: 9f32d3eca940100b92f6ceb91e975fb859f99c1cf97fb98ae859e6cd79419103
    • 25-role retained closure: ff67bc6f101681ff5c8345c763036ca1c07caed4eec714ba8c35f5017a5c28e3
    • publication report: 12f0aaca0f6e9a16c242205da24f53fadc08ba9177cff6e039ec394c50ee1012
    • retained validator result: 1d5adfc932ffa566f859c45caba62d97443e80ee1a3eb4532f792e5ca69362c0
    • attempt summary: 503c86845b6e0a78fa3712b9cf999f78203c15df2550356e3965a12944740ea5
    • candidate Sigstore bundle: a23d190fdaffe7e87fc98747b32525f96f199aa05f5431cba39548b38207a84e
    • raw pinned-gh verification: 1e6063a8ca1ef58476992d8691f702cc39d547ce94d82ebf90a848eef75d549a
    • constrained verification record: 93871363affcfcc6a36d954577779de5791752d2951340c90f77df095c81ce3a
    • verified Rekor timestamp: 2026-07-20T04:22:41Z

    Inspection confirmed exactly 25 sorted fixed-path closure members and all member hashes; source commit/tree/run/attempt agreement; clean checkout; GitHub-hosted protected main; enforced network, memory, time, and output controls; empty environment/formalization imports; protected dependency output containing only /opt/lib/lean/Init.olean; one exact no-axioms result in both local and protected audits; seven intact retained CAS objects; three passed protected execution records; report-subject digest agreement; SLSA v1 predicate; exact workflow certificate identity; exact source commit/ref; GitHub-hosted runner; and one verified timestamp.

    The report, attempt, validator result, and constrained attestation record all remain authoritative:false. This completes candidate production and retained evidence only. Controlled ingestion, authoritative proof/refutation evidence, and mathematical-status derivation remain unavailable.

  14. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Canonical-main follow-up is green after the evidence record merged:

    The exact first protected candidate evidence remains recorded in docs/implementation/STATUS.md. Issue #21 is not complete: controlled ingestion is now the next highest-priority criterion, followed by authoritative evidence creation and mathematical-status derivation.

  15. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Slice C implementation plan — controlled staged-CAS attestation ingestion

    Fresh CLI playtesting reproduced the missing bridge: the genuine protected archive fails closed in a fresh instance with MCL_RECORD_NOT_FOUND, while the producer's populated instance can validate it. This slice will preserve that currentness boundary; it will not import caller-supplied record/evidence snapshots as canonical state.

    Implementation contract:

    • add an immutable, publication-scoped quarantine stage for the exact canonical report, retained-closure manifest, all 25 fixed-role closure members (including empty diagnostic files), and one Sigstore bundle;
    • keep staged bytes in the existing content-addressed store, but keep quarantine registration separate from canonical artifacts metadata so staged inputs cannot acquire trusted provenance;
    • expose a bounded CLI staging command that accepts contained files, rejects symlinks/path escapes/oversize or altered members, validates the closed report/closure semantics, and writes stage metadata idempotently; no stage is authoritative;
    • expose shared CLI/MCP verify ingest-publication with only report_artifact_hash, attestation_bundle_artifact_hash, actor, idempotency key, and dry-run—no report JSON, filesystem root, verifier path, or verifier arguments from callers;
    • resolve the unique stage internally, rehash every CAS member, reconstruct and semantically replay the exact closure against the current canonical Store, and reject missing, altered, stale, or mismatched inputs;
    • resolve the allowlisted gh executable internally, require the committed version and binary SHA-256, invoke gh attestation verify with fixed repository/workflow/ref/commit/predicate/self-hosted-runner constraints, bounded time/output, null stdin, and a reduced environment;
    • parse and constrain the pinned verifier's JSON output: echoed bundle, certificate identity and workflow/repository/ref/commit/run fields, verified identity, SLSA statement subject/digest, builder, resolved dependency, invocation, runner environment, and nonempty transparency timestamp(s);
    • persist canonical publication_attestation_verification/1 bytes, exact raw verifier output, and one immutable idempotent receipt row, all explicitly authoritative:false;
    • add migration, schema/invariant, retry/restart, dry-run, missing/altered/stale/path/symlink/output/parser/verifier-pin tests; keep a local fake/old verifier unable to cross the boundary;
    • update the protected workflow to stage and ingest its exact candidate after GitHub creates the attestation, retain the receipt/raw output, and prove the real pinned gh path on hosted protected main.

    Slice C ends at a durable non-authoritative receipt. It will not create lean_kernel_proof / lean_kernel_refutation evidence or derive proved / disproved; those remain Slice D/E gates.

  16. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Merged-main controlled-ingestion evidence

    PR #34 merged as 95bd8a1d2068612b5eca644c3d77754b5e4f49fd, tree 4027d03fe05bd997108c86250adcf2d920adda48.

    • Main CI run 29721420110 passed Linux Rust, Windows Rust, real storage, pinned Lean plus the staged-CAS barrier, and legacy Python.
    • Protected publication run 29721420136, job 88285050682, passed protected-ref enforcement, clean isolated Lean execution, both exact attestations, both independent challenges, candidate staging, controlled ingestion, and unconditional retention.
    • Artifact 8452528096, publication-boundary-95bd8a1d2068612b5eca644c3d77754b5e4f49fd, is retained for 90 days. GitHub reports archive digest sha256:66cd47753a77f90bf216b874d4d7c99f7ba561a4586e29c524e094c82eb3206c.

    Downloaded byte audit:

    • candidate report: 5f02696eac1308f48eae9f085f003e750f009dbe496d055543792b088e3b2aa6
    • retained closure: 6440836d612d91dfe43af952d6ac83ca1445bf75c86b8b52a8c79f6121427b38
    • candidate Sigstore bundle: c02cde0384cd015bbb085d2f98e69c245888dd7cfbc10973b0c9a9e722ad326c
    • canonical quarantine stage: e4b307416358ef657c57d81d07c6b21df0381befbf5600982442bc435d98baa5
    • raw pinned-gh verification: bdfe54e9e889c52c7dc32941dc8fb16d50b1e2b8071a5b69be04eb1040d45932
    • canonical CAS publication_attestation_verification/1 record and SQLite receipt key: 659b789a41a14ac59ca9253c2c71d73c4717acc58dcc2187809e92c710814402
    • separate independent shell challenge record: ee83075cd636e0359ad3ff27fdb81f059d687ced9a8c1d748fa52ebe8fcb5d3a

    The audit recomputed the canonical stage and verification-record hashes; checked all 71 retained files; matched every one of the 25 exact, ordered closure roles by path, byte size, and SHA-256; confirmed the passed report binds the merge commit, tree, run, attempt, protected workflow, main, GitHub-hosted runner, Lean 4.32.0, empty axiom set, clean checkout, complete dependencies, network isolation, and memory enforcement; and verified every retained stderr file is empty.

    The closed attestation result contains exactly one result, report subject, source dependency, and verified attestation. Its certificate and SLSA fields bind repository ID 1305399818, owner ID 193347153, the protected workflow, merge commit, push event, run/attempt, and GitHub-hosted runner. The verified Rekor timestamp is 2026-07-20T06:22:33Z.

    All 18 retained authoritative fields audited as false. This establishes merged-main controlled provenance ingestion only. It does not create authoritative proof/refutation evidence or mathematical status. The next #21 slice must application-replay the current PublicationIngestionReceiptSnapshot and its full bound CAS closure, require a passed report and current fidelity, then atomically create typed authority without trusting receipt-table presence.

  17. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Slice D candidate — atomic receipt-bound authority

    PR #36 implements the next #21 gate on head 11f5c275a51b30b7871ef7ca3fc68b890ff5f646.

    The public surface accepts only one ingestion-receipt hash plus actor/idempotency/dry-run. The application treats that hash only as a locator and replays the exact stage, passed report, 25 retained roles, request, policy, bundle, raw verifier output, canonical receipt, and current Store state. It derives proof/refutation from typed polarity and passes a non-deserializable commit to one immediate Store transaction.

    Review found and closed a same-environment/same-polarity subject-substitution gap: receipt subject projections must now match the controlled retained request artifact at ingestion, promotion, direct-SQL insertion, and read time. Promotion failure also preserves the exact raw/canonical receipt bytes before the gate runs.

    Local evidence is green: 126 default Rust tests, real Lean 4.32, 39 Python regressions, warnings-denied Clippy, formatting, Bash syntax, Actionlint, and a hands-on CLI smoke. Remote CI/review are now running.

    This slice intentionally creates formalization authority without consuming fidelity. Per SPEC §11, source-claim truth remains unavailable until a later derived read combines exact current authority with exact current verified fidelity. #21 will remain open until the merged protected-main promotion artifact is downloaded and independently audited.

  18. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Exact merged-main publication-authority evidence

    PR #36 merged as 0ef8a132dfb99e63238325ac035de948e893f791, tree f3ed084c9c495de68e20a5a9cdda818fd4637d6b. The reviewed PR head was 761171fb093cecc4b2391ac53ef89c315ff1eeea; PR CI run 29726454494 passed all five required jobs after the final test-only review fix.

    Post-merge evidence:

    • Main CI run 29726693096, attempt 1, passed on the exact merge SHA. Jobs: real storage 88301342236, legacy Python 88301342238, pinned Lean 88301342242, Rust Ubuntu 88301342270, and Rust Windows 88301342459.
    • Protected publication run 29726693055, attempt 1, passed on the same SHA. Boundary job: 88301341952.
    • Retained artifact: 8454565233, publication-boundary-0ef8a132dfb99e63238325ac035de948e893f791, 82,717 bytes.
    • GitHub archive digest: sha256:fae9d075ab9fbd4388474ed51458e6707ba8b9e337f9b18800a8f86e19a0e828. A separate gh api download rehashed to the same SHA-256.
    • main reports protected:true; strict passage of the five named CI checks, pull requests, stale-review dismissal, conversation resolution, and admin enforcement remain enabled. Force pushes and deletions remain disabled.

    Downloaded byte audit:

    • publication request: 3cfe3ebfa30e4446b659081cc8874ccbca684fd51d3b2c53a98b1534423a501c
    • publication policy: 5e9f69968913a7f1f716baa1a1e548f27d5d6958582e75278b37f3fac245f167
    • candidate report: 31934fcc89b045f04f57d4a0807c0f599d188887be56507f296a9fe4d8c9e643
    • retained closure: 20059d3ab54b2e075a7476250cf4de73f9a6c8196dd0005a7a96281d789c87df
    • candidate Sigstore bundle: 99850335bf53d095653fbf59b777cbcc9c33d6fe0a769d71f3c5b8701aa9b42f
    • canonical quarantine stage: 527e4db5e0852268e1eda4d9dc5aa0e32432c6ac76e2b06f130e16aac7dbc9c6
    • raw pinned-gh verification: 6adc6e41385249651adf372ece8334c650013b549093587891b36cafa7087453
    • canonical attestation-verification record and receipt identity: 56166a02475a1d47be9013a024693bc3228801ad98d62c65fca06e6aebd90e40
    • final authority evidence ID: 019f7e90-7adb-7f03-8e37-e591b13eac4d
    • canonical final evidence hash: dbaecfb7163476b98aead72d742891c7d8502494e81bf37e81aa5b214a9ef8cc
    • evidence kind/result/class: lean_kernel_proof / accepted / authoritative
    • authority timestamp/actor: 2026-07-20T08:07:05Z / publication-boundary
    • verified Rekor timestamp: 2026-07-20T08:06:54Z

    The audit checked exactly 72 regular files with no symbolic links, all 25 fixed retained roles by canonical path/identity/byte hash, 24 sorted unique final artifact hashes after content deduplication, all eight empty stderr files, and 18 explicitly false authoritative booleans. The only authoritative semantic is the final evidence/2 payload's authority_class.

    The final payload names formalization 019f7e90-4338-7473-9028-e4bded1f71b8 at version b9b56c5e754d42a7fddf72758d5683e1f3eeeabcbac3bb6f0f321548c51194e6, environment c6d7874c5bafa12e639f04db2a935d966aa742e2a5b4463a6cb688b4614fba1a, and declaration MathOS.Publication.smoke. It has no producing local run/job, no supersession, and no stale state. Its exact nine-field publication_authority_binding/1 matches the receipt, stage, report, closure, bundle, raw verification, request, and policy hashes above.

    The certificate and SLSA statement bind immutable repository/owner IDs, the protected workflow, refs/heads/main, push event, exact merge commit, run/attempt, GitHub-hosted runner, and exact report subject. Candidate, stage, ingestion, validation, and verification records remain non-authoritative.

    This completes issue #21's receipt-bound formal proof-authority boundary. It does not create source-claim proved status: derived truth remains unavailable until a separate read combines exact current authority with exact current verified statement fidelity and the remaining SPEC preconditions. MathOS 1.0 is not complete.

  19. Mnehmos commented on Jul 20, 2026

    @Mnehmos
    OwnerAuthor

    Canonical-main follow-up after the evidence ledger merge

    PR #37 merged as fe60adf037ebe6a67ce8a96bf29fdb256ebde0d2, tree abce3ff03d3f8821d07ed73d94f8e85c808a6f90.

    • Main CI run 29727800832 passed all five jobs on that exact SHA: real storage 88304834787, Rust Ubuntu 88304834804, legacy Python 88304834850, pinned Lean 88304834854, and Rust Windows 88304835029.
    • Protected publication run 29727800801, job 88304834439, passed every candidate, attestation, challenge, ingestion, authority-promotion, and retention step.
    • Artifact 8454995294, publication-boundary-fe60adf037ebe6a67ce8a96bf29fdb256ebde0d2, is 82,746 bytes. GitHub reports sha256:a0de61913a4cb35f898602791fd4f7bce7848fa8d24a46687d862f737d61b7cd; a separate gh api ZIP download reproduced the same hash.
    • The parameterized independent audit passed all 72 files, 25 retained roles, 24 deduplicated final artifact hashes, eight empty stderr files, 18 false boolean authority fields, exact commit/tree/run/attestation identities, and the sole final authoritative semantic.
    • Current authority evidence: ID 019f7ea2-34fe-72d3-bdce-6d5b2e4e5b0b, canonical hash 6702807d369a3d0653d97b57d515610ef1f2ca679a5afc236fbca045cc3b20d9, kind lean_kernel_proof, actor publication-boundary, timestamp 2026-07-20T08:26:27Z.
    • Current formalization subject: 019f7ea2-0036-7331-8ea4-ccf3423134da at version fa8e61403cc1d55d8313f49d80c98535f8ad2d2c02f8625551f87d7b4fd956d6; request b70357cb89a927ccba60f30dcd5133ae880fc9ea525151b44f2b53329ed5e186; receipt 9cad0a04843ec091e082213ba39e17495ef101fd03b06615e8a3bb3ff7333112; protected report bf0b597a0b75d595005d6d2dc8a472053e92e8060b559c070929ac4ed7a856eb; retained closure 292563112c1158ad5e366d8359389f52550f51eb20dffd8d86a6780699142745.
    • Verified Rekor timestamp: 2026-07-20T08:26:16Z.

    The evidence ledger is therefore healthy on current canonical main. This remains exact formalization authority only; no source-claim truth or MathOS 1.0 completion is claimed.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0