Repository navigation
optifab v0.2.0: one structure for four organisations' work, with a gate proved in Lean and a loop that runs on it - #2
Merged
Conversation
optifab is the design of one physical structure that holds the work of aska-physical, Foundation-0, Moissanite-Labs and Proven-Commons, so that digital and physical infrastructure are a single unit. The idea comes from the Terrafab documents named in issue 1. The reference structure is funi-frame's 10 MW campus. Status: claimed. Nothing here is measured. - verify.py recomputes every figure from pinned inputs and runs 19 must-fail controls: extra IT load at a fixed supply (2.85 to 2.96 MW, against 3.06 MW of freed utility power), the recooling limit of the sorption stage (41.5 C at best), the self-cooling load floor (0.56 MW), the thermal budget (2,500 kWh_th) and a margin vector of 12 limit states. - plant_gate re-implements Weft's gate predicate. It passes Weft's 15 weight-update vectors and agrees with Weft's own function on 100,000 generated cases. Its budget and radius are now physical quantities. - The contract's state fits the 64-byte layout of Weft's telemetry frame. - data/unit.json places 32 of 41 repositories in the structure and lists the loop's 9 interfaces; 3 are checked and the loop is open. - data/graph.json maps 41 repositories and 43 cited links; every cited line is pinned to a commit and re-read by verify.py --upstream. - HANDOFF.md records negative findings, notes for upstream maintainers and a queue of eleven proposed issues. Prepared by an AI agent and reviewed by a second AI agent. Not reviewed by a person. Refs #1 Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012tWK9W6CVMEDEnj5eQTe6K
… text and data Noncommercial use is open; commercial use is reserved to the copyright holder. Third-party files keep their own terms, listed in NOTICE. The owner should confirm the copyright line in NOTICE. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012tWK9W6CVMEDEnj5eQTe6K
…s bar formal/ is a Lean 4 project with no dependencies. It defines an exact integer gate (margins in parts per million, no floating point), the generation step that makes an admitted candidate the new baseline, and the loop over any list of proposals. Eight theorems are proved, among them: - run_safe: whatever is proposed, in whatever order, every margin stays at or below its limit and the budget is never overdrawn; - run_bounded: the number of changes the loop admits is at most the budget it was given. `lake comparator --paranoid` accepts all eight under every kernel shipped with Lean, with the standard axioms only. 300,000 differential tests against the Python oracle agree. The Proven Commons bar check (Proven-Commons/mission at 7b22e54) reports items 2 to 6 PASS and item 1 OPEN: no reviewer has approved the specification, and none can yet, because the reviewer list is empty. The project is not verified and does not say it is. Also adds two workflows: the bar check on formal/, and a rerun of verify.py. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012tWK9W6CVMEDEnj5eQTe6K
…r the proved gate loop.py holds a genome of three hardware genes (thermal store, liquid capture, wall U-value), two software genes (scheduler load floor, load shed in an outage) and the proposer's own step scale. Each generation a change is proposed, the plant model turns it into 14 margins, and the exact gate decides. Admitted candidates become the next baseline. Every decision is recorded in a hash-chained ledger (results/ledger.json). On the scenario defined in loop.py: 50 proposals, 45 admitted (30 hardware, 15 software), 5 refused by the gate; the objective rose from 0.914228 to 0.919009 and never fell; no admitted state passed a limit. verify.py --formal rebuilds the proofs, runs the comparator and the differential tests, and replays every ledger decision through the Lean executable: 50 decisions, 0 mismatches (results/formal.json). The plain verifier checks that this record matches the current Lean sources and ledger. Five must-fail controls added (24 in all). Version 0.2.0. The plant model, the objective and the proposer are not proved. The scenario is a choice, so the figures are illustrations. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012tWK9W6CVMEDEnj5eQTe6K
… the structure - docs/VISION.md takes the vision apart (formally verified, end to end, recursively improving, intelligence, hardware and software, cohesive) and says for each part what exists and what does not. - docs/PROPOSALS.md proposes eight systems for the open gaps, each with a first slice and a test that can fail. - The unit now lists the proved gate and the loop (30 elements, 10 loop interfaces, 4 checked). README, MODEL, STRUCTURE, HANDOFF and CHANGELOG updated for v0.2.0. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012tWK9W6CVMEDEnj5eQTe6K
This was referenced Nov 17, 2026
Open
ahrazzle
marked this pull request as ready for review
November 17, 2026 16:06
ahrazzle
self-requested a review
November 17, 2026 16:06
This was referenced Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
First content for optifab: the design of one physical structure that holds the work of all four organisations (aska-physical, Foundation-0, Moissanite-Labs, Proven-Commons), so that the digital and the physical infrastructure are a single unit. The idea comes from the Terrafab documents named in #1. The reference structure is funi-frame's 10 MW campus.
Status: claimed. Nothing here is measured. Every number is derived from other repositories' certificates, which are themselves models. An AI agent prepared this. Nothing in it may be called verified: the proofs are machine-checked, but no person has approved their specification.
Refs #1. The distance to the vision is tracked in #3, with eight proposals as sub-issues (#4 to #11).
How close to the vision
docs/VISION.mdtakes the vision apart: a fully end-to-end formally verified, recursively improving intelligence system that evolves its hardware and software together.lake comparator --paranoidunder six kernels. Proven Commons bar items 2 to 6 pass.The two theorems that carry the weight, both in
formal/:run_safe: whatever is proposed, in whatever order, every margin stays at or below its limit and the budget is never overdrawn. No condition is put on the proposer.run_bounded: the number of changes the loop admits is at most the budget a person set.Both are about the gate's arithmetic. Neither says the margins fed to it are true.
Findings
Each is derived in
docs/MODEL.mdand recomputed byverify.py.formal/follows the Proven Commons layout and has no dependencies.What is in the diff
verify.py: derivations, both gates, the plant frame, the loop, graph and unit checks, 24 must-fail controls.--formalrebuilds the proofs and replays the ledger in Lean.loop.py: the improvement loop.formal/: the Lean project, withSPEC.md,bar.toml, differential tests andBAR-REPORT.md.results/: the certificate, the ledger and the record of the last formal run.data/: vendored inputs with hashes, 48 pins, the graph, the unit, and the commits of 36 repositories.docs/:VISION.md,PROPOSALS.md,STRUCTURE.md,MODEL.md,CONVERGENCE.md(generated).LICENSE(PolyForm Noncommercial 1.0.0, code),LICENSE-docs(CC BY-NC 4.0, text and data),NOTICE,HANDOFF.md,CHANGELOG.md.formal/, and a rerun ofverify.py. Both are green on this head.How to check
What a reviewer should look at first
formal/SPEC.mdandformal/PlantGate/Spec.lean. An AI agent wrote the specification. Until a person who did not write it approves it, the gate is proved against a specification nobody has checked (Proposal 5: a reviewer for the gate's specification, so it can be called verified #8).loop.pyare choices. The 0.5% gain is an illustration. The behaviours in finding 15 are properties of the gate.data/unit.jsonwere assigned here.NOTICE("Aska Physical and the optifab contributors") needs the owner's confirmation.Not done
HANDOFF.mdsection 3 says how to refresh.Disclosure
Prepared by an AI agent (Claude Code) working for the owner of aska-physical. A second AI agent reviewed the first version, given the code and not the conclusions;
HANDOFF.mdsection 7 lists what it found and what was fixed. Under the Foundation-0 rule that a person signs, this does not count until a named person has reviewed it.🤖 Generated with Claude Code
https://claude.ai/code/session_012tWK9W6CVMEDEnj5eQTe6K