HomeBuilt: Benji-to-Build-Pack contract
Benji → review → sourcing, don’t lose the review bit. Need units / dimensions / quantities attached to the design revision, otherwise the pretty picture and the parts can drift apart
Walkthrough in the pitch: photograph the intended space, choose a library design, customize it with Benji, generate instructions/materials, and deliver the pack. The dog-house example supplies a single concrete design for tracing this flow.
A-frame doghouse order-summary mock-up.
Benji waiting on a corgi-friendly design request.
Doghouse ventilation edit in the Benji mock-up.
Roof dimensions and a typed Benji request.
Roof material controls and Benji keyboard input.
Roof-color picker with Benji recommendations.
Alternate roof-color picker view.
Selected roof component, material and dimensions.
Camera framing grid and Scan with Benji control.
Benji prototype chat and doghouse preview.
Little Free Library sample guide: box frame and gables.
Little Free Library sample guide: roof, tools and materials.
Little Free Library sample guide: trim and door assembly.
Important handoff: the earlier video script explicitly inserts human review after Benji SUPER generates the instruction manual and before sourcing/packing. Keep that review step in the workflow instead of implying an unchecked model output becomes a physical build.
Data contracts to define: design revision ID; units and dimensions; component quantities/specifications; inventory references; ordered assembly steps; tool requirements; reviewer decision; and any substitutions. These fields are proposed here to make the recorded workflow inspectable—the draft does not supply a final database schema.
Open questions: which edits are permitted by each template, how are unsupported requests rejected, and how is a material substitution checked against load/fit constraints? The pitch names Benji and Benji SUPER, but does not include a reproducible training recipe, weights, prompt set or source-code path. Do not infer those from marketing claims.