Files
boc/docs/design/foundations/RFC_DEFINITION_OF_DONE.md
T
Bernt 5beb8fb640 docs: Capability Parity Principle + Definition of Done update
- LANDVEX_DESIGN_CONSTITUTION.md:
  - Added §0a: Capability Parity Principle
  - All user functions must work on smartphone
  - Desktop may enhance, never require
  - Two-question rule for every new feature
  - Desktop as enhancer (not exclusive)
  - Examples: Payments, History, KYC
  - Verification checklist for every new feature

- RFC_DEFINITION_OF_DONE.md:
  - Added criterion #3: Capability Parity
  - Can be used on smartphone; desktop is enhancement
  - Total criteria: 14 (was 13)
  - Exit criteria: must pass all 14

Rationale: quiXzoom targets field workers. Phone is primary or only
computer. Phone must always be a full client. Desktop is a more
comfortable workspace for some tasks, not a prerequisite. This is a
constitutional principle, not implementation.
2026-07-02 11:40:57 +00:00

2.3 KiB
Raw Blame History

RFC DEFINITION OF DONE

Quality Gate for Every RFC Component

Version 1.0
Status LOCKED
Scope All Tier 1, 2, 3 components

Checklist

# Criterion Requirement Verified By
1 RFC Structure 100% complete per COMPONENT_TEMPLATE.md Self-check + Review
2 Core Principle Supports "From Reality → Decision" Self-check + Review
3 Capability Parity Can be used on smartphone; desktop is enhancement Self-check + Review
4 Cognitive Purpose Documented — what problem does this solve? Self-check + Review
5 User Expectation Documented — what does the user expect? Self-check + Review
6 Interaction Contract Documented — events, responses, state machine Self-check + Review
7 Failure Behaviour Documented — every failure mode handled Self-check + Review
8 Accessibility Contract Documented — WCAG 2.1 AA compliance Self-check + Review
9 AI Contract Documented — when AI chooses this component Self-check + Review
10 Token Dependencies All tokens listed, no hardcoded values Automated lint
11 Motion Follows Motion System v1, reduced motion included Self-check + Review
12 Anti-Patterns Relevant anti-patterns listed and avoided Self-check + Review
13 Compliance Matrix Updated in same PR Self-check
14 Reference Example Working implementation or Storybook story Implementation

Sign-Off

Role Responsibility
Author Self-check all criteria before requesting review
Reviewer Verify criteria 17, 910
Automated Verify criteria 8 (lint)
QA Verify criterion 12

Exit Criteria

MUST pass all 14 criteria before component is marked "Complete" in Compliance Matrix.

MAY merge with criteria 14 pending if implementation is in separate PR.


ÄNDRINGSHISTORIA

Version Datum Beskrivning
1.0 2026-07-02 Initial Definition of Done for RFC components

STATUS

LOCKED

  • Mindre revideringar: 1.x-serien
  • Brytande ändringar: Kräver Architecture Review, ny major-version (2.0+)