Canonical Property-Proposition-Evaluation Map

This appendix is the single consolidated map of the thesis’s evaluation spine. It pairs each critical property with the proposition it motivates, the meta-requirement that grounds it, the evaluation question that tests it, the formative and summative measures that instrument it, and the evidence objects that warrant it. Every downstream verdict recital, in Chapter 10, Chapter 11, and Chapter 12, cites this map rather than restating the chain, so the correspondence is fixed in one place. The short-form identifier families used below, SP, ER, MR, EQ, EM, EVID, and the two senses of P, are defined in the Code-Families Legend; this map is their consolidated wiring, and it inherits that legend’s property-versus-proposition discipline.

Reading the table

Each row records one proposition, P1 to P5. The Critical Property column names the problem-class property from Chapter 2, Section 2.9 that motivates the proposition; the Proposition column gives the canonical mechanism name from Chapter 3, Section 3.5, which is the name the List of Abbreviations records. The alignment is one-to-one: Property Pn motivates Proposition Pn, which is tested by evaluation question EQ-0n. The measure columns carry the chapter infix fixed in the Code-Families Legend: EM-4W-* are the three measures pre-registered in Chapter 4, and EM-09-* are the four measures executed and reported in Chapter 10 against the Chapter 9 generator outputs. Proposition-level success is adjudicated under the four-result and promotion scheme of Chapter 4, Section 4.5, not by a separate success-criterion code.

The map

Notes on the map

• Argument-spine position. The map is the Evaluation stage, SP-03, of the four-stage argument spine registered in the Code-Families Legend (SP-01 Problem, SP-02 Artefact, SP-03 Evaluation, SP-04 Contribution, defined at Chapter 4, Section 4.1). The environment requirements in the linked-ER column are the SP-01 problem anchor; each proposition licenses a technological rule (TR-01 to TR-04, Chapter 11, Section 11.2) as its SP-04 contribution.
• Two naming registers. Each proposition carries a property name and a mechanism name, and both are load-bearing: the property name states what the proposition is a property of, the mechanism name states how it holds. This table fixes the mechanism name (Section 3.5, the List of Abbreviations sense) as the canonical proposition name and keeps the property name in its own column; recitals that name a proposition by its property (for example “Proposition 1, interoperability”) and recitals that name it by its mechanism (for example “Proposition 1, semantic interface and identity persistence”) both resolve to the same row.
• Formative-measure gaps. Only P1, P2, and P4 carry a Chapter 4 formative measure (EM-4W-01, EM-4W-02, EM-4W-03). P3 has no EM-4W-*; its formative round-trip evidence is inherited from Chapter 7, Section 7.20. P5 is summative-only, evaluated in Chapter 10 through EM-09-03.
• EM-09-01 definition. The EM-09-01 metric is the standards-interpretability aggregate resolution rate with a pre-registered floor of a 0.25 aggregate delta, computed from clause-level trace-completeness inputs, as fixed at Chapter 4, Section 4.4. Where the Requirements-Design-Evaluation Traceability Matrix records EM-09-01 as a “trace-completeness index”, that is the input term of the same three-term relationship (trace completeness to resolution rate to ambiguity reduction), not a competing definition.
• P4 evidence set. Proposition 4 is warranted by both EVID-P4-VARIATION and EVID-P4-EXCEPTION-BUDGET; the single-object entry in the Section 4.4 traceability matrix is an omission reconciled here.
• Success adjudication, not success codes. The SC-01 to SC-05 success-criterion labels used in the Section 4.4 traceability matrix are not reproduced here: proposition-level success is adjudicated by the Section 4.5 four-result and promotion scheme, and the artefact-level acceptance criteria live with their artefact chapters. The SC prefix in the Code-Families Legend denotes the Chapter 7 semantic contracts (SC-1 to SC-5), a distinct family; reconciling or retiring the Section 4.4 SC-0n labels against these is a residual for the Section 4.4 and legend sweep.

Codes above are defined in the Code-Families Legend; the full measure specifications are in the Evaluation Workbench and Chapter 4, Section 4.4.