Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:20:10 UTC
E.18.1:7 - Conformance Checklist
CC-E18.1-1 The P2W use starts from an accepted ProblemCard@Context or stops before P2W begins.
CC-E18.1-1a The accepted ProblemCard as the note’s EntityOfConcern, the note’s ClaimGraph and effective ReferenceScheme, any separately identified U.Viewpoint or BoundedModelUseStructure designated by that ClaimGraph, each cited pattern’s subject EntityOfConcern, and every supporting compact note, diagram, plan, trace, or publication remain distinct. Note completeness does not prove a P2W relation occurrence, subject change, performed work, evidence, acceptance, or result.
CC-E18.1-1b Every materialized carry-through episteme identifies one accepted ProblemCard as EntityOfConcern, carries one ClaimContent for the receiving use, names its effective ReferenceScheme, and designates a separately identified U.Viewpoint episteme or BoundedModelUseStructure only when the claim uses that object and its organization changes how the receiving claim is interpreted. It cites the carried ProblemCard slice, applicablePatternRef, returned value kind and ref or honest stop, and rationale. It introduces no reusable P2W predicate, RelationSignature, relation kind, local note kind or occurrence.
CC-E18.1-1c When external naming or publication is current, F.8/F.18/F.17 apply only to the exact already identified value and receiving use. The pattern label and local positive/stop/replay phrases create no NameCard, U-kind, relation, Method or MethodDescription. Any MethodDescription claim separately passes the exact A.3.2 EntityOfConcern and substantive-claim threshold.
CC-E18.1-2 A positive carry-through ClaimContent cites one exact returned result and one or more separate continuation descriptions. A stopped ClaimContent instead states the reduced-use cue or blocker and stop without fabricating a relation. Local non-overread and return conditions appear when relied on; absent fields are not filled by generic unions.
CC-E18.1-3 The stable core works without an episteme or explicit structure: accepted claim, receiving use, concrete question, applicable pattern contribution, returned result or honest stop, split, and smallest local return. When explicit structure is needed, A.22.CGUS and E.18.3 select the exact structure; E.18 keeps several valuations or one internal SubflowRef on one TFS; E.18.NET keeps independently selected flows or nested networks and exact cross-member occurrences. E.18.1 adds no hybrid schema.
CC-E18.1-4 One wording span from an admitted source may split into several FPF applications; the record does not compress them into one generic token.
CC-E18.1-5 Result wording is unpacked into concrete result-related relations; a generic WorkResult kind is not admitted.
CC-E18.1-6PrincipleFrame references keep postulates and CHR observability distinct from units, planes, comparators, thresholds, ontology editions, CHR editions, plans, work, evidence, and gates.
CC-E18.1-7 Measurement, G.11 source-currentness relation, reference-plane, method-set, comparator, or problem-side changes return to the smallest affected application.
CC-E18.1-8 The stable P2W core contains only accepted claim, receiving use and concrete question, applicable pattern contribution, returned result or honest stop, split, and local return. Reliance notes, explicit E.18.3 structure, development examples, and naming or publication are optional extensions. No extension may add a core input or change a returned result. Relation obtaining and identity, occurrence declarations, admission, production, evidence, gates, decisions, and other neighbouring algorithms remain in the patterns whose Solutions answer those exact questions.
CC-E18.1-9 Local boundary wording remains only where it names a near-miss that changes the next P2W application.
CC-E18.1-10 The pattern leaves one usable next move: apply the pattern that answers the question and use its result, write a compact note when another person or later action needs replay, split independent claims, keep a cue and stop, or reopen only the continuation affected by a changed relation.
CC-E18.1-11 For a structure-bearing conformance or authoring use, replay at least one pilot from 5.3 and classify it as several valuations of one exact TFS, one parent-relative internal SubflowRef, or one E.18.NET network of independently selected members and exact cross-boundary occurrences. Keep every member boundary, Work, actual transformation, valuation, position binding and DesignRunTag local. The self-evolving-spec case keeps use-found evidence outside practitioner-facing prose. Ordinary P2W use does not open this extension.
CC-E18.1-12 Every carried claim family can be lowered, stopped, split, or reopened through E.18.1:4.7; a cue from a wording span in an admitted source or from a source-pack cue that cannot name the recovered FPF kind or relation remains a reduced-use cue.
CC-E18.1-13 Every materialized replay identifies the changed value, occurrence, assertion, or description; its kind and changedValuePatternRef; what still carries and what no longer carries; the smallest reopened continuation; any current G.11 currentness line; and nextApplicablePatternRef. If the changed object is relation-bearing, the cited result—not a P2W copy—retains its kind, participants, obtaining or claim basis, occurrence-identity rule, and any receiver-conditioned RelationSignature or typed SlotSpecs.
CC-E18.1-14 When a generated DPF seed or cheap framework seed enters P2W, the record names the G.2 source-use record, selected source U.Episteme reference, exact EpistemePublicationRelation occurrence reference when availability is material, source-pack cue, or source-pack return when that source use is current; the problem-side cue when that is current; the next concrete claim or relation-specific question, including its participants when a relation is asserted; the next applicable pattern selected from the canonical Relations map; and the stop condition that prevents the seed from becoming public authority by generation alone.
CC-E18.1-15 An actual-transformation continuation carries only an exact current value or blocker returned by A.3.4; E.18.1 does not reconstruct the occurrence basis or infer actuality or composition from a method, plan, model, description, flow position, adjacency, shared work, or common referent.
CC-E18.1-16 A work-to-change continuation cites the exact positive or negative claim or blocker already returned by the named subject predicate’s defining pattern or the applicable A.6.RCD route. It keeps the actual U.Work and U.Transformation references when they are part of that result, but does not reconstruct occurrence proof, predicate tests, failure classification, or negative-claim closure. The BuildOps and Pump 14 slices show positive carry-through; Pump 14 also preserves the earlier missing-governor stop. A production continuation likewise carries only the result or blocker returned by A.15.PROD.
CC-E18.1-17 A PatternID reference, selected or recommended continuation, imperative wording, intended realization, plan seed, graph or filled table admits no U.MethodDescription. Membership exists only for an independently identified C.2.1 episteme whose exact EntityOfConcern is one admitted U.Method and whose ClaimContent contains at least one substantive way-of-doing claim.
CC-E18.1-18Move remains Plain wording for the exact current object or use action. Proposed or chosen work remains distinct from dated performed Work; no universal Move kind, record or relation is introduced, and wording performs nothing.
CC-E18.1-19 The local mantra is the compact formula in 4, answers one stated decision, maps every term to independently identified values, has the filled cooling use, and stops at the applicable neighboring pattern. It is not the five-row display, a Method, MethodDescription, plan, Work, CGUS or structure identity.