Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:20:20 UTC

A.15.1:13.1 - SoTA-Echoing

SoTA alignment rule. A source tradition counts here only when it preserves the local separations: U.Work is the admitted kind; one Work individual is a world-side dated occurrence; each actual performer is an admitted U.System with an A.13 agency basis for the action, scope, and window; and A.15.1 independently admits the Work from that performer basis plus its history, enacted Method, temporal extent, and locally declared containing-System relation. F.6 enters only when the receiving use also consumes precise assignment-bound attribution through the same obtaining A.13 assignment; a missing or failed F.6 relation leaves W : U.Work intact. An assertion or description about the occurrence is a separate U.Episteme. Several containing Systems may be valid under different stated boundaries. Work-to-referent, binding, and resource-use relations are added only when they independently obtain. Neighboring change, evaluation, evidence, production, delivery, acceptance, and responsibility claims remain separate.

Source traditionSource reference and status, qualified 2026-08-26Local invariant adoptedShortcut rejected
Occurrent and 4D occurrence ontologyISO/IEC 21838-2:2021, BFO 2020, and BORO-style extensionalism are mature identity lineage, not a newly published operational practice.U.Work admits dated occurrence holons; each Work individual has its own temporal extent and participates in separately obtaining occurrence relations, while assertions and records about it remain separate epistemes. Parts, retries, resumptions, and overlaps stay explicit.Treating a Method factor, diagram, system-role label, log entry, or record schema as the performed occurrence.
Object-centric event logging and process miningThe OCEL 2.0 semantic specification remains the semantic basis; the OCEL 2.1 revision adds a compact single-file CSV serialization and a bundled format using CSV or Parquet tables.Event records can support Work claims only when they designate independently grounded candidate actions and make every actual performer’s A.13 basis, enacted Method, temporal extent, local containing-system relation, and any relied-on object, binding, resource-use, interpretation, or policy relation recoverable. Any precise assignment-bound attribution remains a separate later F.6 result. A serialization revision changes neither Work identity nor these admission conditions.Treating telemetry or event rows alone as Work occurrences or as membership evidence for U.Work.
Observability and telemetry practiceOpenTelemetry Specification 1.60.0 and its current traces, metrics, and logs practice.Telemetry can support, replay, measure, or diagnose a claim about Work, but the occurrence still needs every actual performer’s A.13 basis, independently grounded history, enacted Method, temporal extent, and local containing-system relation. Add F.6 only for a separately claimed precise assignment-bound attribution, and add another enactment, affected-referent, binding, or resource-use fact only when the receiving claim uses it.Counting trace, metric, or log existence as the performed Work, a result, or dominance evidence without the direct evidence, comparison, or archive relation.
Provenance and evidence-provenance practiceW3C PROV is a mature recommendation; the 2025 PROV-O and BFO alignment is a later interoperability contribution.Assertions or descriptions about Work cite the evidence-provenance relations and currentness notes their use needs without letting evidence, assurance, gate, or provenance claims replace the occurrence.Using a provenance relation, assurance statement, or gate result as if it were the performed Work.
Temporal-interval and aggregation practiceInterval-algebra lineage plus current operations-management use of utilization, lead-time, and resource-ledger roll-ups.A.15.1 supplies identified Work intervals, parts, and performed resource-use facts; use B.1.4 for temporal aggregation and B.1.6 for work-resource aggregation, each with its stated policy and admissible use.Mixing union, hull, parent cost, child cost, and ordinal comparison on the Work object without a recovered Part B aggregation claim.

Qualification and smallest reopen. A newer source reopens this table only when it changes an admission fact or a relation used by a receiving Work claim. Revise the affected row and its matching admission, example, checklist, or public cue; do not rewrite unrelated Work identity content merely because a source version advanced.