Code Families Legend

This appendix is the single consolidated legend for the short-form identifier families used across the thesis. Each family is a prefix that names a class of governed objects — requirements, design features, evaluation measures, contracts, claims, axioms, invariants, and the rest — so that the artefact chapters can refer to a specific object by a stable code rather than re-describing it on each mention. The legend pairs every prefix with its single uniform expansion, a one-line operational description, and the location where the family is defined and first used.

The legend consolidates and extends the List of Abbreviations, which defines the acronyms that appear in running prose. Where a family already appears there, this legend cites it and does not restate a divergent expansion; where a family is used in the chapter bodies, appendices, or figure specifications but is absent from the abbreviations list, this legend is its authoritative definition. For full conceptual definitions of the underlying constructs, see the Glossary and the Data Dictionaries; for the reference registers the codes index, see the Environment-Derived Requirements Register, the Evaluation Workbench, the Requirements–Design–Evaluation Traceability Matrix, the RecPol Specification, and the PlaniSyn Grammar.

Reading the table

Each row records a prefix, its uniform expansion, what an instance of the family denotes, and the defining location. A representative instance is given in parentheses where it aids recognition. The “Defining location” column points to the module that introduces the family on first use and carries its canonical inventory.

The argument-spine and traceability families

These families carry the thesis’s design-science traceability chain from problem to contribution. They are introduced in Chapter 4 and recur in every subsequent chapter.

The proposition and property families

The two P senses are deliberately distinguished at every first use per the property-versus-proposition discipline, because P1–P5 carries two distinct meanings.

The alignment is one-to-one: Property Pn motivates Proposition Pn, which is tested by evaluation question EQ-0n. The abbreviations list records the proposition sense; the property sense is qualified in prose by the word “Property” at first use, never left as a bare Pn.

The notation families (RecPol and PlaniSyn, Chapter 7)

These families govern the two-layer planimetric notation. RecPol is the formal core; PlaniSyn is the applied layer. The full inventories are in the RecPol Specification appendix and the PlaniSyn Grammar appendix, with operational definitions in the Data Dictionaries.

The empirical-substrate families (Chapter 8)

These families govern the empirical substrate: its claims, its scope limits, its cross-pipeline coherence probes, and its packing-efficiency indices. The supporting registers are in the Chapter 8 supplementary-context modules.

The cross-chapter handoff-contract family (HC)

HC names the formal interface a chapter hands to the chapter that consumes its product. The abbreviations list registers only the HC-6 series; the full series is registered here. The handoff chain itself is documented in the Artefact Suite Handoff Contracts appendix.

Module-type and instance-suffix codes

The nine governed-kernel module types (ENT, CIR, SAN, BED, LIV, KIT, SVC, EXT, DWL), the Rule-4 variant tags (HLP, LNK, OFC, DIN), and the Chapter 10 instance suffixes (BRn for BED-class instances, BAn for SAN-class instances) and trajectory codes (S0–S5, E0→1 … E4→5) are registered in the List of Abbreviations under “Modularity-scheme primitives” and “State and trajectory codes” and are not duplicated here.

The infix grammar

Several families embed a chapter or category infix between the prefix and the running number. The conventions are uniform across the thesis and are stated here once.

• The -4W- / -09- evaluation-measure infix. An evaluation measure carries the chapter that operationalises it as an infix. EM-4W-01 to EM-4W-03 are the three measures defined and pre-registered in Chapter 4 (the “4W” workbench notation); EM-09-01 to EM-09-04 are the four measures executed and reported in Chapter 10 against the Chapter 9 generator outputs. The infix is the chapter binding, not a sub-series: EM-4W-* and EM-09-* are one seven-measure set, three pre-registered and four executed.
• The design-feature chapter infix. A design feature carries its chapter as a two-digit infix with a sub-letter: DF-05A-01 is a Chapter 5 design feature, DF-06B-01 a Chapter 6 feature, DF-07C-* Chapter 7, DF-08D-* Chapter 8. The sub-letter tracks the artefact letter the chapter develops.
• The -CW- candidate-work and -AW- author-work infix. A deferred-work item is named Ch{N}-CW-{NN} (candidate post-submission work) or Ch{N}-AW-{NN} (author-carried limitation or future-work commitment), where {N} is the originating chapter and {NN} the running number — for example Ch5-CW-04 (single-rater calibration scope) and Ch6-AW-04 (cross-corpus generalisation).
• The trailing ER suffix. A deferred-work code may carry a trailing ER to mark that the item is an external-review obligation — a check that, by its nature, requires an independent third party rather than the candidate or author to discharge. For example Ch7-CW-10ER is the independent third-party Goodman-verification item: candidate-work that is sealed only on external review. The suffix is read as part of the code, not as a separate token.

