FPF Reference

A.2.2:4.2 Conceptual descriptors (not a data schema)

Preface node heading:a-2-2-4-2-conceptual-descriptors-not-a-data-schema:2115

Content

When you describe a capability in a model or a review, anchor it by answering these five didactic prompts:

  1. Holder: Whose ability is this? → a specific U.System.
  2. Context: In which bounded context were the measures established? → U.BoundedContext (strongly recommended for clarity and comparability).
  3. Task family: Ability to do what kind of work? → reference the relevant MethodDescription(s) or method family the system can execute.
  4. WorkScope: Under what conditions? → inputs/resources/environment assumptions (e.g., voltage, pressure, ambient, tool head).
  5. Performance measures: With what bounds? → CHR‑style measures (throughput, precision, latency, reliability, MTBF…) with ranges/targets.

Optional descriptors that improve trust without adding bureaucracy:

  • QualificationWindow: calibration/qualification window for the stated WorkScope (abilities drift).
  • Evidence: links to test reports, certifications, prior Work summaries (as Episteme).
  • Degradation/upgrade notes: known change points that affect the WorkScope.

Didactic guardrail: Capabilities are stated in positive, measurable terms (“can weld seam type W at ±0.2 mm up to 12/min at 18 °C–30 °C”). Avoid role words (“welder”) or recipe detail (step flows) here.