A.2.9:4.2 — Minimal occurrence-description record (normative)
Preface node
heading:a-2-9-4-2-minimal-occurrence-description-record-normative:7445
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
Use the following declaration schema only when a receiving use needs a persistent claim about one already admitted actual speech-act occurrence. The record fields state claims about the referenced occurrence. A source that has only a candidate observation uses the separate non-conformant episteme/stub described under SpeechActRef discipline; it supplies neither a SpeechActRef nor a SpeechActRecord.
Occurrence-side constraints:
- (SA‑C0) Actual Work conformance. The individual referenced by
speechActOccurrenceRefMUST first satisfy independent A.15.1 admission: every actual performer has the A.13 core for the communicative action, scope, working situation, and window; the performance history is grounded; and the Work has an actualenactsMethod -> U.Methodrelation, temporal extent, and at least one obtaining locally declared Work-to-System containment relation. Add a characteristic profile only when a Grade, autonomy or profile result, criterion-dependent characteristic, or assurance use consumes it. A record that makes no exact assignment-bound attribution MAY omitperformedUnderAssignmentRef. Whenever that field is present or the record claims exact assignment-bound attribution, it MUST resolve to a separate F.6 relation established after admission for this already admitted act through the same obtaining A.13 assignment.methodDescriptionRef, when present, cites a separate C.2.1 episteme; the description is not enacted. - (SA‑C1) The System performs; exact attribution reuses the same assignment. The performer MUST be an admitted
U.Systemthat satisfies and is classified under one exact local agential system-role kind for this act. An observation-only or otherwise non-attribution record MAY omitperformedUnderAssignmentRefand MUST NOT be used to satisfy a guard, gate, or claim that depends on exact assignment-bound attribution. If the field is present, it MUST resolve to the separately obtaining F.6performedUnderAssignmentrelation for the already admitted act and the same obtaining assignment occurrence named by A.13, together with its declaredU.SystemRoleAssignmentspecies. If a guard, gate, or claim relies on exact assignment-bound attribution, the field MUST be present and that F.6 relation MUST obtain. The assignment MUST have the performer as holder, supply every other participant, cover the act, and satisfy its species predicate for the required scope, working situation, and window. Evidence supports those core facts; a characteristic profile enters only when conditionally consumed. Taxonomy and reference-scheme epistemes may interpret an assertion but are not assignment participants. Establish any authority required by the receiving use under its applicable rule. - (SA‑C2) Act types are independently satisfied recognition classifications. The occurrence MUST instantiate at least one
SpeechActTypeRefdefined by the exactrecognitionTaxonomyRefunder the statedeffectiveReferenceScheme. If a policy or procedure supplies an additional recognition condition, cite its exact current episteme and satisfy that condition separately. - (SA‑C3) Time honesty and interval separation. The occurrence MUST have an actual temporal extent so freshness can be evaluated; the record's
windowis a claim about that act extent. Every instituted commitment, grant, publication relation, status relation, or other effect keeps its own independently governed occurrence or validity interval. Coincident boundaries do not merge act and effect. - (SA‑C3a) Policy, procedure, and channel remain neighbors. A cited
policyOrProcedureRefis a separate current C.2.1 episteme; its currentness, applicability, and any edition relation must be established under their subject patterns. An optionalchannelRefnames an independently governed communication route or participating entity.
Keep three questions separate. utteranceSubjectRefs answers what the utterance or claim is about. institutionalTargetRefs answers which object or relation the act is intended to institute or update under the cited current policy or procedure. Actual change or institutional effect is a third world-side fact and is stated only through its exact direct change/effect relation and the matching typed institutes.* reference when the record needs it. An informative notice or assertion may have a subject without any institutional target or changed entity. Shared reference values do not collapse these relation meanings.
Record- and reliance-side constraints:
- (SA‑C4) A relied-on occurrence must be observable. When a gate, checklist, commitment, or grant relies on a
SpeechActRef, theSpeechActRecordSHALL identify that same occurrence and cite at least one applicable entry fromutteranceDescriptionLocatorsorcarrierRefs, or a separately governed evidence relation. Evidence-critical uses SHOULD cite at least one carrier through A.10. Record completeness alone does not prove occurrence or institutional force. - (SA‑C5) Institutional-effect claims are typed references to world-side effects.
institutes.*may reference only a separately obtaining commitment or relation occurrence through its declared RefKind. Eachinstitutes.commitmentsvalue resolves throughU.RelationRef constrained to U.Commitmentand is usable only when an identified policy applies and A.2.8's bearer, constitutive-rule, instituting-basis, and continuation conditions hold. Eachinstitutes.permissionsvalue resolves to oneGrantedPermissionRelation@Contextwhose participants, policy, scheme, and validity satisfy A.2.8.PER; eachinstitutes.systemRoleAssignmentsvalue resolves to one occurrence whose species is declared under A.2.1; and each publication value resolves to an obtainingEpistemePublicationRelationunder E.24.PUB. A status claim is an episteme about an effect; keep it and its A.10 evidence relation outsideinstitutes.*. A Bridge is added only if the receiving inference depends on translating or comparing local meanings across schemes. - (SA‑C6) F.9 only for a real cross-locality dependency. Cite an F.9 Bridge when a receiving check, gate, provenance claim, or effect inference actually compares, substitutes, or transfers a speech-act type or policy meaning between different local taxonomies, schemes, or policies. A different consumer, organization label, repository location, or downstream use does not by itself create that dependency. The same token in two local schemes does not establish equivalence, and a Bridge does not transfer institutional force by itself.
Last Updated: 2026-09-03 — upstream FPF commit b999972c (github.com/ailev/FPF)