A.6.C:5.3 — Show (Episteme archetypes)
Preface node
heading:a-6-c-5-3-show-episteme-archetypes:16318
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
(C) Multiparty protocol boundary (behavioural and session-type motif)
Draft wording: “The protocol guarantees progress. Participants must follow the sequence.”
Source clauses and additional illustrative premises:
The progress guarantee needs its semantic or operational meaning. For the illustrative case below, assume the published protocol description and the trace-admissibility criteria; the named trace evaluation is an additional hypothetical case.
-
Description/publication: protocol description (could be a type spec or protocol spec plus explanatory views).
-
L — when the guarantee is semantic: the progress property is a law over the protocol model (truth-conditional, within the theory).
-
A — additional entry-condition premise: suppose a session-entry mechanism uses the declared trace criteria to determine whether an interaction may enter the session. Its entry predicate is A; the trace-validity definition remains L and an actual conformance verdict is E.
-
D: the protocol description generically requires covered participants to follow the stated sequence. It asserts no individual commitment occurrence.
-
E — additional hypothetical trace evaluation, not inferred from the progress guarantee: suppose admitted system
ProtocolConformanceEvaluator-AperformedProtocolConformanceRun-T1 : U.Workover bounded interactionTrace-42.A.6.1 application
ProtocolConformanceApplication-T1has result bindingconformanceResult -> ProtocolConformanceResult-T1; that C.2.1 result episteme statesconformanceVerdict=passandobservedTerminalState=completedunderProtocolConformanceCriterion-v5.For a disputed interaction, an A.10 path links this result to
MessageTrace-42,ConformanceRunRecord-T1, andProtocolAuditRecord-42carriers.
(D) Socio-technical “SLA + audit trail” boundary
Draft wording: “Provider shall respond within 4 hours for Severity‑1 incidents. Only Severity‑1 is covered. Evidence is provided by ticket logs.”
Unpack + classify:
-
Promise content (service promise clause, when present): a responsiveness promise for a defined incident class and window is separate from the SLA's generic prescription.
-
Description/publication: SLA publication (and its views for different audiences).
-
Scope from the source: the promise covers only Severity-1 incidents. This coverage restriction becomes an A claim only when a separately defined admission rule uses it as an entry or continuation condition for a named action or application.
-
D: the SLA clause generically requires the covered Provider to respond within 4 hours for Severity-1 incidents; only Severity-1 is covered. Claim that actual provider
ProviderSystem-Abears the four-hour duty only after the SLA's individualizing rule and required actual basis establish one A.2.8 commitment; otherwise keep the clause generic. -
Evidence source clause: the draft names ticket logs as evidence; it supplies no measured response interval.
-
E — additional hypothetical response evaluation: suppose admitted system
SLAEvaluator-AperformedResponseEvaluation-Ticket-17 : U.Workover Severity-1 ticketTicket-17under the declared clock and measurement method.A.6.1 application
ResponseMeasurementApplication-Ticket-17has result bindingresponseIntervalResult -> ResponseIntervalResult-Ticket-17; that C.2.1 result episteme statesobservedResponseInterval=3h42mandwithinFourHourTarget=true.When the SLA decision relies on this result, an A.10 path links it to ticket, response-timestamp, clock-source, and severity-classification carriers. The four-hour requirement is from the source;
3h42mis the additional hypothetical observation.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)