CAPABILITY
What actually changed?
Start with the primary source. Name the new capability, the access conditions, and the part that remains unclear. A headline is not evidence.
AI moves fast. The notes should still hold up.
Field Notes will be my sourced, dated record of the AI changes that affect real work. Each note will separate what was announced, what I could verify, what I observed, and what an operator should do next.
What earns a place here.
A release, model, workflow, or argument belongs in Field Notes only when it changes a real decision. The page will not chase every announcement. It will document the few changes worth understanding well enough to act on.
WORKFLOW
Where does it enter the work?
Place the tool inside an actual handoff, decision, or operating path. Record the inputs it needs, the person who remains responsible, and the fallback when it fails.
CONSEQUENCE
What becomes easier or riskier?
Translate the change into time, quality, control, cost, or customer impact. If the consequence cannot be stated plainly, the note is not ready.
The publication standard.
Every note will show enough of its working material for a reader to tell the difference between evidence, interpretation, and a next-step recommendation.
- Source and dateWhere the underlying claim came from and when it was checked.
- Verification stateWhat was tested directly, what was observed, and what remains a source claim.
- Operating contextThe business task, person, constraint, or handoff the change affects.
- Practical next moveWhat to test, ignore, protect, or revisit, and why.