Workflow
Make deployment dependencies visible before the final build
Use a first-person app-building account to create a handoff ledger for configuration, identities and service boundaries.
THE SHORT ANSWER
A deployable application needs a verifiable configuration handoff as well as code that builds.
What the account illustrates
Karpathy’s MenuGen post links to a longer account describing the gap between a local prototype and a deployed application. The essay discusses configuration, API changes, environment variables and identity handling. These are the author’s historical observations, not current instructions for the named platforms. They provide concrete prompts for reviewing the work that sits outside a code diff.
Follow one user action
Choose a harmless example such as submitting a document for processing. Trace the action from browser to server, service call and stored result. For each boundary, name the environment, credential owner, expected identifier and failure response. Write down how a retry finds the existing job instead of starting another. Keep actual secrets in their proper store; the ledger should contain names and responsibilities only.
Prepare evidence for handoff
Ask a reviewer to follow the same action in the intended environment, including one interrupted or failed request. Link the observed result to the configuration revision and build artifact. A successful build answers only part of that review. This is an original deployment-planning workflow; no account was created, payment was processed or hosted application tested to produce this resource.
Put it to work.
- Trace one complete action.
- Name configuration owners.
- Use stable job identifiers.
- Check a failed request path.
Go to the source.
Original material, with its own scope and publication date. This note is an explanation, not a CooScope performance test.
Source published · Editorial review
Archived English post text; primary sources reviewed separately. Generated annotations, media and missing replies are outside the evidence scope.
- @karpathy — archived X post (2025-05-01)
- Andrej Karpathy — Vibe coding MenuGenLink / source review: 2026-10-15