Intent becomes settled phases.
python/crank turns a vague task into ordered phases. Each phase must
produce a non-empty output, pass a gate, and avoid repeating earlier output.
Verified builds become recipes.
scripts/forge_speak.py checks build memory first. A matching verified
recipe skips planning, but still rebuilds and re-runs the spec.
The map stays inspectable.
scripts/village.py makes a flow map compile into code.
scripts/forge_torus.py gives a build a reversible topological address.
Run it
Plain English to verified build.
python scbe.py prove forgeExpected behavior: the controller parses capabilities, assembles a real app, runs the requested commands, emits a reversible prime deed, then runs the same request again through build memory. It reports BUILT + VERIFIED: YES only after execution.
Reuse rule
Memory is not a shortcut around proof.
python scbe.py prove black-boxThe Black Box proof path builds the buyer ZIP, runs the included scanner locally, and prints the top finding plus text/JSON report paths. It is the same rule: show the artifact, run it, and print where the result landed.
Mechanical model
Why this is useful.
- Mechanical calculator lesson: no half-turned gears; every phase must settle.
- Fixed-point lesson: convert vague work into bounded representation before running.
- Topology lesson: lift the run into a structure where drift and collisions show up.
- Product lesson: a buyer gets a workflow route, catalog, receipts, and next fixes.
Scope boundary
What this does not claim.
This page does not claim legal protection, certification, autonomous correctness, or universal safety. It shows a concrete workflow-control mechanism: bounded phases, verification, memory reuse that re-verifies the run, and inspectable build addresses.