Quality Requirements
Quality Requirements Overview
| ProductShape requirement | Architectural realization | Evidence or gap |
|---|---|---|
| QR-DETERMINISM-001: identical content gives identical structural results | Core logic is deterministic; generated artifacts are derived from the model | packages/core/; CI and conformance workflows compare behavior. The product requirement owns the pass criteria. |
| QR-PORTABILITY-001: consistent supported development platforms | Node.js package with platform-neutral path handling and no shell-dependent core logic | .github/workflows/ci.yml runs a Linux, Windows, and macOS matrix on Node 22 and 24. |
| QR-ACCESSIBILITY-001: generated explorer is keyboard operable and understandable without color | Semantic HTML, visible focus, keyboard controls, and embedded assets are implemented in the snapshot renderer | packages/cli/src/snapshot/; product verification criteria require rendered inspection. |
| QR-PRESENTATION-001: compact, text-first snapshot | System fonts, restrained palette, explicit artifact-kind labels, responsive layout | Snapshot source and scripts/screenshot-snapshot.mts; inspect rendered results against the requirement. |
Quality Scenarios
The model's quality requirements define their own measurable scenarios. This view records the architectural mechanisms and directs verification to the canonical requirements rather than restating their acceptance criteria.