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

E.8:4.2.4 - Human-facing fit beyond intended-reader correctness

Human-facing fit is also subject-domain fit. A recognition text that starts from internal taxonomy, pattern-placement convenience, or package-architecture wording before the problem-domain moment is still under-authored even if its later guidance or check text is correct.

When a broader umbrella name and a narrower operative branch are both used, the recognition text should also tell the reader how the branch fits under the umbrella, what it governs and which action and predicate apply, as described in §4.2.1 rather than leaving that reconstruction to a later declaration block or companion note.

P-2 epistemic precision check. When the E.10 criteria call for epistemic precision restoration in pattern prose, the first admissible action-guiding move must survive as remaining admissible reader use or be replaced by a neighboring FPF rule whose content now defines or constrains that claim application. E.2 P-2 and E.12 require this.

Intentional didactic metaphors and vivid Plain recognition lines are admissible when they are ordinary recognition aids or when their claim kind or admissible-use boundary maps back to Tech under E.10:6.2. A precision-corrected rewrite that leaves the recognition text inert is still under-authored.

For method guidance, explain in Solution what the performer should attend to or compare when it can change the next move: conditions needed for the operation, consequences expected from it, and whether the obtained result serves the receiving work. Give a reachable continuation when a condition is unmet, unknown or the result leaves the original concern unanswered.

B.5.PI develops an opening into inquiry; B.5.EA helps when the concern cannot yet be expressed, and an early cue can remain unresolved. Put these connections where they change use, including in first authoring.

Do not add a compulsory monitor, extra form or copied “watch for anomalies” paragraph to every pattern. A known adequate result can still end the work directly.

Use the recognition and assurance functions in §4.2.1. Put the working situation and first useful result in Problem frame and Solution; add candidate-pattern comparison cues when a question about finding the right pattern remains under E.11.

Entry-cue authoring rule. Begin with one ordinary question about the user’s object and claim, before any PatternID, card, template label, or internal taxonomy. In the same compact cue, state what cited content contributes, cite the pattern id, and name the smallest result usable now plus its stop or return condition.

Add a tempting overread only when the F.19 plausible-reader test finds independent local ground and an action-changing effect. Name an exact episteme, ClaimGraph, or edition only when a later use depends on that identity. The cue guides reading; it does not by itself constitute a result or relation.

Compact candidate-pattern comparison belongs in E.11-distributed entry material. Longer first-entry comparisons belong with E.11’s bounded-comparison explanation; E.11:5.7–5.14 supplies worked examples.

Keep a claimed breadth visible at first reading and preserve the same claim as the assurance text develops it, under §4.2.1.

Illustrative migration example (informative).

Old pre-template top:

Start here when the dominant question is API, protocol, SLA, published boundary, or compliance wording.
First output: Claim Register.
Neighboring pattern relations and entry-recognition reclassifications: A.6.B, A.6.C.

Repaired Problem-frame recognition signature:

Use this pattern when boundary-facing language - API, protocol, SLO/SLA, compliance clause, or other published boundary description - mixes guidance or check clauses, admissibility gates, duties, and evidence into one sentence or published boundary description.

If missed, runtime behavior, governance, and evidence are treated as one undifferentiated promise.

Do not use this pattern merely because the text mentions an API or boundary description. For an unstable cue, keep the passage or observation that prompted the concern. Use B.5.EA when the participant cannot yet express the distinction needed to continue; use A.16.1 when preserving the cue itself is the first useful publication.

First admissible action-guiding result: one `A.6.B`-governed atomic claim set or one Claim Register whose claim/use questions are explicit enough for a reader to inspect using the pattern content that defines or constrains the claim, or a named project-side FPF kind and reference.