Category

F02 Product — Formal Operator R&D Arc

Definition
Working Definition:
A completed [Read Log] entry that has cleared the [Bias Prosecution] step and generated a testable proposition with declared evaluation criteria. The point at which a logged read becomes a formal test initiation. The R&D Brief names the hypothesis, declares both evaluation instruments upfront (lagging metric and GX indicator), and defines the test window before the test runs. The operator has formally initiated a test. The brief is the document that makes the initiation real — without it the test runs informally against an undeclared standard and the informal diagnostic reclaims the evaluation.
Open Questions:
Is [R&D Brief] a standalone term or a phase label within [Operator R&D]? Current position: standalone — it names the document that bridges prosecution and test, which is a specific enough function to earn its own bracket.
Does the brief require a named format in [The Workbook] or is the term sufficient without a physical instrument?
Relationship to [Read Log] — the brief is the output of a completed log entry that cleared prosecution; the log is the input; they are sequential not synonymous
Workshop Trail:
Surfaced during Gartner whitepaper shape read session, 07.08.2026
Emerged from the observation that a completed problem/evidence/solution arc IS a test initiation document — the operator has formally started a test without calling it that
User confirmed the ten-step process — Step 6 (Test) requires declared criteria and a defined window upfront; the brief is what carries those declarations
Key function: prevents the informal diagnostic from reclaiming the evaluation after prosecution has cleared the bias. The declared criteria in the brief are the protection.

Explanation
See Definition.