Category

F02 Product — Formal Operator R&D Arc

Definition
Working Definition:
The capture instrument that converts [The Read] from instinct into durable evidence. A fast, named, habitual logging discipline run after any production where the operator’s read surfaced something worth naming. Three fields: Problem (what was observed, what it names), Evidence (stage-side and numbers-side indicators), Solution (what the evidence calls for, what test it generates). The act of completing the three-part arc forces the operator to adjudicate — a half-formed read cannot be logged. The log is not a record-keeping tool. It is a thinking tool. The discipline is in the completion, not the filing. Lives in [The Workbook].
Open Questions:
Physical form: mental discipline with named categories or an actual fillable instrument in [The Workbook]? Current position: actual instrument, minimal friction, three fields, three minutes post-production.
Cadence: after every production or after productions where the read surfaced something notable? Current position: operator-determined, minimum after any production where a notable read occurred.
Relationship to [R&D Brief] — a completed [Read Log] entry IS an [R&D Brief]; the two terms need clean boundary definition so they don’t collapse into each other
Workshop Trail:
Surfaced during Gartner whitepaper shape read session, 07.08.2026
User confirmed: “logging of any sort forces the operator to solidify his thinking and his evidence. its the piece that forces the operator to adjudicate the problem/evidence/solution arc”
Problem/evidence/solution arc confirmed as the three-field structure
Position in the formal process: handoff instrument between [The Read] (discovery) and [Bias Prosecution] (prosecution). The log is where gathering ends and prosecution begins.
Compounding mechanism confirmed: informal process burns intelligence every shift; formal log banks it; compounding is slow then accelerates

Explanation
See Definition.