Skip to content

Tracker: how close optifab is to a verified system that improves its own hardware and software #3

Open
0 of 9 issues completed

Description

@abu-aska

This tracks the distance between what optifab delivers and the vision: a fully end-to-end formally verified, recursively improving intelligence system that evolves its hardware and software together, as one unit. The full account is docs/VISION.md, and the proposals are docs/PROPOSALS.md. Prior work that set the idea: #1.

Where it stands

v0.2.0 is on main (#2, merged). v0.3.0 is in #13, a draft. Both are claimed work and no person has reviewed either. The "Exists" column below describes v0.3.0.

Part of the vision Exists Missing
Formally verified Fifteen theorems in Lean, accepted by lake comparator --paranoid under six kernels. Eight are about the gate. Seven are about designs: the plant model, the bounds, the objective and the step are inside the proved code. Proven Commons bar items 2 to 6 pass. A reviewer's approval of the specification (bar item 1, #8). A branch rule on main (bar item 7). Any proof that the model describes a real plant. Five known defects in the model (#14).
End to end One command runs certificates → design → margins and objective → step → ledger. A second works 3,071 decisions out again in Lean from the designs, and runs each ledger in one piece through the proved loop, with no mismatch. Both ends: no sensor feeds it (#4) and nothing obeys it (#5). 4 of 10 loop interfaces are checked.
Recursively improving loop_never_worse: whatever is proposed, the objective of the design held cannot fall. The notes one proposer left were given to the next, which needed 4 proposals where the first needed 11. The hand-over was done once, by hand, in prose. Nothing improves the gate, the model or the proposer's own code. A design that ties is taken up, so "never worse" is not "always better" (#14). The objective drives the design onto a limit, where it can no longer change (#6).
Intelligence A language model proposed through the loop's interface, seeing only the printed state, and reached the best objective a direct search finds. Two recorded runs of one model. Neither Weft nor Exo proposes anything (#6).
Hardware and software One design: 3 hardware genes, 2 software genes, one step, one ledger. The model's proposals changed both in the same step. The hardware is three numbers in a thermal model (#7). Nothing structural moves and nothing is built (#10).
One unit One predicate, one 64-byte frame, one margin vector, one record. 32 of 41 repositories placed. No shared interface in code between the four organisations yet (#4, #9).
A network A first look: the load floor depends on the site, and placement between campuses is degenerate in the current plant model. A model with a cost that differs by site (#11).

The theorems that carry the weight: loop_safe (from a start within its limits, whatever designs are proposed, the margins the model computes stay within the limit and the budget is never overdrawn), loop_never_worse (the objective never falls), loop_bounded (the number of changes is at most the budget a person set) and loop_keeps_physics (a margin within its limit means an exact inequality about heat or storage). They are about the model. None says the model's constants are true, and an independent read found mistakes in the model itself (#14).

Proposals and open work

Each is a sub-issue with a first slice and a test that can fail.

Decisions waiting on a person

Open in other repositories

Boundaries

The gate refuses; it does not command. A person sets the budget and authorises. Nothing here moves a valve, a load or a machine, and nothing may be called verified until a person who did not write the specification approves it.

Filed by an AI agent (Claude Code) working for the owner of aska-physical.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions