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
{{ message }}
Repository navigation
Phase 3: define publication-profile proof authority and retained evidence #21
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;
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.
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.
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.
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.
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.
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
derive claim truth only when exact current verified fidelity and authoritative proof/refutation evidence both apply;
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Activity
docs: advance the ledger to publication authority
Mnehmos commentedon Jul 19, 2026
Issue #21 contract slice is published.
This slice adds:
9cac0ae88eb00e84474ce9f7a2357b5b8677beb6e042d163f95c78a453c34a2b;actions/attestand artifact retention identities;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:
bb9cff8894bf43927c3106d8a452c9932c656460Exact local and GitHub tree:
ac36221dfb268fc0b60e0aabaf70bd31bae57699No authoritative evidence or mathematical status exists in this slice. Protected candidate generation, attestation, verified ingestion, and promotion remain active.
Mnehmos commentedon Jul 19, 2026
Publication authority contract checkpoint passed GitHub Actions run
29706570941on exact treeac36221dfb268fc0b60e0aabaf70bd31bae57699. 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.
Merge spec-driven MathOS foundation
Mnehmos commentedon Jul 19, 2026
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:
367ff24ba0091009aaeeade1eda402838348b585Exact tree:
1cba96a24c6759c52216f7a626d2f0ef7ea93d51I am monitoring the hosted Linux result and will repair the boundary in place if adversarial CI exposes a platform assumption.
Mnehmos commentedon Jul 19, 2026
Checkpoint: the first protected
mainboundary is now independently inspectable. Publication run29707995584passed on merge commit31ccfdda41d538bde7e01e061865580cab2f04e5and retained artifact8448453305for 90 days. The archive digest is0e3d0007da30460b1918d98fea39fad08cffda4b0249035a88bb9a1cd2d30896; the exact report digest is08bead82cea25ffdfc3424084cb0878f2a648b3375317daa0c799395751dba40; and the Sigstore bundle digest is5dd23a13fa66efef8885e2116bd994bce92244a290c3ce0d9467d5eeb6d5ac14. 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/1and authoritative exact evidence remain open.Mnehmos commentedon Jul 20, 2026
Protected publication evidence for the merged correction:
d10cb27a620bf0f3b5c4881a55aeee53179b4a90e5b0bcbf4eacf9cb402d87b04b5dc9b0431134f26b4a0f22d3498a4cb0c8dab744da7f9a09993fd8e5b0bcbf4eacf9cb402d87b04b5dc9b0431134f229709569292(all five jobs passed on the PR head)29709634846, attempt 1882517098188448739399,publication-boundary-6b4a0f22d3498a4cb0c8dab744da7f9a09993fd8a379d01a60157f6ad22de4d933e662a044684bc471ec528de6017e34519498af15a7a938504f8c57a8693bf57efec7692c1c4270d3325304bae61234fb203021c8cbeb76cc2092ed4b537a0686c00f2ce80a5ba8598a5d7d1d744f51eccd39042aa75b909c67fe44f464f1b5d78f8f19c36bab0df1d41ffd4121ea5f445ab7a1fc47407047615b97ff25a1790ead1dfe090636202ab8ae779216040018b6cab4de1ecfaa304bc403c76752a7fecd0906fe1ea1bfefdc7a94ed54e286e651bc4a2026-07-20T00:33:02Zhttps://slsa.dev/provenance/v11/1falseThe 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, andgithub-hostedrunner. This is infrastructure evidence only; it does not create authoritative proof/refutation evidence or mathematical truth status.Mnehmos commentedon Jul 20, 2026
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)
publication_request/1from one exact stored formalization and exact current accepted elaboration, proof-closure, and axiom-audit evidence;generatedCAS artifact with controlled provenance;Slice B — real protected candidate closure
publication_closure/1manifest;publication_report/1;authoritative: false.Slice C — controlled attestation ingestion
ghverifier with typed arguments;Slice D — authoritative evidence gate
accepted+authoritative+lean_kernel_prooforlean_kernel_refutationfor the exact formalization;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: trueuntil Slice D is complete.Mnehmos commentedon Jul 20, 2026
Slice A is implemented and published for review in #30.
Exact candidate:
1dbcab26aa5a31561b113abf48d9746c7ff6c2f5620f2a3060290ffe37fb3051ff604fa4433679afThis slice prepares canonical
publication_request/1artifacts 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.
Mnehmos commentedon Jul 20, 2026
Post-merge evidence for the exact merged tree:
da33431a1061bb3f05db7a7d2473f1fb5b8059f2620f2a3060290ffe37fb3051ff604fa4433679af882570022828449114011sha256:3f8b0567519521a29d302ab6dd4f229c59ce2d823ddbf144db01d07458e0fd31b6edcfc92ed622e847444629ce2b38c1f20afb7b9e065bb75a65bdaa69cb3af943859d5dac0eb406c39b9dfd08862a8b874bf9102de6fec79d1c36b82186477858013a04bb8f10aac04d55402e605fc169c90abf11fcc22211e98fcbba23d759541b74172ae4c12f2ce2b31ce2330917a090214c0f1358a3795fcf15f8d99eb0afdef248f30dd3b5d26ba7a342b9bba2a1e569a69fcf62145ee722c1cfd4e40a7ac95b59d3c3ca102fc8893117b440477beaa057caa9162683406e9d0f04b4d8The 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.Mnehmos commentedon Jul 20, 2026
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.
Mnehmos commentedon Jul 20, 2026
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.
Mnehmos commentedon Jul 20, 2026
First protected-main candidate run after merge failed closed and was retained:
55a0ae0fad9fe5cfd20ed0a5fbddf6b80a5303c17508582f4ac01b6cd4533c135d7da5f238ad2149882701252878450708477sha256:29c70446a4ba089b44621b254bd6ff54ca3a109a836ff8c60a4525e8e7059c27The 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_hostedshadowed GitHub's immutableRUNNER_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.Mnehmos commentedon Jul 20, 2026
Protected candidate production is now complete and independently inspected.
Exact merged source:
fc9116492a60fd891bbb1a175096002c8ab504a45dc109a29888c7ac34e67cdd6fb84454947133e5882712221448450846116sha256:1e0ecbf1ca9250494e164ffe8fe093e4b2a99ca4aa34bcaa1126c9a698ff26e6Downloaded candidate audit:
9f32d3eca940100b92f6ceb91e975fb859f99c1cf97fb98ae859e6cd79419103ff67bc6f101681ff5c8345c763036ca1c07caed4eec714ba8c35f5017a5c28e312f0aaca0f6e9a16c242205da24f53fadc08ba9177cff6e039ec394c50ee10121d5adfc932ffa566f859c45caba62d97443e80ee1a3eb4532f792e5ca69362c0503c86845b6e0a78fa3712b9cf999f78203c15df2550356e3965a12944740ea5a23d190fdaffe7e87fc98747b32525f96f199aa05f5431cba39548b38207a84eghverification:1e6063a8ca1ef58476992d8691f702cc39d547ce94d82ebf90a848eef75d549a93871363affcfcc6a36d954577779de5791752d2951340c90f77df095c81ce3a2026-07-20T04:22:41ZInspection 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.Mnehmos commentedon Jul 20, 2026
Canonical-main follow-up is green after the evidence record merged:
b7879350d350208dcf5374127ec071a0d588f1f1698176b6ce4057b865030727748904edaa395616The 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.Mnehmos commentedon Jul 20, 2026
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:
artifactsmetadata so staged inputs cannot acquire trusted provenance;verify ingest-publicationwith onlyreport_artifact_hash,attestation_bundle_artifact_hash, actor, idempotency key, and dry-run—no report JSON, filesystem root, verifier path, or verifier arguments from callers;ghexecutable internally, require the committed version and binary SHA-256, invokegh attestation verifywith fixed repository/workflow/ref/commit/predicate/self-hosted-runner constraints, bounded time/output, null stdin, and a reduced environment;publication_attestation_verification/1bytes, exact raw verifier output, and one immutable idempotent receipt row, all explicitlyauthoritative:false;ghpath on hosted protectedmain.Slice C ends at a durable non-authoritative receipt. It will not create
lean_kernel_proof/lean_kernel_refutationevidence or deriveproved/disproved; those remain Slice D/E gates.Mnehmos commentedon Jul 20, 2026
Merged-main controlled-ingestion evidence
PR #34 merged as
95bd8a1d2068612b5eca644c3d77754b5e4f49fd, tree4027d03fe05bd997108c86250adcf2d920adda48.29721420110passed Linux Rust, Windows Rust, real storage, pinned Lean plus the staged-CAS barrier, and legacy Python.29721420136, job88285050682, passed protected-ref enforcement, clean isolated Lean execution, both exact attestations, both independent challenges, candidate staging, controlled ingestion, and unconditional retention.8452528096,publication-boundary-95bd8a1d2068612b5eca644c3d77754b5e4f49fd, is retained for 90 days. GitHub reports archive digestsha256:66cd47753a77f90bf216b874d4d7c99f7ba561a4586e29c524e094c82eb3206c.Downloaded byte audit:
5f02696eac1308f48eae9f085f003e750f009dbe496d055543792b088e3b2aa66440836d612d91dfe43af952d6ac83ca1445bf75c86b8b52a8c79f6121427b38c02cde0384cd015bbb085d2f98e69c245888dd7cfbc10973b0c9a9e722ad326ce4b307416358ef657c57d81d07c6b21df0381befbf5600982442bc435d98baa5ghverification:bdfe54e9e889c52c7dc32941dc8fb16d50b1e2b8071a5b69be04eb1040d45932publication_attestation_verification/1record and SQLite receipt key:659b789a41a14ac59ca9253c2c71d73c4717acc58dcc2187809e92c710814402ee83075cd636e0359ad3ff27fdb81f059d687ced9a8c1d748fa52ebe8fcb5d3aThe 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
passedreport 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 ID193347153, the protected workflow, merge commit, push event, run/attempt, and GitHub-hosted runner. The verified Rekor timestamp is2026-07-20T06:22:33Z.All 18 retained
authoritativefields audited asfalse. 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 currentPublicationIngestionReceiptSnapshotand its full bound CAS closure, require apassedreport and current fidelity, then atomically create typed authority without trusting receipt-table presence.Mnehmos commentedon Jul 20, 2026
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.
Mnehmos commentedon Jul 20, 2026
Exact merged-main publication-authority evidence
PR #36 merged as
0ef8a132dfb99e63238325ac035de948e893f791, treef3ed084c9c495de68e20a5a9cdda818fd4637d6b. The reviewed PR head was761171fb093cecc4b2391ac53ef89c315ff1eeea; PR CI run29726454494passed all five required jobs after the final test-only review fix.Post-merge evidence:
29726693096, attempt 1, passed on the exact merge SHA. Jobs: real storage88301342236, legacy Python88301342238, pinned Lean88301342242, Rust Ubuntu88301342270, and Rust Windows88301342459.29726693055, attempt 1, passed on the same SHA. Boundary job:88301341952.8454565233,publication-boundary-0ef8a132dfb99e63238325ac035de948e893f791, 82,717 bytes.sha256:fae9d075ab9fbd4388474ed51458e6707ba8b9e337f9b18800a8f86e19a0e828. A separategh apidownload rehashed to the same SHA-256.mainreportsprotected: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:
3cfe3ebfa30e4446b659081cc8874ccbca684fd51d3b2c53a98b1534423a501c5e9f69968913a7f1f716baa1a1e548f27d5d6958582e75278b37f3fac245f16731934fcc89b045f04f57d4a0807c0f599d188887be56507f296a9fe4d8c9e64320059d3ab54b2e075a7476250cf4de73f9a6c8196dd0005a7a96281d789c87df99850335bf53d095653fbf59b777cbcc9c33d6fe0a769d71f3c5b8701aa9b42f527e4db5e0852268e1eda4d9dc5aa0e32432c6ac76e2b06f130e16aac7dbc9c6ghverification:6adc6e41385249651adf372ece8334c650013b549093587891b36cafa708745356166a02475a1d47be9013a024693bc3228801ad98d62c65fca06e6aebd90e40019f7e90-7adb-7f03-8e37-e591b13eac4ddbaecfb7163476b98aead72d742891c7d8502494e81bf37e81aa5b214a9ef8cclean_kernel_proof/accepted/authoritative2026-07-20T08:07:05Z/publication-boundary2026-07-20T08:06:54ZThe 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
authoritativebooleans. The only authoritative semantic is the finalevidence/2payload'sauthority_class.The final payload names formalization
019f7e90-4338-7473-9028-e4bded1f71b8at versionb9b56c5e754d42a7fddf72758d5683e1f3eeeabcbac3bb6f0f321548c51194e6, environmentc6d7874c5bafa12e639f04db2a935d966aa742e2a5b4463a6cb688b4614fba1a, and declarationMathOS.Publication.smoke. It has no producing local run/job, no supersession, and no stale state. Its exact nine-fieldpublication_authority_binding/1matches 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
provedstatus: 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.Mnehmos commentedon Jul 20, 2026
Canonical-main follow-up after the evidence ledger merge
PR #37 merged as
fe60adf037ebe6a67ce8a96bf29fdb256ebde0d2, treeabce3ff03d3f8821d07ed73d94f8e85c808a6f90.29727800832passed all five jobs on that exact SHA: real storage88304834787, Rust Ubuntu88304834804, legacy Python88304834850, pinned Lean88304834854, and Rust Windows88304835029.29727800801, job88304834439, passed every candidate, attestation, challenge, ingestion, authority-promotion, and retention step.8454995294,publication-boundary-fe60adf037ebe6a67ce8a96bf29fdb256ebde0d2, is 82,746 bytes. GitHub reportssha256:a0de61913a4cb35f898602791fd4f7bce7848fa8d24a46687d862f737d61b7cd; a separategh apiZIP download reproduced the same hash.019f7ea2-34fe-72d3-bdce-6d5b2e4e5b0b, canonical hash6702807d369a3d0653d97b57d515610ef1f2ca679a5afc236fbca045cc3b20d9, kindlean_kernel_proof, actorpublication-boundary, timestamp2026-07-20T08:26:27Z.019f7ea2-0036-7331-8ea4-ccf3423134daat versionfa8e61403cc1d55d8313f49d80c98535f8ad2d2c02f8625551f87d7b4fd956d6; requestb70357cb89a927ccba60f30dcd5133ae880fc9ea525151b44f2b53329ed5e186; receipt9cad0a04843ec091e082213ba39e17495ef101fd03b06615e8a3bb3ff7333112; protected reportbf0b597a0b75d595005d6d2dc8a472053e92e8060b559c070929ac4ed7a856eb; retained closure292563112c1158ad5e366d8359389f52550f51eb20dffd8d86a6780699142745.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.