Environment-Derived Requirements Register
Six environment-derived requirements are recorded here. Each is grounded in the environmental diagnosis from Chapter 2 and Chapter 3. Each traces directly to the evaluation protocol in Chapter 4 and the demonstration evidence in Chapter 10. Full problem-statement derivations are in Appendix: Environmental Grounding Dossier. Full traceability chains are in Appendix: Requirements-Design-Evaluation Traceability Matrix.
Requirement ID | Environment Derivation Summary | Derived Requirement | Acceptance Criterion |
— | — | — | — |
ER-01 | Diachronic demand versus synchronous artefact governance | Encode lifecycle-validity conditions with each transformation unit | Re-verification can be executed from declared conditions without global reinterpretation |
ER-02 | Cognitive burden from tacit cross-document inference | Publish machine-queryable invariants and interfaces | At least one invariant breach path and one pass path are reproducibly detectable |
ER-03 | Rework/delay from late conflict detection | Shift checks upstream and define baseline comparator | Baseline and artefact workflows are compared with explicit units and thresholds |
ER-04 | Accessibility intent loss in delivery transitions | Preserve semantic intent as first-class representations | Case evidence demonstrates relation-level accessibility checks |
ER-05 | Hidden coupling inflates verification scope | Require finite trigger-to-check mapping per local edit | Each transformation event traces to a bounded check set with escalation rule |
ER-06 | Interface drift and ungoverned complements | Enforce versioned rule compliance with exception governance | Every exception is typed, bounded, and justified against a rule set |
Each requirement row is traceable to a source anchor in Chapter 2 or Chapter 3. Each row links to at least one design feature and one evaluation measure in Chapter 10. Three primary cost dimensions are covered: time, cognitive burden, and physical usability. Requirements defined here establish the minimum problem scope the artefact suite must address. Therefore, the register functions as the authoritative source of requirement identifiers across the traceability matrix, evaluation workbench, and demonstration evidence appendices.