The appeal
Prompt-driven programming can broaden experimentation and compress the distance between an idea and a running prototype. These are capabilities to document rather than assume to be universal benefits.
Vibe Coding.
An accessible interface still requires responsibility for correctness, privacy, security and maintainability.
EVIDENCE FRAMEWORKREVISION-READYOPEN QUESTIONS
WHAT THIS FIELD EXAMINES
Programming through prompts, generated code and iterative feedback. Our purpose is to establish the evidence and questions needed for rigorous coverage, not to imply that a proposed future is inevitable.
Where the risks shift
A working demo can hide dependency fragility, secrets exposure, untested paths and fragile behavior. A rigorous assessment records whether users can explain, reproduce and safely extend what they build.
Operational boundary
Our experiments separate a throwaway prototype from production software. The second demands tests, source control, review and a defined owner.
How we would test the claim.
Record task definition, starting skills, generated diffs, test coverage and post-generation fixes.
Documents to consult
These are starting references for future reporting, not proof that every open question above is resolved.
Revision record
Edition 1.0 · 9 October 2026. Initial scope and source register created. This brief is a research framework, not a completed investigation; material future corrections should be described rather than silently overwritten.
How corrections are documented ↗