A.15.PROD:11 - SoTA-Echoing
Scrum, NASA systems-engineering guidance, and IMO regulation are authoritative practice or regulatory sources for their named local questions. They are not treated here as SoTA merely because they are official or widely used. Manufacturing-information, product-information lifecycle, event-log, constructional-ontology, and provenance sources remain bounded comparators. None supplies a universal production ontology or a cross-domain answer to every A.15.PROD branch.
FPF synthesis scope. The three-question decomposition is an FPF-scoped architectural hypothesis for receiver-specific production recovery. The reviewed source set contains no independent best-known comparison that would justify calling Scrum, NASA, or IMO a SoTA answer to the cross-domain architecture. Their rows constrain only their named practice questions. The whole-to-proper-part and Work-closure architecture remains a bounded FPF hypothesis built from exact Work identity, direct predicates, state-satisfaction claims, and subject-practice closure rules. A later best-known comparison can reopen only the affected branch.
| Source, named branch question, and classification | Exact answer carried into A.15.PROD | Adoption status and blocked overread |
|---|---|---|
| Schwaber and Sutherland, The Scrum Guide, official edition 2020. Authoritative practice source for the bounded Scrum question. | The guide makes the applicable Definition of Done the quality-state criterion, says that an Increment is born when a Product Backlog item meets it, excludes work that does not meet it, permits multiple Increments before Sprint Review, and says that review is not a release gate. The guide does not identify exact Work or provide the subject-practice rule that closes Work. | Adopt for this bounded practice question, not as SoTA or a cross-domain production rule. The Definition of Done supplies only the branch-specific criterion; a Sprint, backlog item, Increment label, review, or release supplies neither the exact A.15.1 Work, its performer and effects, nor a universal production rule. |
| NASA NPR 7123.1D, Systems Engineering Processes and Requirements and the official NASA Systems Engineering Handbook product-realization guidance. Authoritative agency practice source family for its tailored realization question. | The sources distinguish implementation or integration, verification, validation, and transition. The handbook also keeps a validated end product separate from its later transition to the next product layer or user. They do not identify the exact local Work or make criterion satisfaction close that Work. | Adopt for the named NASA practice branch, not as SoTA or a universal completion rule. The tailored product-layer success, verification, or validation criterion can supply a local state-satisfaction basis; a validation report, transition record, or delivery is not the world-side boundary or the separate Work-closure governor. |
| IMO Resolution A.1215(34), Integrated IMO Identification Number Scheme and Circular Letter No.5096. Authoritative regulatory source family for ship designation. | The current scheme allocates an identifier at build or first registration, keeps it unchanged through the ship’s life, and explicitly says that allocation does not define ship status. It supplies neither an applicable identity rule nor inception or Work completion. | Adopt the stable-designation boundary, not as SoTA or an identity-inception rule. The number can help reidentify Ship 27 but does not by itself make the hull basis the ship, locate first existence, or establish completion, delivery, or operational status. |
| IEC 62264-2:2026. Current-standard reference for the manufacturing-information question: which operations objects and relationships can an interface exchange? | Sections 4.2, 4.6, and 4.8 keep exact work, actual resources, criterion or test content, boundary-state facts, records, and evaluation results separately recoverable; case 5.6 preserves an earlier completion claim after later destruction. | Adopt and adapt as an information-interface reference, not a SoTA-bearing production-recovery answer. An exchanged operations object, record, test result, or work definition establishes neither a Work occurrence admitted under U.Work nor any work-to-change, inception, or completion fact by form. |
| Failla, Rossoni, Quirini, and Colombo, “Managing lifecycle of product information with an ontology-based knowledge framework”, 2025. Current research proposal for the product-information traceability question. | Sections 4.2 and 4.8 and cases 5.2 and 5.5 preserve traceability between product knowledge and a project instance while keeping templates, cloned information individuals, records, and the project-world entity distinct. | Adapt for product-information lifecycle traceability, not physical or project-world inception. The paper does not supply A.15.PROD’s identity-specification applicability, earliest world-side boundary, work-to-change chain, or completion architecture. |
| IEEE 1849-2023 XES. Current-standard reference for the event-evidence interchange question. | Sections 4.4 and 4.8 and the plan-or-log anti-pattern let logs and event streams support reconstruction while exact A.15.1 work, A.3.4 transformations, work-to-change facts, identity, and completion remain independently governed. | Adopt for evidence interchange; reject as ontology. A logged event, timestamp, trace order, or extension attribute establishes neither a performed occurrence nor a causal, production, identity, or completion link by form. |
| Borgo and Righetti, “Towards Applied Constructional Ontology”, 2025. Ontology-design analogy about givens, constructors, dependence, mereology, and identity choices. | The Rationale and the construction-label and composition anti-patterns retain only the caution that a chosen ontology construction or label does not settle a product-construction fact. The paper supplies no production-work, project-world inception, or production-completion practice answer. | Retain as a sharply limited design analogy, not SoTA-bearing product-construction evidence. Lexical proximity between constructional ontology and constructing products supplies no support for sections 4.3-4.6 or case 5.5. |
| The historical W3C PROV-DM Recommendation, 2013. Historical lineage for provenance generation and availability. | Sections 4.1, 4.5, and 4.6 deliberately separate production-work participation, entity-identity inception, production completion, and later availability so each can have its own work, rule, boundary, and evidence. | Reject wholesale; retain as lineage. PROV remains useful for provenance interchange, but its generation bundle is not imported as FPF’s universal production ontology. |
The practical source-use result is visible in the Solution, checklist, and cases: the Scrum source supplies a bounded product-state criterion without collapsing review into release; NASA guidance distinguishes realization activities from transition; and IMO regulation supplies stable designation without status or inception. These are authoritative local constraints, not evidence that any one source is the best-known cross-domain production architecture.