Field note 001

A four-step evidence loop for builders.

The fastest way to become wrong is to make a confident change to a system you have not actually observed. This loop keeps practice anchored to reality.

Observe the real system

Open the live page. Read the actual function. Pull the current record from the authoritative source. A plan, memory, or plausible explanation is a lead—not evidence.

Make one claim testable

Name what you believe, what would support it, and what would disprove it. Replace “this should work” with a concrete request, result, threshold, or before-and-after comparison.

Change the smallest useful thing

Choose a change large enough to create value and small enough to isolate what happened. Preserve working behavior and avoid widening the blast radius without evidence.

Preserve the evidence

Record the verified result, the limitation, and what should happen next. Route the lesson to the one place future work will actually find it.

The loop is recursive: each preserved result changes what you can observe and test next. Completion is not the end of learning; it is the beginning of a better next pass.