WORKING-DOCUMENTS — Make a document support its intended uses

Preface node heading:working-documents-make-a-document-support-its-intended-uses:807

What this page is

This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

Methodology

Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

Content

  • Situation: A document is requested, but its label does not reveal the use it must support.
  • Question: Do you need to check one view, reuse related views, show the same subject differently, see enough structure, compare named sources, or use an architecture description in a decision?
  • First useful result or blocker: A checked view, a reusable viewing approach, another presentation of the subject, an account of sufficient or missing structure, a source comparison, the architecture-description result needed now, or the specific obstacle to obtaining it.
  • Mantra: Start from each recipient’s work. Choose the claims, relations and form it needs. One account can serve several users. Compare the relevant features on a common basis. For joint operation, check that the conditions can hold together. For rival accounts, trace what follows under each. Distinguish the document, its subject, decisions and performed Work.
  • Start with: E.17.0 to choose a viewpoint for the reader's work or check view conformance. Use E.17.1/E.17.2 for reusable bundles, A.6.3.RT for representation changes, C.33 for structure, E.17.ID.CR for comparing sources and C.30.AD for architecture descriptions.
  • Stop or return: Stop when the requested uses have the accounts or decisions they require. Return when a use or the content changes.

Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)