cad

Motion verification is opt-in. Standalone make_round and verify_project default to false; pass --check-motion true to enable it. Inside Workshop, read the immutable run-root MAKE-OPTIONS.json: the tools inherit its check_motion value and reject contradictory flags. A missing options file in an older materialized run retains its mandatory motion policy. When false, skip motion sweeps and required animation/reconstruction/review, even if a manifest or assembly claims exist. Motion is unverified, never passed; do not claim assemblability or working motion from skipped evidence. Build, fit, print gates and still-image review remain required. These rules take precedence over motion-specific requirements in references and templates.

A correction carries unchanged parts forward. This is the default for workshop fix, recorded as carry_unchanged in the run-root MAKE-OPTIONS.json under schema_version: 2; motion_policy.carry_unchanged() reads it. It is false for every run with no source to carry from, and for every run created before the policy existed -- those have no schema-2 document, so a refreshed tool still reads them the way they were created. workshop fix --full declines it. The policy changes only what a round may CARRY FORWARD. It lowers no threshold, relaxes no gate and skips nothing about the assembly.

A seeded run records its Approved Proof. workshop wish|fix --seed-source (Workshop ADR 0096) freezes seed: {approval_sha256, manifest_sha256} under schema_version: 3, beside check_motion and, for a correction, carry_unchanged: true; motion_policy.seed() reads it and is None for every other run. It changes no gate.

What it permits, and only after the changed-part set is established by building and exporting EVERY part and hashing each against the source archive's make/made.json product_manifest:

• A part whose STEP is byte-identical to the source's needs no new isolated component round. The source archive's round history for that part is still exactly true of it, because a gate is a pure function of the STEP it reads. Carry that history forward and record the hash it is carried on.
• Its per-part measure reports are carried forward the same way, unchanged.

You are not trusted on this, and do not need to be: make_round --require-component-passes rebuilds every part and refuses assembly review for any whose digest no longer matches its recorded pass. A part that moved cannot be carried even if you try.

What the policy never touches:

• The hash proof itself. It is the whole warrant for everything above, so it is computed fresh, over every part, every time.
• refs:assembly, validate:assembly and interfere:assembly. The assembly changes whenever any part does, and interference is a property of the whole set, never of a part.
• Every gate on every CHANGED part, and the assembled-object rounds.
• verify_project, the whole-set renders and the independent blind review. The final sweep is what would catch a mistake in the carry-forward reasoning, so scoping it would remove the one check that makes the rest safe.

Write a measure/quick-fix-carry.md naming every part carried forward, the sha256 it was carried on, and what was regenerated instead. A reader must be able to tell a carried report from a fresh one without diffing, because the round record itself cannot say which run produced it. If the changed-part set turns out to be most of the project, say so and regenerate everything: the policy saves nothing there and the claim is weaker.

CAD generation, inspection, and validation

Provenance: maintained in earthtojake/text-to-cad. Use the installed local skill files as the runtime source of truth; the repository link is only for provenance and release review.