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
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
2e62e5fb80
docs: Glossary + Sanity Review + Normative Words
...
- GLOSSARY.md (v1.0, LOCKED):
- Normative words: MUST, MUST NOT, SHOULD, SHOULD NOT, MAY (RFC 2119)
- Core concepts: Component, Variant, State, Token, Primitive/Semantic/Component
- Layout: Page, View, Screen, Panel, Module, Overlay, Drawer, Modal, Dialog, Sheet
- Visual: Layer, Elevation, Surface, Backdrop
- Interaction: Focus, Hover, Active, Disabled, Loading
- Tokens: Brand, Semantic, Status, Neutral
- Governance: Constitution, Doctrine, Specification, DDR
- Sanity Review completed:
1. Terminology: Component (not Widget/Control), Token (not Variable),
Panel (consistent usage)
2. Normative words: Normalized MUST/MUST NOT/SHOULD/MAY across all docs
3. Naming: surface-primary, text-secondary, border-default (consistent)
4. Document hierarchy: correct upward references
5. Acceptance Criteria: consistent template (Button as reference)
- TOKEN_PHILOSOPHY.md: Replaced informal rules with RFC 2119 normative words
- DESIGN_SPECIFICATION.md: Replaced Rule: with MUST/MUST NOT
- ANTI_PATTERNS.md: Replaced Rule:/Forbidden: with MUST/MUST NOT
Rationale: Reproducible sanity checklist. Common language prevents
misunderstandings. Normative words make requirements unambiguous.
2026-07-02 09:02:41 +00:00
500d9c052b
docs: AI Design Principles + Button RFC + Release Definition
...
- Motion System v1:
- Renamed duration tokens from time-based (fast/slow) to intention-based
(instant, interaction, transition, navigation, layout, context-change,
attention, background)
- Updated all component motion tables to use intention-based tokens
- Rationale: AI reasons about purpose, not milliseconds
- Button gold standard (chapter 8.3.1):
- Added RFC-level sections: Cognitive Purpose, When to use/NOT use,
User Expectation, Interaction Contract, Failure Behaviour,
Accessibility Contract, AI Contract
- Sets the bar for all future component specifications
- AI_DESIGN_PRINCIPLES.md (v1.0, LOCKED):
- Core principle: AI must be a design system citizen
- Before-action rules: read hierarchy, check existing, apply New Component Rule
- Token rules: no hardcoded values, semantic first, lifecycle, deterministic
- Component rules: inheritance first, use template, document anti-patterns
- Motion rules: intention-based duration, reduced motion, no decorative animation
- Accessibility rules: WCAG 2.1 AA, no ARIA without purpose
- AI Contract for Button: when to choose Button vs Link vs Icon Button
- RELEASE_DEFINITION.md:
- Defines Landvex Design System v1.0 release gates
- Foundation, Tokens, Foundations, Components (Tier 1/2/3),
Validation, Production
- Current progress: ~55%
- Next milestones: Grid+Elevation, Input/Select/Card, Brand Palette
Rationale: AI rules before components (AI will write components).
Intention-based motion tokens for better AI reasoning. Button as RFC
sets the standard. Release definition creates clear target.
2026-07-02 08:58:29 +00:00
1e40d384ca
docs: Motion System v1 + Button gold standard + Component Template + Decision Tree
...
- Motion System v1 (chapter 5):
- Motion principles: when to animate, when NOT to animate
- Duration scale (instant to slower: 0ms to 500ms)
- Easing functions (linear, in, out, in-out, spring)
- Component-specific motion: Button, Modal, Drawer, Map, Skeleton,
Progress, Error/Success
- Reduced motion support (prefers-reduced-motion)
- Interruption rules (animations must be interruptible)
- Error/success animations (shake, checkmark, pulse)
- Button gold standard (chapter 8.3.1):
- Full specification: purpose, design goal, token dependencies,
layout, sizes, variants, states, keyboard, touch, accessibility,
anti-patterns, related components, DDR references
- Sets the bar for all future component specifications
- COMPONENT_TEMPLATE.md (v1.0, LOCKED):
- Standard template for all component specifications
- Sections: purpose, tokens, layout, sizes, variants, states,
keyboard, touch, accessibility, motion, acceptance criteria,
anti-patterns, related components, DDR references
- COMPONENT_DECISION_TREE.md (v1.0, LOCKED):
- Decision trees for: user actions, information display, user input,
feedback, navigation, Landvex-specific
- Quick reference table mapping needs to components
- Prevents invention of unnecessary components
Rationale: Motion before brand (affects every interaction). Button as
reference implementation. Template ensures consistency. Decision tree
guides AI agents and developers to correct component choice.
2026-07-02 08:53:20 +00:00
48236658e8
docs: Information-level typography + semantic colors + AI anti-patterns
...
- Typography v1 (chapter 3):
- Restructured from heading levels (H1-H6) to information levels
- Display, Section Title, Panel Title, Data Heading, Body, UI Label,
Metadata, Caption, Code/Numeric
- Each with: token, weight, usage, frequency
- Accessibility mapping to HTML heading elements
- Rationale: enterprise users scan for information, not headings
- Color System (chapter 4):
- Semantic Foundation: split into Neutral Semantic and Status Semantic
- Status tokens: success/warning/danger/info with surface/border/text
- Brand Palette rule: brand != status, never mix identity and meaning
- Map Layer Palette: restructured by layer (Base Surface, Terrain,
Water, Road Network, etc.)
- DESIGN_ANTI_PATTERNS.md:
- Restructured into 5 categories: visual, code, interaction, content,
AI-specific
- AI anti-patterns: AP-017 to AP-021 (inheritance check, hardcoded
values, token lifecycle, multiple icon libraries, document hierarchy)
- Total: 21 anti-patterns
Rationale: Function-based typography maps to mental models. Semantic
status colors prevent brand/status confusion. Layer-based map palette
enables theme swapping.
2026-07-02 08:49:28 +00:00
a412177512
docs: Component Architecture - Tiers, Inheritance, Minimalism
...
- Add Component Architecture (chapter 8):
- Tier 1 Canonical: Button, Input, Select, Card, Modal, Navigation,
Table, Data Grid, Search, Map Panel (10 components)
- Tier 2 Derived: Badge, Alert, Toast, Tooltip, Accordion, Tabs,
Breadcrumb, Pagination, Empty State, Skeleton (10 components)
- Tier 3 Domain: KPI Card, Map Overlay Panel, Layer Selector,
Mission Status, Dataset Card, Geospatial Inspector, Asset Summary,
Coordinate Picker, Timeline Panel (9 components)
- Component Inheritance: visual hierarchy showing parent-child
relationships (Button to Icon Button to Split Button, etc.)
- New Component Rule: 4-step checklist before creating anything new
- Principle: system shall be minimal, not maximal
- Restructure component numbering: 8.3.x for specifications
- Update table of contents with new structure
Rationale: Components before colors (component structure drives color
usage). Tiers prevent bloat. Inheritance prevents duplication.
Minimalism principle reduces complexity.
2026-07-02 08:46:07 +00:00
22be1efcd4
docs: Typography v1 + Foundation Colors + Anti-Patterns
...
- LANDVEX_DESIGN_SPECIFICATION.md:
- Typography v1 (chapter 3): Inter + JetBrains Mono, type scale,
heading hierarchy, line height rules, letter spacing, max line length,
tabular figures, numerical typography
- Foundation Colors (chapter 4.1): 12-step neutral palette (neutral-0 to neutral-1000)
- Semantic Colors (chapter 4.2): surface, text, border mappings
- Brand Palette (chapter 4.3): placeholder for brand colors
- Semantic Status Colors (chapter 4.4): green, yellow, red, blue
- Map Layer Palette (chapter 4.6): dedicated geospatial palette
- Updated primitive references from gray-* to neutral-*
- DESIGN_ANTI_PATTERNS.md (v1.0, LOCKED):
- 19 anti-patterns across 5 categories: visual, technical, interaction,
content, AI-specific
- Each with: forbidden description, rationale, alternative
- AI-specific rules: no hardcoded values, no invented components,
no skipping token lifecycle
Rationale: Typography before colors (harder to change). Neutral palette
before brand (90% of surface area). Anti-patterns prevent recurring
mistakes and guide AI agents.
2026-07-02 08:42:55 +00:00
16bc14cd32
docs: Token Philosophy v1.1 + Design Specification restructured
...
- TOKEN_PHILOSOPHY.md:
- Added Token Lifecycle (Draft → Experimental → Stable → Deprecated → Removed)
- Added Design Review Gate (6 mandatory checks before new token)
- Added deterministic principle: two AI agents must arrive at same token choice
- Restructured into 8 sections with clear hierarchy
- LANDVEX_DESIGN_SPECIFICATION.md:
- Restructured into 4 parts: GOVERNANCE → TOKENS → COMPONENTS → VALIDATION
- Added part headers and updated table of contents
- Aligned with Token Philosophy lifecycle and review gate
Rationale: Governance before values. Prevents uncontrolled token growth
and ensures AI-assisted design development is deterministic and traceable.
2026-07-02 08:37:50 +00:00
3afb583d71
docs: Token Philosophy + updated Design Specification
...
- Add docs/design/TOKEN_PHILOSOPHY.md (v1.0, LOCKED)
- Three-level token hierarchy: Primitive → Semantic → Component
- Semantic-first rule: no primitive references where semantic exists
- DTCG JSON as canonical export format
- Semantic versioning + deprecation policy
- Platform agnostic (web, iOS, Android, future)
- Update LANDVEX_DESIGN_SPECIFICATION.md
- Add Token Philosophy as chapter 0
- Restructure Design Tokens (chapter 1) with three levels
- Add blur scale, border width primitives
- Add semantic tokens (surface, text, border)
- Add component tokens (Button, Data Grid examples)
- Reference TOKEN_PHILOSOPHY.md for governance rules
Rationale: Establish token rules before values. Prevents rework
when components are specified later.
2026-07-02 08:34:48 +00:00
125ec6e4d2
docs: Document hierarchy + Design Specification skeleton
...
- Add DOCUMENT HIERARCHY (0d) to MEMORY.md
- 7 levels: SYSTEM > ENGINEERING > DESIGN > PRODUCT > SPEC > GUIDES > CODE
- Conflict resolution: higher document wins
- Add docs/design/LANDVEX_DESIGN_SPECIFICATION.md (v1.0-skeleton, DRAFT)
- 18 chapters with full structure
- Button component as reference spec (states, ARIA, keyboard, touch, animation, AC)
- All other chapters marked as TODO with placeholder tables
- Status: DRAFT — filled progressively, not all at once
Rationale: Establish governance first (Fas 1), fill specification
progressively (Fas 2), automated QA later (Fas 3).
2026-07-02 08:24:49 +00:00
f756b63fe2
docs: Landvex Design Constitution + quiXzoom UX Doctrine
...
- Add docs/design/LANDVEX_DESIGN_CONSTITUTION.md (v1.0, LOCKED)
- Enterprise UX Doctrine: 21 principles for professional GIS platform
- Device Adaptive (not Desktop First nor Mobile First)
- Add docs/products/quixzoom/QUIXZOOM_UX_DOCTRINE.md (v1.0, LOCKED)
- Field-first UX: Camera-First, Offline-First, Mission-First
- Mobile-Only, One Hand, Three Seconds
- Update MEMORY.md with DESIGN GOVERNANCE section (0c)
- References to both doctrines
- Shared DNA: components, tokens, colors, typography, motion, icons
- LOCKED status with version governance
2026-07-02 08:14:26 +00:00
bae705aa97
ARCHITECTURE: NFC roadmap, edge AI, audit logging
...
- Add NFC ePassport roadmap (ICAO 9303, eIDAS)
- Add TensorFlow.js edge face detection (BlazeFace)
- Add structured audit logger (GDPR-compliant)
- Risk scoring support
Part of KYC Apple Native UX v1.1.0
2026-06-29 16:24:48 +00:00
19d55c545e
Initial commit: aamos-ledger source + CLAUDE.md context
2026-06-17 06:34:57 +00:00
Bernt