fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 68494–68505

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 17:40:10 UTC

C.30.AD:10 - SoTA-Echoing

Deliberate exclusion. SysML v2 is not used here as SoTA or useful lineage. Search prominence, a systems-oriented name, and long-standing promotion do not show that it improves the practitioner questions above, and this pattern has no project evidence that it does. For C.30.AD it is a historical dead end. Reopen this boundary only if concrete project results change a rule, worked case, or practitioner action in this pattern.

Practice or source lineSource-use relation and currentnessC.30.AD adoptionAction consequenceBoundary
FPF C.2.1, A.22, E.17.0, C.30, and C.30.ASV separate episteme identity, selected structures, direct architecture relations, architecture claims, and structural-view adequacy.Current internal definitions for the objects used by this pattern.Reuse these objects instead of importing a second architecture-description ontology.Disciplines C.30.AD:4.1, C.30.AD:4.1a, C.30.AD:4.2, CC-C30AD-1, CC-C30AD-3, and CC-C30AD-4: every description has one exact EntityOfConcern and scheme; every asserted view has exact viewpoint conformance; correspondence and source use are explicit.A description or view remains an episteme and does not become architecture, proof, decision, or release authority.
Views-and-Beyond and related architecture documentation practice treats views as stakeholder-relevant projections over architecture.Mature reference and lineage source for view-based architecture documentation; not used as a mandatory current catalog.Adopt view usefulness while requiring exact E.17.0 viewpoint conformance and structure-kind recovery through C.30.ASV; description-set use remains claim content or a separate relation that actually holds.Disciplines C.30.AD:4.1a, C.30.AD:4.2, and the multi-view worked case: a view remains useful for a working concern without becoming the selected structure or a U.View by label.No mandatory view catalog or local membership relation is imported, and view adequacy remains in E.17.0 and C.30.ASV.
E.17.0 and MVPK publication machinery in current FPF.Current internal FPF definitions and publication practices for views, viewpoints, publication occurrences, forms, carriers, and publication separation.Reuse generic view and publication machinery instead of minting architecture-local copies.Disciplines C.30.AD:4.1a, C.30.AD:4.5, CC-C30AD-5, and CC-C30AD-6: architecture-description identity and composition remain separate from representation, publication occurrence, form, carrier, and publication-currentness.C.30.AD specializes architecture-description use; it does not replace E.17.0, E.17.1, E.17.2, E.17, E.24.PUB, or C.2.P.
C4, arc42, ADR, model-card, and system-card practice makes architecture communication practical.Current practitioner-source family for familiar architecture publication and documentation forms.Admit these as possible source publications, view publications, decision-description publications, transparency publications, or specification-use records.Disciplines C.30.AD:4.5, worked cases, and anti-patterns: practitioners can use familiar forms while keeping source, representation, publication, description, architecture, evidence, gate, decision, work authorization, release authorization, and other non-description claims separate.Template, card, graph, or diagram quality is not architecture adequacy by itself.
Tool-generated architecture relation graphs and code-agent architecture probing expose useful but partial structure.Emerging practitioner practice for recovering architecture-relevant relations from code, models, and generated analyses; currentness depends on the analyzed edition and tool run.Treat generated graphs as representations or source-derived descriptions with observed, inferred, and unknown relation boundaries.Disciplines C.30.AD:4.3, C.30.AD:5, and CC-C30AD-4: a generated output can guide structure recovery and next architecture moves only through a named source-to-use path; stronger use activates the declared source-return condition.Generated relation coverage does not become an obtaining subject relation, U.View, proof, gate passage, safety assurance, or complete architecture.