CC-E2DA-1 | Name FPFObjectUnderImprovementRef, use scope, reader scope, and qualification window. |
CC-E2DA-2 | Preserve E.2 as the source of Pillar meaning. |
CC-E2DA-3 | Evaluate all eleven Pillar coordinates with values, short rationales, and evidence loci, using the required result-row shape. |
CC-E2DA-4 | Justify values from FPF content, not review praise, landing, monolith placement, or absence of visible defects. |
CC-E2DA-5 | State declared use, status, stop or first repair, and reopen condition; add a non-use boundary only when an independently grounded reading changes that use. |
CC-E2DA-6 | Keep the pattern-derived rules in projections, packets, companions, and entry rows traceable to the supplying pattern bodies. Each authored definition, constraint, test, method instruction, or publication rule stays in its pattern body. Preserve E.11’s distinct locator, ordinary-entry, and Practical-Use Card functions, including the first-use guidance admitted for that form. |
CC-E2DA-7 | Treat E.21 and E.9.DA as evidence loci only where they change Pillar realization. |
CC-E2DA-8 | State what became worse when visible coordinates improved. |
CC-E2DA-9 | State the FPFPillarAdequacyEvidenceBasis. For every value, check the host, publication, projection, entry, source, relation or evaluation evidence it actually needs. Keep an unsubstantiated value and its evidence gap in draft material; do not assign an E.2.DA status until all eleven values are justified. |
CC-E2DA-10 | Use the value-appropriate adjacent comparison in E.2.DA:4.5a for every assigned value, including its endpoint rule for 0 or 5. |
CC-E2DA-11 | For broad wording, naming, or precision cleanup, state FPFKindRestorationEvidence for changed FPF-governed meanings. Preserve the pre- and post-repair object kind, relation or claim kind, admissible use, and scope; also preserve the current ontic slot, relation position, and use relation when they are part of the changed claim. When the changed position depends on cited pattern content, name its concrete contribution. An unaccepted semantic change lowers the affected Pillar coordinates and keeps the repair blocking. |
CC-E2DA-11a | When the evaluated FPF object includes ontic architecture, evaluate FPF-level effect, not ontic apparatus volume: reduced duplicate ontology or type explosion, clearer EntityOfConcern and SlotRelation boundaries, correct description-publication separation, thinner projections, and improved entry, authoring, review, or project use. Missing effect lowers the affected P1, P2, P4, P5, P6, P7, or P8 coordinates. |
CC-E2DA-12 | Keep Pillar values as ordinal evaluation results, not repair targets. Below-floor values require FPF-level findings or repair. Above-floor improvement requires substantive non-dominated proposal rows when requested; it cannot close by adding projection proof, entry apparatus, source volume, review praise, monolith parity evidence, or all-5 result framing that does not improve Pillar realization for the declared FPF use. A no-proposal or stay-at-current-value disposition must name loci and why no worthwhile Pillar-content improvement remains. |