#A.2.9:5 — Archetypal Grounding (Tell–Show–Show)

Preface node heading:a-2-9-5-archetypal-grounding-tell-show-show:6920

#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

#A.2.9:5.1 — Tell (universal rule)

When governance or gating depends on “someone said/did X”, identify that saying/doing as actual Work SA : U.SpeechAct, its exact enacted U.Method, performer System, and obtaining assignment. Add a SpeechActRecord only to state relied-on claims about it, and keep any MethodDescription, optional channel, utterance text, and carriers separate. If the occurrence creates obligations, recommendations-as-duty, or prohibitions, cite explicit U.Commitment objects; if it creates strong permission, cite an exact GrantedPermissionRelation@Context. The act institutes neither effect without an exact current policy or procedure and the effect owner's independently satisfied conditions.

#A.2.9:5.2 — Show #1 (system archetype: change-control approval gates a deployment)

Situation (messy prose): “Change is approved, so the pipeline may deploy.”

Conformant modeling sketch. The first line names the actual communicative Work. The record then states claims about that occurrence; the assignment, Method, recognition classification, policy and grant must each obtain independently.

• Actual occurrence: SA-Approve-4711 : U.SpeechAct.
• Exact performer and assignment: admitted system CAB_Chair_A performs SA-Approve-4711 under obtaining CAB_Chair_A_ApproverAssignment_2026 : U.RoleAssignment. That assignment independently exposes role value ApproverRole, role-taxonomy episteme ChangeControlRoles_v3, effective scheme ChangeControlReferenceScheme_2026, and an extent covering the act. The assignment grounds attribution; it does not act.
• Actual method relation: enactsMethod(SA-Approve-4711, ChangeApprovalMethod_v3) independently obtains, with ChangeApprovalMethod_v3 : U.Method.
• SA-Approve-4711-Record : SpeechActRecord states:
  • speechActOccurrenceRef = SpeechActRef(SA-Approve-4711);
  • performedBy = U.EntityRef(CAB_Chair_A);
  • performedUnderAssignment = RoleAssignmentRef(CAB_Chair_A_ApproverAssignment_2026);
  • enactsMethodRef = U.EntityRef(ChangeApprovalMethod_v3);
  • methodDescriptionRef = EpistemeRef(ChangeApprovalProcedure_v3), a separate C.2.1 episteme used here to identify and constrain the Method;
  • recognitionTaxonomyRef = EpistemeRef(ChangeControlSpeechActTaxonomy_v3);
  • effectiveReferenceScheme = ChangeControlReferenceScheme_2026;
  • policyOrProcedureRef = EpistemeRef(ChangeControlApprovalPolicy_v3), current for this approval and grant use;
  • channelRef = U.EntityRef(CAB_TicketChannel);
  • actTypes = {SpeechActTypeRef(Approval)} under that taxonomy and scheme;
  • reliancePosture = relianceReady, executedWithin = ChangeControlBoardSystem, and window = [2026-06-12T10:03Z, 2026-06-12T10:04Z];
  • utteranceSubjectRefs = {ChangeRequestId(4711)};
  • institutionalTargetRefs = {GrantedPermissionRelationRef@Context(PER-Deploy-4711)};
  • utteranceRefs = {EpistemeRef(ChangeTicket#4711)} and carrierRefs = {CarrierRef(TicketSystemRecord#4711)};
  • institutes.permissions = {GrantedPermissionRelationRef@Context(PER-Deploy-4711)}.

PER-Deploy-4711 : GrantedPermissionRelation@Context obtains separately under A.2.8.PER:

• beneficiaryRef = RoleAssignmentRef(OpsBot#DeployerRole:CD_Pipeline_v7);
• permittedActionSpecificationRef = EpistemeRef(DeployChange4711WorkSpecification);
• institutingSpeechActRef = SA-Approve-4711;
• grantorAssignmentRef = RoleAssignmentRef(CAB_Chair_A_ApproverAssignment_2026);
• grantValidityPolicyRef = EpistemeRef(ChangeControlGrantPolicy_v3) under ChangeControlReferenceScheme_2026; the separately cited ChangeControlApprovalPolicy_v3 supplies the act-to-grant instituting rule;
• scope, revocation stance, and validity interval [2026-06-12T10:04Z, 2026-06-19T10:04Z] are explicit.

The one-minute speech-act interval and seven-day grant interval are different facts even though the latter begins when the former ends.

The utterance is about ChangeRequestId(4711); its policy-selected target and demonstrated effect are the separately obtaining grant. Nothing here claims that the change-request entity itself changed. Gate predicate A-Gate-Deploy-4711 may check exists SpeechAct(type=Approval, utteranceSubjectRefs includes ChangeRequestId(4711), performedBy=CAB_Chair_A, performedUnderAssignment role=ApproverRole, within 90d), consume the current grant, and apply other prerequisites; passing the gate neither institutes nor equals the grant. No F.9 Bridge is needed merely because a pipeline consumes the result: this case uses one exact taxonomy, scheme and policy. A Bridge becomes current only if another receiving use actually translates or compares a different local meaning.

Near misses. A ticket row alone is a carrier-backed claim, not the act. ChangeApprovalProcedure_v3 is a MethodDescription, not what the act enacts. A current approver assignment does not prove that approval Work occurred. Without the exact current policies, the occurrence remains communicative Work but establishes no grant.

This case retains kind versus occurrence versus record, utterance versus carrier, explicit performer and grant beneficiary, exact act and grant intervals, current policy bases, provenance from grant to instituting act, and strong permission versus admissibility gate as independently judgeable distinctions.

#A.2.9:5.3 — Show #2 (episteme archetype: publishing a spec edition without making the spec an agent)

Situation (anti-pattern): “The interface spec declares MUST/SHALL requirements.”

Conformant modeling sketch. SA-Publish-API-v12 : U.SpeechAct is the actual occurrence. Admitted system StandardsEditor_A performs it under obtaining StandardsEditor_A_PublisherAssignment_v12; that assignment independently identifies PublisherRole, role-taxonomy episteme StandardsRoles_v12, effective scheme APISpecReferenceScheme_v12, and an extent covering the act. enactsMethod(SA-Publish-API-v12, SpecPublicationMethod_v12) independently obtains; SpecReleaseProcedure_v12 is only a separate description of that exact Method.

SA-Publish-API-v12-Record : SpeechActRecord states:

• speechActOccurrenceRef = SpeechActRef(SA-Publish-API-v12);
• performedBy = U.EntityRef(StandardsEditor_A) and performedUnderAssignment = RoleAssignmentRef(StandardsEditor_A_PublisherAssignment_v12);
• enactsMethodRef = U.EntityRef(SpecPublicationMethod_v12) and methodDescriptionRef = EpistemeRef(SpecReleaseProcedure_v12);
• recognitionTaxonomyRef = EpistemeRef(APISpecSpeechActTaxonomy_v12) and effectiveReferenceScheme = APISpecReferenceScheme_v12;
• policyOrProcedureRef = EpistemeRef(APISpecPublicationPolicy_v12) and optional channelRef = U.EntityRef(StandardsReleaseChannel);
• actTypes = {SpeechActTypeRef(Publish), SpeechActTypeRef(DeclareNorms)} under that taxonomy and scheme;
• reliancePosture = relianceReady, executedWithin = SpecPublicationSystem, and window = [2026-06-14T09:00Z, 2026-06-14T09:06Z];
• utteranceSubjectRefs = {EpistemeRef(APISpec_v12)}, institutionalTargetRefs = {EpistemeRef(APISpec_v12)}, utteranceRefs = {EpistemeRef(APISpec_v12)}, and carrierRefs = {CarrierRef(GitTag:v12), CarrierRef(SignedReleaseArtifact:v12)};
• institutes.publicationRelations = {EpistemePublicationRelationRef(APISpec-v12-Publication)}.

APISpec-v12-Publication : EpistemePublicationRelation separately names the selected APISpec_v12 edition, audience declaration, bounded-use declaration, publication form, exact carrier, availability interval and governing publication conditions under E.24.PUB. It obtains only while that exact edition remains available under those conditions. Its interval need not equal the six-minute publishing act. The same episteme can be both utterance subject and publication object without those relations becoming identical.

The act does not change the spec's claim content or make the episteme an actor. If D-StdStatus-APISpec_v12-Published is needed, keep it as a separate C.2.1 claim about the exact publication relation and cite its evidence through A.10; do not put the claim in institutes. Norms live in the published utterance description, while StandardsEditor_A performs the publishing Work. Another audience or scheme needs F.9 only when a receiving use actually translates or substitutes the local act or policy meaning.

Bounded non-use. If the only question is what APISpec_v12 says, stop at A.7/C.2/E.17. If the question is whether it is available to an audience, use E.24.PUB. If the question is evidentiary support for a status claim, use A.10. Keep A.2.9 only when the actual communicative Work occurrence itself matters.

---

Last Updated: 2026-08-01 — upstream FPF commit 9a9a42e4 (github.com/ailev/FPF)