FPF Reference

    Show 2 — Episteme archetype (physical/human service)

    Preface node heading:show-2-episteme-archetype-physical-human-service:16464

    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

    Draft (ambiguous): “The auto service accepts walk‑ins and promises repair in 2 days.”

    Unpacked (facet‑explicit):

    • “The service access point is the Auto Repair Shop front desk (an addressable facility).”
    • “The service access spec is the intake procedure (how to request/submit a car).”
    • “The promise content promises ‘repair completed within 2 business days’ given stated preconditions.”
    • “The service delivery method is the shop workflow (inspection → parts ordering → repair → QA → handover).”
    • “The service provider principal is the shop entity that can hold a commitment (not the front desk as an access point).”
    • “If advertised as binding, introduce a service commitment held by the shop’s provider role.”
    • “Each repair job is service delivery work with evidence (work order, timestamps, acceptance record).”

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)