Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 21:45:05 UTC

E.4:7 - Conformance Checklist

CheckPassing condition
CC-E4.1 First route and family caseThe work names the ecosystem question, classifies the likely case, points to the pattern that addresses the case or states what is missing, and opens a complete ecosystem-architecture record only when durable architecture or later reliance needs it. When a record is needed, it names whether the family member is Core, Tooling Reference, Pedagogical Companion, a foundational principle pattern set, a First Principles Framework edition, FPF Core, a domain principle framework, or a local practice framework.
CC-E4.2 Selected structures namedThe ecosystem-architecture record names its intended use and every field from FPFEcosystemArchitectureRecord@Context that the claim uses. Cite a source, pattern host, publication relation, or bounded model-use structure only when the record uses that independently established value.
CC-E4.3 E.5.3 respectedDependency direction points toward more stable framework editions, and Core does not depend on domain or local frameworks.
CC-E4.4 Publication and access separatedEach publication form or unit, presentation carrier, access route, access occurrence, and view keeps its subject and predicate. Apply the pattern that defines each claim.
CC-E4.5 Exact predicate and assertion namedEach architecture-adjacent claim names its exact subject and predicate; a pattern identifier is only the locator for the next question’s defining or constraining ClaimGraph.
CC-E4.6 Source-return presentAny carrier used as architecture evidence states captured structure, lost structure, admissible use, and the source to return to.
CC-E4.7 Framework carrier structure-account explicitA Readme, Architectural Reference, ToC, all-in-one carrier, skill-pack carrier, or other form-bearing framework carrier states which framework structures its selected form exposes for whom. An MCP, retrieval, search, or assistant route identifies the first form-bearing carrier or response it reaches and returns to the same account; it is not scored as that carrier. Missing form or adequacy content is repaired by stating the missing claim about the form or its adequacy using E.4.FPF, E.4.DPF, or E.4.DPF.DA before adoption or adequacy claims are made.
CC-E4.8 Product decision proportional and typedProduct remains Plain management wording. Each product decision names the subjects it makes claims about and the identity, edition, current-state, provision, publication, availability, or maintenance relations it uses. Framework support units stay in one product when their edition, use, access, and change rule agree; an adjacent subject needs an independent use or change reason. Shared use and one carrier are only probes. An unresolved kind is returned as a question, not U.Product.
CC-E4.9 DPF Suite truthA Suite describes a composite discipline whose constituents, knowledge-practice couplings, identity, composition-grounded characteristic and larger-assembly compatibility are recoverable under C.20. The framework exposes constituent DPFs and justified whole-level Methods, distinguishes external suppliers and support publications, and names what it covers. Discipline, framework edition, edition series, publication and maintenance remain distinct. The physical publication reflects the selected composition without ambiguous duplicate Method owners.
CC-E4.10 Architectural reference at the explained levelEach declared language assembly has a public architectural reference named for that whole, embedded or separately carried. It explains the connections and use-changing rationale of its level, returns to constituent explanations, and preserves direct pattern use. File divisions do not create assembly levels; an account does not by itself create a discipline, composite Method, independently managed product or product series.