# RUN — Inside the Machine / initial delivered candidate

## Identity and scope

This is an original independent pilot inspired by a public example, not a recovered private prompt and not a model comparison. The directed production brief was implemented in this task’s own local workspace. The short comparison variant, common comparison contract and larger matrix were not run.

Status: initial candidate complete, locally runnable, exported and verified. First delivered candidate is the project and exports beside this file, frozen in `../inside-the-machine-initial.zip`. Preserve that ZIP before any future review correction. **No separate post-delivery targeted correction has been used.** The internal debugging and export fixes listed below happened before the first delivery, under the explicitly authorized initial implementation/verification allowance.

## Times and observable runtime

| Measurement | Recorded value |
| --- | --- |
| UTC start | 2026-09-07 03:10:44 UTC |
| UTC completion record | 2026-09-07 03:43:12 UTC |
| Overall elapsed work | 1948.3 seconds (32.47 minutes), including research, builds, browser QA, captures and packaging |
| First capture started | 2026-09-07T03:32:42.770Z |
| First pre-delivery export pass | 89.577 seconds total; 71.225 capture + 1.778 encoding |
| Final production build | 4.964 seconds; start 2026-09-07T03:36:00.158Z; end 2026-09-07T03:36:05.122Z; exit 0 |
| Final export started | 2026-09-07T03:36:26.549Z |
| Final export ended | 2026-09-07T03:37:36.337Z |
| Final browser frame capture | 59.540 seconds |
| Final MP4 encoding | 1.680 seconds |
| Final export pass total | 69.787 seconds, including browser setup, screenshots and GLB |
| Requested controller model / effort | gpt-6-astra / Ultra |
| Actual model / effort / speed setting | unknown / unknown / unknown; no authoritative per-run telemetry exposed these settings |
| Token totals / dollar cost | not observable; no costs invented |

The final production build time is distinct from the much longer authoring/verification elapsed time. The first capture was inspected and replaced after material cover/framing defects; its timing record is retained. A targeted assembled screenshot was subsequently refreshed after waiting for its selected tab to settle; the final MP4 was already correct and was not re-encoded for that screenshot-only fix.

Shared-account usage snapshots: 26% used at the beginning, 36% during final export, 37% near completion, in the 10,080-minute window. Other tasks were active on this account. These are account-level observations, not this task’s consumption, and no per-task percentage or monetary inference is made. Account identifiers, credits and reset identifiers are excluded from this delivery. No resets, credit purchases or paid generation were used.

Hardware/runtime: Apple M4 Pro MacBook Pro, 14 CPU cores, 24 GB memory, arm64; macOS 26.3 (25D125). Node.js 24.16.0, npm 11.13.0, system Python 3.14, FFmpeg 8.1.1. Chrome 152.0.7977.76. Playwright package for reproducible scripts: 1.58.2. The preinstalled Playwright CLI used for initial visible browser inspection carried Playwright 1.63.0-alpha-2026-08-31. No hardware serial numbers or host/account identifiers are included.

Main libraries: Three.js 0.180.0; React and React DOM 19.2.6; Vinext 1.0.0-beta.5; Vite 8.0.13; Base UI 1.7.0; Shadcn React 0.3.0; Lucide React 1.31.0; Tailwind 4.2.1. The full exact dependency graph is in `project/package-lock.json`.

## Inputs, instruction influences and delegation

- `inputs/dispatch-prompt.txt` preserves the full initial dispatch text. `inputs/01-v8-cutaway.md` preserves the exact brief bytes; final byte comparison passed against the original source file.
- The user’s current working agreement authorized safe local implementation, required concrete deliverables/validation and a Next prompt section, and limited external writes and cross-task actions. The explicit dispatch authorized within-task subagents, autonomous initial debugging, one initial candidate and a reserved consolidated correction.
- Sites building skill and its environment reference guided the pinned scaffold, Shadcn add-on, readable responsive layout, meaningful actual app, and production build. Registration and hosting were intentionally skipped under the explicit local-only instruction. A delegated task skips a user-facing Sites browser handoff; the browser was used for explicitly requested QA instead.
- Playwright skill guided real browser snapshots, screenshots and interactions. Reproducible Node/Playwright scripts additionally perform actual-app capture and coordinate assertions; no `@playwright/test` suite was introduced.
- HyperFrames entry point, product-launch route/workflow and CLI references were inspected for the required demo. The deliverable is a capture of this actual deterministic web app, so no separate promotional composition, generated media, storyboard approval gate, account connection, skill update or HyperFrames render was needed. The original app’s timeline supplies the demonstrated motion; FFmpeg only encodes the captured frames.
- One within-task subagent, `mechanics_references`, researched primary technical references and checked the proposed math, then performed a bounded read-only review of the implemented helper/scene/diagram. It wrote research notes in task-local work space. It did not edit the Site, invoke Sites tools, spawn agents or send any other Codex task a message. Model/effort of that inherited subagent are not independently observable.
- No separate Codex task was created, started, woken or messaged by this agent. No external deployment, site registration, publication, account change, outreach or physical hardware operation occurred.

## Human/controller interventions

The initial dispatch is the sole human/controller creative instruction for this candidate. There were no follow-up user preference decisions, concept checkpoints, review corrections or human edits during the build. The agent made routine design and implementation choices autonomously.

