Before access
- Finish line and exclusions agreed
- Inputs and data classes named
- Approval and stop conditions written
- Test environment chosen
The artifact is the meeting
Gate. Build. Verify. Hand off.
The process is written so the buyer can see when scope is fixed, when access expands, how failure is tested, and what survives after delivery.
Async by default. One named buyer. One written review round unless the scope says otherwise.
Five steps
- 01
Name the finish line
You should know the finish line before I touch the work. We name the file, screen, decision, or working path that must exist at handoff.
- 02
Inspect the field conditions
I inspect the actual sources and permissions before asking for more access. That is where constraints and failure cases usually surface.
- 03
Build the smallest deep solution
I build the smallest version that answers the question or makes the path work. Protocols and polish wait until they earn their place.
- 04
Try to break it
Then I try the obvious breakpoints: bad input, a rejection, an interruption, and a repeat request. The agreed checks decide whether it is ready.
- 05
Hand over the artifact and the manual
You get the artifact, its source, the checks I ran, the limits I found, and a manual someone else can follow.
Access expands with proof
Read first. Write later.
Public sources and sandbox fixtures come first. Sensitive production access waits for a written boundary, payment, least privilege, and a named owner.
Before release
- Happy path and known failure paths run
- Secrets absent from source and logs
- Duplicate-write behavior checked
- Handoff and rollback understood
Scope changes
No invisible expansion.
A new system, screen, decision, access class, or review round becomes a written fixed-price change. Work pauses when required buyer inputs are late.