platform-admin/boc - boc - Gitea: Git with a cup of tea

platform-admin/boc

Fork 0

Commit Graph

Author	SHA1	Message	Date
Bernt	54255eeae9	docs: RFC-002 Input + Definition of Done + Compliance Matrix update - RFC_DEFINITION_OF_DONE.md (v1.0, LOCKED): - 12 criteria for every RFC component - Sign-off roles: Author, Reviewer, Automated, QA - Exit criteria: all 12 must pass - RFC-002: Canonical Input Component: - Cognitive Purpose: captures free-form text/numeric data - When to Use/NOT Use: clear boundaries vs Select, Switch, Date Picker - Interaction Contract: click, type, tab, blur, enter, escape - Failure Behaviour: invalid, network, max length, required, disabled - Accessibility Contract: label, focus, error, required, screen reader - AI Contract: when to choose Input vs alternatives - Token Dependencies: 13 tokens (bg, border, text, padding, radius, sizes, states) - Layout, Sizes (sm/md/lg), Variants (default/ghost/filled), States (8 states) - Keyboard, Touch, Motion (with reduced motion) - Anti-Patterns: placeholder as label, validation only on submit, etc. - Related Components: Select, Textarea, Search, Form, Label - DDR References: DDR-001, DDR-002, DDR-003 - Acceptance Criteria: 10 checklist items - COMPLIANCE_MATRIX.md: Input updated to 33% (Governance 🟡, Tokens 🟡, Motion 🟡, Accessibility 🟡, AI ✅, QA ⏳) Rationale: Validate RFC-001 template works for different component types. Definition of Done ensures consistent quality. Compliance Matrix tracks progress visibly.	2026-07-02 10:38:23 +00:00
Bernt	b0a1808b2b	docs: AI Principles restructured + Compliance Matrix + Platform governance + RFC-001 Button - AI_DESIGN_PRINCIPLES.md: - Restructured into 5 parts: A. Decision Process, B. Component Selection, C. Token Usage, D. Design Review, E. Escalation - All rules use RFC 2119 normative words (MUST/MUST NOT/SHOULD/MAY) - Clearer escalation path: when to create DDR, when to flag uncertainty - COMPLIANCE_MATRIX.md: - Tracks readiness for all 29 components (Tier 1/2/3) - 6 dimensions: Governance, Tokens, Motion, Accessibility, AI, QA - Foundation documents tracked separately - Button at 82% (reference for others) - docs/platform/README.md: - Reserved directory for cross-cutting governance - Future: AI Governance, Product Governance, Review Process, Quality Gates, Release Governance, Decision Frameworks - Separates platform governance from design system - LANDVEX_DESIGN_SPECIFICATION.md: - Button renamed to RFC-001: Canonical Button Component - Structured with: Cognitive Purpose, When to Use/NOT Use, User Expectation, Interaction Contract, Failure Behaviour, Accessibility Contract, AI Contract - Sets standard for all future RFC component specs Rationale: AI rules before components (AI writes components). Compliance matrix makes progress visible. Platform governance separates cross-cutting concerns from design system. RFC format for components ensures production-ready specifications.	2026-07-02 09:06:08 +00:00

Author

SHA1

Message

Date

Bernt

54255eeae9

docs: RFC-002 Input + Definition of Done + Compliance Matrix update

- RFC_DEFINITION_OF_DONE.md (v1.0, LOCKED):
  - 12 criteria for every RFC component
  - Sign-off roles: Author, Reviewer, Automated, QA
  - Exit criteria: all 12 must pass

- RFC-002: Canonical Input Component:
  - Cognitive Purpose: captures free-form text/numeric data
  - When to Use/NOT Use: clear boundaries vs Select, Switch, Date Picker
  - Interaction Contract: click, type, tab, blur, enter, escape
  - Failure Behaviour: invalid, network, max length, required, disabled
  - Accessibility Contract: label, focus, error, required, screen reader
  - AI Contract: when to choose Input vs alternatives
  - Token Dependencies: 13 tokens (bg, border, text, padding, radius, sizes, states)
  - Layout, Sizes (sm/md/lg), Variants (default/ghost/filled), States (8 states)
  - Keyboard, Touch, Motion (with reduced motion)
  - Anti-Patterns: placeholder as label, validation only on submit, etc.
  - Related Components: Select, Textarea, Search, Form, Label
  - DDR References: DDR-001, DDR-002, DDR-003
  - Acceptance Criteria: 10 checklist items

- COMPLIANCE_MATRIX.md: Input updated to 33% (Governance 🟡, Tokens 🟡,
  Motion 🟡, Accessibility 🟡, AI ✅, QA ⏳)

Rationale: Validate RFC-001 template works for different component types.
Definition of Done ensures consistent quality. Compliance Matrix tracks
progress visibly.

2026-07-02 10:38:23 +00:00

Bernt

b0a1808b2b

docs: AI Principles restructured + Compliance Matrix + Platform governance + RFC-001 Button

- AI_DESIGN_PRINCIPLES.md:
  - Restructured into 5 parts: A. Decision Process, B. Component Selection,
    C. Token Usage, D. Design Review, E. Escalation
  - All rules use RFC 2119 normative words (MUST/MUST NOT/SHOULD/MAY)
  - Clearer escalation path: when to create DDR, when to flag uncertainty

- COMPLIANCE_MATRIX.md:
  - Tracks readiness for all 29 components (Tier 1/2/3)
  - 6 dimensions: Governance, Tokens, Motion, Accessibility, AI, QA
  - Foundation documents tracked separately
  - Button at 82% (reference for others)

- docs/platform/README.md:
  - Reserved directory for cross-cutting governance
  - Future: AI Governance, Product Governance, Review Process,
    Quality Gates, Release Governance, Decision Frameworks
  - Separates platform governance from design system

- LANDVEX_DESIGN_SPECIFICATION.md:
  - Button renamed to RFC-001: Canonical Button Component
  - Structured with: Cognitive Purpose, When to Use/NOT Use,
    User Expectation, Interaction Contract, Failure Behaviour,
    Accessibility Contract, AI Contract
  - Sets standard for all future RFC component specs

Rationale: AI rules before components (AI writes components).
Compliance matrix makes progress visible. Platform governance
separates cross-cutting concerns from design system. RFC format
for components ensures production-ready specifications.

2026-07-02 09:06:08 +00:00

2 Commits