Build Inside the Machine from /Users/curtispyke/Documents/Codex/2026-09-06/peop/outputs/astra-build-files/prompts/01-v8-cutaway.md.

Curtis explicitly authorized this separate local Codex task using gpt-6-astra with Ultra, including within-task subagents, and existing account allowance for one initial run and one targeted correction per project. This is one of three independent pilots, not a model comparison. Build the directed production brief in the specified file; do not run the short comparison variant or the larger matrix.

Use your new task's local workspace for the implementation. Read the brief and copy its exact original text into your output records before work. Fulfill the directed production brief's actual deliverables, including runnable editable projects, actual screenshots/captures/renders, and usable opening/render instructions. Implement, inspect, and validate the result. One initial implementation with autonomous internal debugging/verification is authorized. Preserve the first delivered candidate before any separate targeted correction. Do not spend the separate correction pass on preferences; I will review your first result from the parent task and may send one consolidated correction. If you fix a material defect in a distinct correction pass already, record exactly what it was.

Use installed, available dependencies and procedural/original local assets. No paid external generation, purchases, credit purchases, usage resets, publishing (including private deployment/registration), account changes, outreach, or unrelated project changes. Do not create, start, wake, or message any other Codex tasks. Within-task subagents are authorized; keep their work scoped and record their use. Follow applicable skills, but the current explicit local-only/no-publication instruction overrides deployment defaults. Do not stop for routine creative choices. Do not invent additional concept approval checkpoints. Websites require real desktop/phone and interaction QA as stated in the brief.

Produce your final user-facing deliverables inside your own outputs directory, with an individual downloadable ZIP excluding node_modules, caches, credentials, and irrelevant personal data. Include the editable project/source, actual exports, README and remix example, input and asset attribution, and RUN.md. RUN.md must record UTC start/end times, elapsed build and render time separately where measurable, actual model/effort/speed when observable (unknown if not observable; never assume from a prompt), runtime/hardware/dependency versions, applicable skill/instruction influences, provided inputs, subagents, actual tests, limitations/failures, and all human/controller interventions. Shared account usage is confounded by other tasks: record snapshots if available but do not claim per-task percentage consumption or invented dollar costs. Do not expose account identifiers or reset-credit IDs in deliverables.

Save the full initial dispatch prompt and exact brief as inputs; label this as an original pilot inspired by public examples, not a reconstruction of a creator's private prompt. Do not imply that a visual render proves accurate physics. End by listing absolute paths to the editable project, ZIP, exports, RUN.md, and any live localhost preview, along with remaining material limitations. Include the required Next prompt section.