Cited-undefined codes: resolutions and flags

The seal requires every code cited as an authority in examiner-facing prose to be either enumerated here or, where its meaning is not determinable from the text, flagged for operator judgement. The following are the determinations.

Enumerated (defined above and resolvable from the text)

• EXP-* — Experiment file. A sealed experiment record under experiments/recpol-v6/ or the corresponding experiment directory (for example EXP-7.5-hc6-compliance.md, EXP-6.3-interactive-plane-semantics.md, EXP-5B.1), cited as the provenance for a notation or semantic result. Note: every use in the body and appendices is the experiment-file sense; the List of Abbreviations previously glossed EXP as “Exemplar file (PlaniSyn-encoded)” and has been corrected to the uniform experiment-file expansion, so the two records now agree.
• EC-01 … EC-10b — Extensibility Contract clauses (EXP-7.6); enumerated under the notation families above.
• SL-02 … SL-06 — Scope Limits; enumerated under the empirical-substrate families above (SL-02 source bound, SL-03 packing cap, SL-04 hardcoded thresholds, SL-05 untestable probes, SL-06 boundary-margin sensitivity).
• INV-C / INV-I — Configurative-plane and Interactive-plane invariants; enumerated under the notation families above.
• NR-014 — Notation Rule 014 (the four typed interaction declarations realising the three interface types); enumerated above.
• G-V-01 — Generator-Verification audit 01 (the 2026-04-24 D8-canonicalisation implementation audit confirming the 100 canonical packings are unique under the D8 equivalence relation). Determinable from the Chapter 8 polyomino-grammar supplementary module; registered here as a generator-verification audit identifier.

Flagged for operator judgement (not determinable from examiner-facing text)

• T-E-01 / T-V-01 — No definition or use exists anywhere in the examiner-facing text (publish-text/). The strings appear only in non-examiner working records (debt registers, plans, and archived drafts). They cannot be enumerated from context. Flag: if these codes are cited in any examiner-facing passage, the citation is orphaned; if they are not cited there, no legend entry is required. Removal from prose, if any citation is found, is a separate operator decision and is not performed here.
• AM-08 — Cited once in examiner-facing text, as an axiom-trace tag on invariant INV-P-06 (“Axiom trace: DA-06; AM-08”) in the Data Dictionaries. Resolved — the citation is correct: AM-08 is Identity Preservation Under Transformation, entry 08 of the Abstract Model Specification Register (AM-01–AM-18) established in the working experiment record EXP-3.4-abstract-models.md. The INV-P-06 trace pairs the design-axiom warrant (DA-06, Stratified) with the abstract-model commitment (AM-08); both halves are intended, so the trace is correct as written (it is not a stale alias for DA-08, which is the unrelated “Extensible” axiom). The only residual is presentational: the AM register is defined in a working experiment file rather than in examiner-facing text, so promoting an AM-family summary into this legend is an optional operator choice, not a correction.
• DP-R — Listed in the audit’s family census but not present in examiner-facing text; it appears only in audit and plan working documents. No examiner-facing definition or use exists, so no legend entry is warranted. Flag: audit-internal label only; carried here for completeness, no action required in publish-text/.

ER expansion: the locked decision

The List of Abbreviations previously hedged the ER expansion as “Evaluation Requirement (or Evaluation Reference)”. The seal requires a single uniform expansion, and the evidence fixes it unambiguously:

• The two registers that own the ER-01 … ER-06 identifiers are titled the Environment-Derived Requirements Register and the Environmental Grounding Dossier, and each row is an “environment-derived requirement”.
• Chapter 4 introduces the family as “six environment requirements (ER-01 to ER-06), each a governance obligation derived from the housing-adaptation problem”, and the traceability matrix routes “environment-derived requirements through design features to evaluation measures”.
• Neither “Evaluation Requirement” nor “Evaluation Reference” matches any register title or body usage; both hedge expansions are spurious.

Locked expansion: ER = Environment Requirement (equivalently, environment-derived requirement), uniform across the abbreviations list, this legend, and the requirements appendices. The hedged abbreviations-list entry is corrected to this single form.