From Small Idea to First Release in Six Passes
A decision sequence for defining the result, cutting the edge, shaping records, mapping state, handling failure and proving one useful path.
Programming project notebook / issue 00
Finish the small project.
Six field guides turn a loose software idea into a bounded, observable and maintainable first release. No product pitches. No mystery stack. Just the decisions that stop a small build becoming a permanent draft.
Six passes
A release has edges.
Small does not mean casual. Outcome, boundary, data, state, failure and verification form a chain: a fuzzy choice near the front usually reappears as a costly ambiguity near the end. The notebook keeps those choices visible, with worked examples rather than named technologies.
01Outcome
02Boundary
03Data
04State
05Failure
06Verification
Exactly six editorial notes
Start at the knot in your project.
Each note answers a different question. The framework joins them; the five narrower pieces supply a ledger, transition chart, annotated record, failure matrix and risk-based test budget.
Cut One Observable Slice From a Vague Idea
Turn “a request organiser” into one demonstrable path, then keep tempting extras in a first-release exclusion ledger.
Model the States Before Drawing the Interface
A generic booking-request example shows why nouns, allowed moves and rejected moves should precede screens and controls.
Plan the Record Before Writing Behaviour
Choose identifiers, ownership, invariants, absence rules and a migration boundary while changes are still cheap.
Give Each Failure a Different Answer
Separate expected rejection, unavailable dependencies, partial work and retryable trouble without exposing internal details to users.
Spend a Small Test Budget Where Risk Lives
Map acceptance examples, unit boundaries, integration checks and smoke checks to the failures that would hurt this release.
Publication boundary
Educational, pre-launch and deliberately generic.
ProgtiProj does not distribute source bundles, recommend products, run teaching programmes or promise employment outcomes. The examples are invented to explain decisions; they are not reports of client work or measured production results.
This six-pass method is unsuitable on its own for safety-critical, regulated, high-scale, real-time, medical, financial or security-critical systems. Those contexts need specialist review and controls beyond a compact editorial framework.
Read the publication scope, the illustrative role disclosures and the proposed checking policy before relying on any draft.