FPF Reference

    Show 1 — System archetype (microservices + SRE)

    Preface node heading:show-1-system-archetype-microservices-sre:16446

    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): “Payments service is down; the service guarantees 99.9% uptime; we will restart the service.”

    Unpacked (facet‑explicit):

    • “The Payments service access point (the Payments API ingress/endpoint host) is down.”
    • “The Payments service delivery system (the Payments backend realizer) is degraded (symptom attribution is explicit).”
    • “The Payments service access spec (e.g., OpenAPI/endpoint interface description) defines the request/response interface.”
    • “The Payments promise content states target availability SLO=99.9% over Γ_time=30d (promise content).”
    • “The service commitment held by the service provider principal binds them to that clause.”
    • “The service delivery work Incident#2025‑… records outage evidence and the restart action; the runbook used is the service delivery method.”

    Optional serviceSituation bundle (sketch):

    • serviceSituation( promiseContentRef=PaymentsAvailabilityClause, providerRoleRef=PaymentsPlatform#ServiceProviderRole, providerPrincipalRef=PaymentsPlatformTeam, accessSpecRef=PaymentsAPIv2, accessPointRef=PaymentsAPIIngressProd, deliverySystemRef=PaymentsBackendProd, deliveryMethodRef=PaymentsIncidentRunbook@ed=…, commitmentRef=AvailabilityCommitment@ed=…, deliveryWorkRef=Incident#…, Γ_time=Rolling30d, witnesses={SLOReport#…, IncidentLog#…} )

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