E.4.DPF.DA:4.4 - Evidence basis and where to check it
Use these sources and patterns instead of expanding this pattern into a package bureaucracy:
| Evidence or defect | Evidence source or pattern to use |
|---|---|
| Source payload, rejected alternatives, source currentness, and source-use boundary | G.2, G.11 |
| Public field promise, selected problem-family pattern sets, representative use, every pattern required for the first use, and each relied-on external result with its direct kind, supplying product, edition or current state, receiving use, discovery route, material currentness or availability, and externality | E.4, E.4.PFAD, E.4.DPF, E.4.PFR where a dependency or recorded relation actually obtains, and E.8:4.1.3 for the four return boundaries |
| First-then versus simultaneous contribution and several-structure synthesis | B.1.5, A.22, A.22.CGUS, C.30.AD, and a completed C.32.MWA result when several structures need reconciliation |
| Common framework publication form | E.11.PFP and E.4.DPF; use E.4.PFIP separately when accepted-source integration or predecessor continuity is claimed |
| Individual pattern quality | E.21 |
| Pattern admission or profile gating | E.19 |
| First-entry, publication occurrence/form/presentation carrier, access route, and actual access or use | E.24.PUB, E.11, E.17, and the direct access or use pattern |
| Carrier structure-account, captured/coarsened/lost structure, where readers return for fuller sources, and structure-capture or epiplexity account | E.4.DPF, E.11, E.17, A.6.3.CSC, C.33, C.34, and A.6.3.NAR when sequential narrative rendering is load-bearing |
| Naming and local vocabulary | E.10, F.18, and the pattern that defines or constrains the named subject |
| Ordinary wording defects and precise plain language | F.19; use E.10 for cues and the pattern that defines or constrains an unresolved subject meaning |
| Generated or searched package candidate intended to inform architecture work | C.35, then E.4.PFAD or the pattern that defines, constrains, or tests the candidate content being used |
| Carrier capture, loss, and preservation | C.33, C.34 |
| Improvement framing and repeated improvement | E.22, E.23 |
| Evaluation characteristic space and specification, semantic Method, ordinary evaluator action or references to an exact A.13 actual evaluator and independently valid A.15.1 assessment-Work account, optional same-assignment A.2.1/F.6 attribution only when the result expressly represents it, optional A.6.1 application when an operation declared by a separately admitted Mechanism is actually used, coordinate claims, aggregate result episteme, witnesses and evidence use, local status, and external admission or status use | A.19.ECS, this E.4.DPF.DA specification, A.3.1 and A.3.2, A.13 and A.15.1, A.2.1 and F.6, A.6.1, C.2.1, A.10, F.10, and E.19 respectively |
| FPF-level Pillar effect | E.2.DA, only when the package changes FPF-level adequacy |
When a coordinate is below floor, return a finding or repair proposal. When a coordinate is at 4 and improvement is requested, search for a substantive non-dominated improvement. Do not raise a value by adding proof apparatus, more maps, more citations, or quality-status prose unless the package becomes easier to use, more source-grounded, more accurately bounded, or more refreshable.