fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 60270–60284

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 18:00:10 UTC

C.22.2:21 - Machine-Assisted Drafting Boundary

Machine-assisted ProblemCard drafting is only a drafting aid. Before the draft is used for P2W or selector-facing work, a practitioner checks the card’s local fields and any subject-pattern cues for claims outside C.22.2.

Required practitioner checks for a machine-assisted draft reuse the exact Thin contract:

  • problem signal;
  • one joint EntityOfConcern, effective ReferenceScheme, and ClaimScope;
  • exact claim family;
  • reason this is not merely a wish, ticket, slogan, label, or preselected Work request;
  • improvement check or acceptance probe; and
  • one honest next use.

Check problem-formulation follow-up reason, validation boundary, freshness or expiry, unknown handling, source-set reference, representation or retargeting relation, and outside-pattern cues only when that content is current for the chosen next use. Omit a non-current field; do not invent a value or write unknown merely because the drafting aid exposes that field.