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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 05:05:10 UTC

A.15.5:7 - Conformance Checklist

IDA conforming readiness use…Check
CC-A15.5-1names the exact WorkPlan, PlanItem, intended performance, criterion, and evaluation time.The readiness result cannot float free of the plan content and bounded entry question it judges.
CC-A15.5-2separates readiness from performed work.No target U.Work occurrence is asserted unless dated work evidence is current.
CC-A15.5-3separates full-kit inputs from preparation and checking Work.Cite preparation or checking as actual only through one exact dated U.Work, performer system, obtaining assignment, enacted Method, extent, and required actual bindings.
CC-A15.5-4cites planned baselines without rewriting them.A.15.3 planned-filling rows remain declaration-local content inside the exact WorkPlan.
CC-A15.5-5keeps gate decisions in A.21.Readiness labels do not create GateDecisionResult without A.21 fields.
CC-A15.5-6keeps resource readiness and resource aggregation distinct.Planned reservations and actual consumption are not merged.
CC-A15.5-7states stop, degraded-use, or recheck condition.The reader can tell whether to stop, probe, commit, launch, or name a missing value under its subject pattern.
CC-A15.5-8keeps prospective and retrospective permission inputs temporally typed and non-productive.A current grant uses its validityWindow; non-prohibition uses its evaluationWindow; conflict uses its overlapWindow and any subject-pattern resolution effectiveWindow. Exercise and non-violation appear only for different dated Work or an explicit post-launch recheck, with their own intervals. None proves another permission value, readiness, gate passage, capability, or target-work performance.
CC-A15.5-9keeps the readiness result, domain-local inputs, provenance, assurance, and any inception claim under their subject patterns.C.2.1 identifies the readiness-result episteme; each measurement, evaluation, resource, permission, gate, or other input keeps its own result algebra; use A.10 for provenance and state any assurance result separately under B.3, and A.15.PROD is opened only for a separately current local entity-identity inception claim.