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:30:10 UTC

E.8:4.2.3 - Intended-reader discipline for pattern prose

The intended user is the agent that uses the pattern. Write for the work it supports, such as organising thought, investigating a question, changing a system, publishing a description or reviewing a result. One agent may apply the pattern while another performs the work it describes.

Check which system the claim concerns. Try the operation with a different performer. What capabilities, access or authority does it require? Use the action or role in the general instruction. A person, a technical system or a division can work as an engineer. Then hold the work result fixed and vary the system to which a decision or a capability is attributed. If the attribution changes what the evidence establishes, name that system and the conditions that matter.

A robot can measure a part against a tolerance. If the contract assigns acceptance to the customer’s inspection unit, that unit decides whether to accept it. The same accepted part could follow from a judgement supplied by a vendor or from the unit’s own interpretation. To find out whether a human trainee can interpret the readings, observe the trainee on a new part with the aids permitted in later work.

The pattern’s sections explain the described subject, the user’s action and result, costs, and grounded boundaries that change use. Public architectural explanation belongs here when it helps the reader understand, select, combine, or adapt the Methods.

For example, explain why a profile specializes one step but reuses another, how a combination makes its next result possible, or when an alternative would be better. State the relations that apply in Solution and explain their reasons in Architectural Rationale. A whole language and its profiles use the same content functions through E.11.PFP:4.7.

E.8 reader and reviewer wording is framework-authoring wording. Project-side publication readers, explanation readers, comparative review units, and participants in named project-side review relations are governed by the patterns that name those units and relations, such as E.17, E.17.ID.CR, E.17.EFP, A.10, A.15.4, A.20, or A.21.

Keep the development history of the current pattern version in its DRR, companion, review, or release material. This includes current arguments for promoting a draft, authority-reference or naming freezes, merge and landing state, and review correspondence.

When a development decision contains a durable reason that changes practitioner use, publish that reason with the necessary explanation and source return; retain the dated decision and its evidence in the development record. Users need enough reasoning to understand the choice without reconstructing that record.