Tool execution required sandbox escalation for fetching open-source npm packages and for local loopback servers/browser automation. Those calls completed after automatic review. There was no unresolved auto-review rejection or additional user permission message. The initial scaffold fetch failed with DNS/network restriction; the authorized escalation allowed it to complete. Dependency installation was local and free; no external generation or paid service was called.

## Implementation and initial debugging

The engine uses 90° banks, four cross-plane crankpin phases, eight cylinders, the traditional 1–8–4–3–6–5–7–2 firing sequence, one half-speed cam and two overhead valves per cylinder. All moving parts and the selected-cylinder diagram are tied to one crank angle. Geometry, dimensions, material choices and timeline are procedural and editable. The opening section view, assembled view, exploded housing inspection and five-stage guided sequence share the same scene.

Material defects found and fixed before delivery:

1. The first rocker implementation moved valve stems sideways with rocker tips. Stems now stay on a fixed guide axis and have a sliding contact pad. Actual rendered-axis and pushrod-length checks pass.
2. The initial phone diagram shrank its text with the graphic; the phone view now uses its own cropped graphic and a normal-size text valve status. A clipped intermediate graphic was corrected before capture.
3. Assembled rocker covers left rocker tips exposed. Cover depth/height now contains the visible train. Exploded housings crowded the frame, so its field of view now expands with separation.
4. A captured assembled screenshot could precede the tab’s visual selection update. The capture helper now waits for the selected tab; that still screenshot was refreshed. The already verified movie was preserved after this screenshot-only change.

Non-product issues corrected during the same initial run: a relative scratch-directory/copy path mistake (corrected without overwriting inputs); initial npm DNS failure; local dev/prerender socket EPERM requiring approved loopback execution; a benign Cloudflare development metadata fetch timeout that used its built-in fallback; initial missing favicon request, resolved with the original local typographic icon; and a QA assertion that checked dialog removal before its exit animation finished. The dialog test was changed to wait for the hidden state and QA resumed from that point, retaining prior passing evidence. No extra process gate or separate review correction was consumed for these issues.

## Actual verification

- Production build passed. Final timed build: 4.964 seconds, exit 0. A large-client-chunk warning remains because the exhibit includes the 3D renderer; no compile/runtime blocker remained.
- Four numerical test groups pass. The actual helper was swept through 0–720° in 0.5° increments for every cylinder. Firing TDCs, fixed rod lengths, shared journal orbit, bank axes, valve windows, 360° piston repetition, 720° cycle repetition and tour endpoints were checked.
- Real Chrome desktop QA at 1440 × 1000 and phone QA at 390 × 844 / 360 × 844 passed: pause, play, ±15° stepping, Home/End/arrow scrubbing, speed changes, cylinder selection, all inspection views, orbit, zoom, reset, information dialog, tour start and manual exit. Phone views have no horizontal overflow.
- Actual Three.js world transforms were checked at twelve crank angles, including 37° and cycle boundaries. Maximum errors: rod length 8.88e-16; crankpin XY agreement 2.05e-15; piston/rod alignment 0; fixed valve-axis drift 4.45e-16; pushrod length 8.87e-10 normalized units.
- No application JavaScript exceptions occurred in the browser QA. The initial favicon 404 was resolved. Native WebMCP was unavailable, so its optional feature-detected registration is unverified.
- Final actual screenshots were visually inspected for desktop section, phone, assembled and exploded states. Representative movie frames, including the final return to the complete engine, were decoded/inspected. FFprobe verifies H.264, 1440 × 1000, 30 fps, 540 frames, 18.000 seconds, no audio track.
- GLB header, declared byte length and mesh/node structure passed. It contains 308 meshes and 337 nodes, with no animation. It is a static section pose, not the interactive exhibit or an engineering CAD certification.
- The delivered source modules match the verified working source. The included static build opened successfully from `project` without node_modules, at **http://127.0.0.1:4319/**. The temporary development and earlier work-preview servers were stopped; the final local preview is left running for review.

Detailed records are under `verification/`, with precise capture timing in `exports/capture-record.json`.

## Material limitations

This is a schematic kinematic teaching model, not a calibrated Chevrolet replica, thermodynamic simulation or structural/physical validation. Normalized dimensions, ideal valve timing, schematic tappet/lobe contact, static timing-chain envelope and omitted passages/accessories are documented in the app and `MECHANICS.md`. Color does not represent measured or simulated pressure/temperature. The GLB has no moving relationships.

Phone tests used responsive viewports in real Chrome, not physical phone hardware. Other browser/GPU combinations were not tested. WebGL 2 is required.

The starter’s npm audit reports 11 dependency advisories (8 high, 2 moderate, 1 low), primarily in development/server/image tooling; the local static file preview does not expose server functions or upload processing. This pilot was not expanded into a dependency migration or production-security review. No production deployment is authorized or provided.

## Next prompt

Optional

Ready-to-send prompt: “Review the initial Inside the Machine candidate in this package. If a material issue needs the reserved correction, identify one consolidated set of concrete changes while preserving the initial ZIP. Do not implement or publish anything during this review.”

Suggested model: gpt-5.6-terra. Suggested reasoning effort: medium.
