Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:20:20 UTC

F.16:5 - The one-page Worked-Example Canvas

Each item is a thought the reader needs, not a mandatory form field.

  1. Title, working situation, and gain. Name the situation in ordinary language and say what practical error or decision the example resolves.

  2. Worked claim. State one bounded claim. Example: “June availability is evaluated from observations of the defined service-delivery Work, not from the approved runbook.”

  3. Actual subjects. Name the values and entities the claim concerns, distinguishing its subject, relation participants and result.

  4. Direct pattern route. Beside each substantive claim, cite the pattern that defines, constrains, or tests the value or relation used by the claim. This prevents one vague word or generic Bridge from taking over several relation families.

  5. Exact source basis. Cite the source and edition and, where local wording matters, the expression, claim, and effective scheme. Add an F.17 cell only if the exact local meaning needs a stable address for this use.

  6. Obtaining relations. For each relation, name its exact participants, direction, basis, and loss. Use F.9 when the example tests a proposed relation between local meanings with different interpretation bases. Assert a Bridge only if its predicate holds.

    Use the defining or testing pattern for MethodDescription membership, enactment, performed Work, measurement, evidence, fulfilment, kind, assignment, publication, transformation, and any load-bearing indicator relation. Use C.16.P to recover the proposed indicator relation. If no rule defines or tests it, return A.6.RCD missing-governor. When a rule exists, state what the case evidence supports under it.

  7. Evidence, result, and limits. Show the independently established direct relations by which observations or sources support the claim. A.10 describes that path and classifies reliance on it for the bounded use; the cited basis must meet the evidence requirement of the claim and its direct rule.

    When evaluation is part of the case, show the selected inputs, evaluation rule, result and any declared result scale. Recover the evaluation Work, enacted Method and exact application and result binding when the case claims them or its governing rule requires them, including the performance-history branch of A.2.3/F.12 promise evaluation.

    Add F.10 status and a durable C.2.1 verdict assertion only for their selected uses. Use B.3 only for an actual named assurance claim. State the consequential limits of the conclusion.

  8. Optional comparison surface. If two or more local meanings or source claims are hard to compare in prose, add one compact F.7 table. State the receiving-use conclusion separately. Omit the table when it adds ceremony but no clarity.

  9. Micro-narrative and checks. Walk briefly from the working situation through the actual relations to the result. End with the direct subject checks that let the reader replay the claim, and add a non-use boundary only when F.19’s grounded-contribution test requires it. Add F.15 only when a finite naming slice needs its static or regression checks.

Memory rule. If the case cannot fit on one page or slide, reduce it to one claim or split it into linked examples. When shortening the case, keep the evidence or relation that makes its claim intelligible.