chati-dev 4.3.0 → 4.4.0

package/framework/constitution.md

@@ -332,10 +332,10 @@ The pipeline operates in three execution modes that control agent permissions. M
 
 7. Token budgets per bracket (Progressive Reinforcement Model — as context degrades, reinforcement increases):
    - Budgets are expressed as a percentage of the actively detected context window
-   - FRESH: 1.5% of context window (Claude 200K: 3000, Opus 1M: 15000, Codex: 1920)
-   - MODERATE: 2.5% of context window (Claude 200K: 5000, Opus 1M: 25000, Codex: 3200)
-   - DEPLETED: 4.0% of context window (Claude 200K: 8000, Opus 1M: 40000, Codex: 5120)
-   - CRITICAL: 5.0% of context window (Claude 200K: 10000, Opus 1M: 50000, Codex: 6400)
+   - FRESH: 1.5% of context window (Claude 1M: 3000, Opus 1M: 15000, Codex: 1920)
+   - MODERATE: 2.5% of context window (Claude 1M: 5000, Opus 1M: 25000, Codex: 3200)
+   - DEPLETED: 4.0% of context window (Claude 1M: 8000, Opus 1M: 40000, Codex: 5120)
+   - CRITICAL: 5.0% of context window (Claude 1M: 10000, Opus 1M: 50000, Codex: 6400)
 
 8. Autonomous spawn capability varies by IDE:
    - Full autonomy: Claude Code, AntiGravity, Gemini CLI
@@ -411,13 +411,13 @@ The pipeline operates in three execution modes that control agent permissions. M
 
 Once the orchestrator is activated via `/chati`, a session lock engages. All agents and the orchestrator itself are bound by these rules:
 
-1. **Lock is mandatory**: When a session is active (session.yaml has project.name and current_agent), the session lock MUST be ACTIVE. CLAUDE.md MUST contain the Session Lock block.
+1. **Lock is mandatory**: When a session is active (session.yaml has project.name and current_agent), the session lock MUST be ACTIVE. `CLAUDE.local.md` (the local, non-committed sibling of `CLAUDE.md`) MUST contain the Session Lock block. The lock state lives in `CLAUDE.local.md` — NOT `CLAUDE.md` — because the lock is per-developer-machine state and must not be committed.
 2. **All messages routed**: Every user message MUST be routed through the orchestrator and then to the active agent. No message may be answered outside of the Chati.dev system while the lock is active.
 3. **No generic responses**: The AI MUST NOT respond as a generic assistant while the lock is active. It IS the Chati.dev orchestrator. Off-topic requests are handled via the Deviation Protocol (5.7), not by dropping out of the system.
 4. **Explicit exit only**: The session lock is released ONLY by explicit user intent via recognized exit commands (`/chati exit`, `/chati stop`, `/chati quit`) or clear natural language exit requests in the user's language.
-5. **Exit preserves state**: On exit, all session state, progress, and partial work MUST be persisted. The session lock status in CLAUDE.md is set to INACTIVE. The user can resume anytime with `/chati`.
-6. **Resume re-locks**: When `/chati` is invoked after a previous exit, the session lock is immediately re-activated and CLAUDE.md is updated with the active lock block.
-7. **IDE restart resilience**: If the IDE is closed/restarted, the session lock status in CLAUDE.md persists. On the next `/chati` invocation, the orchestrator detects the existing session and re-engages the lock.
+5. **Exit preserves state**: On exit, all session state, progress, and partial work MUST be persisted. The session lock status in `CLAUDE.local.md` is set to INACTIVE. The user can resume anytime with `/chati`.
+6. **Resume re-locks**: When `/chati` is invoked after a previous exit, the session lock is immediately re-activated and `CLAUDE.local.md` is updated with the active lock block.
+7. **IDE restart resilience**: If the IDE is closed/restarted, the session lock status in `CLAUDE.local.md` persists. On the next `/chati` invocation, the orchestrator detects the existing session and re-engages the lock.
 
 **Enforcement: BLOCK** — Responses outside the Chati.dev system while session lock is active are violations.
 
@@ -481,11 +481,11 @@ The system SHALL support two execution modes that govern the degree of human inv
    - **brief**: Requirements extraction requires human validation
    - **orchestrator (deviation protocol)**: Deviations from the plan always need human approval
 
-5. **Terminology Note:** "Autonomous" in this article controls WHO evaluates gates (system vs human). Article XVIII's "autonomous" profile controls WHETHER confirmation is required for writes. Both must be satisfied for fully autonomous operation: this article's mode active AND Article XVIII cumulative gate score >= 95%.
+5. **Terminology Note:** "Autonomous" in this article controls WHO evaluates gates (system vs human). The sole prerequisite for fully autonomous operation is this article's autonomous mode being active with the relevant QA gate score >= 95%.
 
 6. Safety net triggers SHALL pause autonomous execution when dangerous conditions are detected: consecutive failures, circular approaches, resource limits, or destructive operations.
 
-7. Circuit breaker pattern: After 3 consecutive gate failures at the same pipeline point, the system SHALL pause and escalate to human review regardless of mode.
+7. Loop protection: the pipeline manager tracks consecutive correction cycles for each reviewer-to-rework-target pair. Once the correction-cycle limit at the same pipeline point is exceeded (default: 2 cycles, so the third consecutive failure), the system SHALL stop the correction loop and escalate to human review regardless of mode.
 
 8. Mode transitions are logged in session.yaml under `mode_transitions[]` for audit trail.
 
@@ -836,7 +836,54 @@ Tiers reset to each agent's DEFAULT at task start. Exception: if the current ses
 
 ---
 
-*Chati.dev Constitution v4.3.0 — 23 Articles + Preamble*
+## Article XXIV: Model-Harness Parity
+
+Every component of this framework encodes an assumption about what the active model cannot do on its own. Those assumptions go stale as models improve, so the harness is re-examined when the model family changes.
+
+### 1. Trigger
+When `session.active_model` differs from `session.model_at_last_audit` at the start of a session, the harness may no longer be calibrated for the active model.
+
+### 2. Advisory, not a block
+On that mismatch the orchestrator SHALL surface an advisory recommending `/chati-update`. The advisory never blocks pipeline work, which preserves the guided, low-friction experience.
+
+### 3. Clearing the advisory
+A successful `/chati-update` run SHALL record `session.model_at_last_audit = session.active_model`, which clears the advisory (the active model now matches the audited one). The first run (`model_at_last_audit: null`) does not advise; it only seeds the baseline.
+
+### 4. Audit scope
+A model-change audit re-checks the parts of the harness whose calibration is model-dependent: context bracket token budgets (Article XII), agent confidence calibration, and which scaffolding agents are still load-bearing versus removable for the new model. Governance rules (the Articles, the gates, the registry) are model-agnostic and are kept.
+
+**Enforcement: GUIDE** (advisory only). The orchestrator surfaces the recommendation; it does not gate the pipeline on it.
+
+---
+
+## Article XXV: Execution Kinds
+
+A task is the unit of work; how it executes is a separate, declared property. Most work needs a model, but some development tasks are fully deterministic, and spending an agent turn on them adds cost, latency, and nondeterminism for no benefit.
+
+### 1. The four kinds
+Every task carries an `execution_kind`: `agent` (default), `script`, `specialist`, or `human`. Omitting the field means `agent`, so the kind is fully back-compatible: a plan written without it behaves exactly as before.
+- `agent` - an LLM agent implements the task. The default, and the path for anything needing implementation, design, or judgment.
+- `script` - a deterministic executor runs the task with no model call (lint, tests, build verification, file or schema checks).
+- `specialist` - an agent carrying a fixed embedded methodology. Reserved; today it resolves to `agent`.
+- `human` - a decision a person must own (irreversible, legal, financial, or product judgment). Presented as a Guided Option; never automated.
+
+### 2. Feature-flagged and inert by default
+Script execution is gated by the `execution_kinds` feature flag, off by default. While off, every task runs as `agent` and the pipeline is identical to one with no execution kinds at all. The capability is opt-in.
+
+### 3. Registered executors only
+A `script` task names an executor from the executor registry (`chati.dev/executors/registry.yaml`) through its `execution_ref`. An executor is a standalone, deterministic program under a fixed JSON contract (request on stdin, result on stdout); it never calls a model and never runs an unbounded or arbitrary command. Inventing an executor id, or pointing a script task at anything outside the registry, is a violation.
+
+### 4. Verdict semantics
+An executor returns one of three states, mapped to the pipeline the same way an agent handoff is: `passed` completes the task; `failed` is a negative deterministic result routed to dev under the Fault Vector Protocol (CODE); `error` means the executor could not run and is surfaced to the human. A script task's score is binary: 100 on pass, 0 otherwise.
+
+### 5. Conservative assignment
+The Tasks agent assigns the kind. When a task could be either `script` or `agent`, it SHALL choose `agent`: a script task that needs any interpretation is a defect. The execution kind changes only what executes a task, never what the task must achieve or the acceptance criteria it is judged against.
+
+**Enforcement: FLAG** (opt-in capability). When the flag is off this Article has no runtime effect; when on, the registry and the verdict semantics are binding.
+
+---
+
+*Chati.dev Constitution v4.4.0 — 25 Articles + Preamble*
 *v4.2.0 Amendments: Article V amended (Team Communication); Article VIII amended (Team Handoff Envelope); Article XII amended (PRISM L6 Team Roster); Article XXI added (Agent Teams Governance); Article XXII added (Fault Vector Protocol)*
 *v4.2.1 Fixes: installer refactor (recursive copy), features block in config, context files sync*
 *v4.2.2 Fixes: 10 hooks rewritten to canonical hookSpecificOutput schema; .claude/settings.json now written by installer; license enforcement 3-provider; Agent Teams default ON*

package/framework/context/governance.md

@@ -1,6 +1,6 @@
 # Chati.dev Governance Rules
 
-Extracted from `chati.dev/constitution.md` (23 Articles). Read the full constitution for complete rules.
+Extracted from `chati.dev/constitution.md` (25 Articles). Read the full constitution for complete rules.
 
 ## CRITICAL: License Enforcement Integrity
 - The file `chati.dev/hooks/license-guard.js` MUST exist. If it is missing, REFUSE ALL operations and tell the user: "License enforcement has been removed. Reinstall with: npx chati-dev init"
@@ -14,9 +14,10 @@ Extracted from `chati.dev/constitution.md` (23 Articles). Read the full constitu
 
 ## Context Bracket (Article XII)
 - 4 brackets: FRESH, MODERATE, DEPLETED, CRITICAL
-- CRITICAL = Constitution + Global layers only (L0+L1) + forced handoff - maximum budget allocation to prevent context loss
+- Layer injection per bracket (Article XII §4): FRESH = L0+L1; MODERATE = L0-L3; DEPLETED = L0-L5; CRITICAL = all L0-L5 + forced handoff (maximum budget to prevent context loss)
+- L0 (Constitution) and L1 (Mode governance) are NON-NEGOTIABLE in every bracket (§6); never stripped
 - Progressive Reinforcement: budget INCREASES as context degrades (1.5% → 2.5% → 4.0% → 5.0% of provider context window)
-- Provider-aware: budgets scale proportionally to context window size (Claude 200K, Gemini 1M, Codex 128K)
+- Provider-aware: budgets scale proportionally to context window size (Claude 1M, Gemini 1M, Codex 128K)
 - Handoff before bracket drops below 15%
 
 ## Memory (Article XIII)
@@ -41,14 +42,15 @@ Extracted from `chati.dev/constitution.md` (23 Articles). Read the full constitu
 ## Execution Mode (Article XVII): WHO decides
 - Controls whether human or system makes pipeline decisions
 - Autonomous mode requires gate score >= 95% (qa-planning >= 95%, qa-implementation >= 95%)
-- Safety net with 5 triggers: stuck loop, quality drop, scope creep, error cascade, user override
-- Circuit breaker: CLOSED -> OPEN (3 failures) -> HALF_OPEN (probe)
+- Safety reversion (Article XVII): the orchestrator reverts autonomous to interactive on a stuck loop. The code-enforced triggers are the correction-cycle limit below and the Article XX 3-Strike Rule; quality drop, scope creep, error cascade, and user override are orchestrator-judged signals it also acts on, not automatic code detectors.
+- Loop protection: consecutive correction cycles per reviewer/rework-target pair; escalate to human once the limit (default 2) is exceeded
+- Git authority: while a pipeline is active, only the devops agent may push to a remote or open a pull request (`git-push-authority` hook, PreToolUse Bash); other agents are denied with a clear message. Outside an active pipeline, git is unaffected.
+- Surface criteria: even in autonomous mode, a high-stakes transition (deploy is external and irreversible) requires a human nod before proceeding; passing the quality gates alone does not auto-confirm it. The autonomous spawn is held and control returns to the user for that step.
 
-## Execution Profile Governance (Article XVIII): HOW actions execute
-- 3 profiles: explore (read-only), guided (default), autonomous (gate >= 95%)
-- Transition to autonomous requires QA-Planning >= 95% AND QA-Implementation >= 95%
-- Safety net: 5 triggers revert to guided (stuck loop, quality drop, scope creep, error cascade, user override)
-- Circuit breaker: CLOSED -> OPEN (3 failures) -> HALF_OPEN (probe)
+## Execution Profile Governance (Article XVIII): DEPRECATED
+- DEPRECATED: collapsed into Article XVII (Execution Mode). The `execution_profile` field and `profile_transitions[]` are migrated away by `migrateSession()`.
+- Historical mapping (read-only, applied automatically by migration): explore/guided -> interactive; autonomous -> autonomous.
+- New code SHALL use `execution_mode` only (interactive | autonomous). Do NOT add new references to `execution_profile`.
 
 ## Multi-CLI Governance (Article XIX)
 - 3 providers: Claude, Gemini, Codex

package/framework/context/root.md

@@ -1,9 +1,9 @@
 # Chati.dev System Context
 
 ## Framework
-- **Version**: 4.3.0
+- **Version**: 4.4.0
 - **Agents**: Specialized agents across DISCOVER, PLAN, BUILD, DEPLOY phases
-- **Constitution**: 23 Articles + Preamble
+- **Constitution**: 25 Articles + Preamble
 - **Quality**: 5 pipeline gates + 3-tier verdicts + Fault Vector Protocol (Article XXII)
 - **Agent Teams**: Native Claude Code teams with peer communication (Article XXI, default ON for Claude provider)
 

package/framework/data/entity-registry.yaml

@@ -3,9 +3,9 @@
 # and by the Health Check for system integrity validation.
 
 metadata:
-  version: "4.3.0"
-  last_updated: "2026-04-14T00:00:00Z"
-  entity_count: 100
+  version: "4.4.0"
+  last_updated: "2026-05-18T00:00:00Z"
+  entity_count: 109
   checksum_algorithm: sha256
 
 entities:
@@ -313,7 +313,7 @@ entities:
     constitution:
       path: chati.dev/constitution.md
       type: governance
-      purpose: "23 Articles + Preamble governing all agent behavior"
+      purpose: "25 Articles + Preamble governing all agent behavior"
       keywords: [constitution, governance, rules, articles, enforcement]
       dependencies: []
       adaptability: 0.1
@@ -673,6 +673,14 @@ entities:
       dependencies: [motion-premium, ux-brand-architect]
       adaptability: 0.4
 
+    saas-dashboard:
+      path: chati.dev/scaffold/saas-dashboard/scaffold.yaml
+      type: scaffold
+      purpose: "Premium SaaS dashboard and app-shell preset: sidebar nav, top bar, sortable data tables, KPI stat cards, a self-contained SVG chart, accessible forms, and a Cmd+K command palette. 30 templates, calibrated dark palette, fully token-driven, WCAG AA. App-shell category, distinct from the motion showcase presets."
+      keywords: [scaffold, premium, saas, dashboard, app-shell, data-table, command-palette, chart, accessibility, phase-10]
+      dependencies: [ux-brand-architect]
+      adaptability: 0.4
+
   context:
     context-governance:
       path: chati.dev/context/governance.md

package/framework/data/qa-rubrics.yaml

@@ -0,0 +1,335 @@
+# QA Rubrics - single source of truth for gate thresholds and scoring criteria.
+#
+# Why this file exists: the pass thresholds (95 / 90 / 85) used to live as
+# literals in advance-trigger.js, the quality-gate docs, the QA agent files and
+# the constitution at the same time, with nothing keeping them in sync. They now
+# live here, in exactly one place. advance-trigger.js reads the threshold at
+# runtime; the QA agents and gate docs reference this file as canonical.
+#
+# Treat the rubric like a tuned parameter, not prose: changing a threshold or a
+# dimension weight changes the quality of the output, so every change bumps
+# rubric_version and adds a changelog entry. No agent may edit this file or its
+# own threshold during a run.
+
+rubric_version: "1.2.0"
+
+changelog:
+  - version: "1.0.0"
+    date: "2026-06-07"
+    change: "Initial extraction. Establishes the canonical gate thresholds as a single source of truth."
+  - version: "1.1.0"
+    date: "2026-06-08"
+    change: "Add the 8-dimension QA-Visual scoring rubric (weights, premium/slop markers, measurable + judged signals), the weak-dimension cap, and the anti-slop catalog."
+
+# Minimum score (percent) an agent must reach to clear its gate.
+thresholds:
+  qa-planning: 95
+  qa-implementation: 95
+  qa-visual: 90
+  standard: 90
+  discovery: 85
+
+# Scores within this many points below the threshold trigger a human-review
+# band even in autonomous mode (the gate does not auto-pass on a near miss).
+review_band: 5
+
+# ---------------------------------------------------------------------------
+# QA-Visual scoring rubric (8 dimensions). This is the canonical quality bar
+# the QA-Visual agent scores generated UIs against, and the contract the UX
+# agents design toward. Weights sum to 1.0. Each dimension carries premium
+# markers, slop markers (the generic-template tells), measurable signals (what
+# visual-qa.js can detect) and judged signals (what the agent eyeballs).
+# ---------------------------------------------------------------------------
+visual_rubric:
+  applies_to: qa-visual
+  scoring_protocol: |-
+    Application protocol for the QA-Visual agent scoring against this rubric:
+
+    SCORING ORDER: Score dimensions in this sequence: accessibility first (it has the hardest cap), then interaction, then layout, then motion, then typography, then color, then spacing_composition, then performance. Apply dimension caps before computing the weighted total. If accessibility scores below 60, apply the hard cap of 70 immediately and surface it as a BLOCKED finding before computing any other dimension.
+
+    EVIDENCE STANDARD: Every JUDGED signal that produces a finding below the premium band requires a screenshot reference cited by filename. Every MEASURABLE signal finding requires the computed value that triggered the flag. Findings without evidence are downgraded from ERROR to SUGGESTION and treated as non-blocking per the Fault Vector Protocol (Article XXII).
+
+    ANTI-SLOP CATALOG USAGE: Scan the anti-slop catalog before opening screenshots. Each catalog entry that matches the output applies a -3 to -8 point penalty against the most relevant dimension score (not the overall score directly). Document which catalog entries fired and which dimension absorbed the penalty. An output that triggers 4 or more catalog entries in the same dimension automatically scores that dimension at or below 55, triggering the weak dimension cap.
+
+    GATEWAY WEAK MODE: When Playwright is unavailable and the agent operates in WEAK gateway mode, all MEASURABLE signals are assessed from source code analysis only. JUDGED signals from screenshots are marked as CANNOT-ASSESS. The overall score is capped at 84 in WEAK mode, preventing a fallback-only verdict from clearing the 90 APPROVED threshold. Surface gateway: WEAK prominently in the report header.
+
+    WEIGHTED TOTAL FORMULA: overall_score = sum(dimension_score times dimension_weight) across all 8 dimensions, after individual dimension caps are applied, after anti-slop catalog penalties are absorbed into dimension scores, and after the weak_dimension_cap is evaluated. Do not round intermediate values; round the final overall score to the nearest integer.
+
+    CORRECTION LOOP ROUTING: When a dimension scores below its threshold, route the correction to the appropriate fault layer per Article XXII. Layout, spacing, and typography failures route to the UX-Brand-Architect for spec revision or to Dev for implementation correction. Motion and interaction failures route to Dev. Accessibility failures route to Dev with explicit WCAG violation citations. Color failures route to Dev if token references are wrong, or to UX-Brand-Architect if the palette itself needs redesign. Performance failures route to Dev.
+
+    EM-DASH ENFORCEMENT: The framework bans em dashes in all visible text. If visual-qa.js reports em_dashes_found=true, apply a -5 point penalty to the typography dimension score and raise a VISUAL-ERROR regardless of other dimension scores. This is non-negotiable per the constitution.
+
+    DIMENSION WEIGHT RATIONALE (for auditors): layout (0.18) and typography (0.15) carry the highest weights because they govern the gestalt impression formed in the first 50 to 200 milliseconds of viewing, before any interaction occurs. Motion (0.14) and interaction (0.14) share the second tier because motion is a multiplier on every other dimension and interaction quality is entirely under the generator's control with no external asset dependency. Color (0.13) is weighted below motion because a strong spatial and typographic foundation partially compensates for a mediocre palette, whereas the reverse is less true. Spacing/composition (0.11) is weighted below layout because it largely overlaps with layout discipline and its marginal contribution is captured there. Accessibility (0.10) is weighted conservatively because its primary governance instrument is the hard cap (not the weighted score): a failing accessibility score triggers the most severe overall cap (70), making its weight multiplier secondary to its gate function. Performance (0.05) carries the lowest weight because slow but structurally sound UIs can be corrected in a targeted loop and their defects are less immediately visible in static screenshots than the other dimensions.
+  weak_dimension_cap:
+    threshold: 60
+    cap: 74
+    accessibility_override:
+      threshold: 60
+      cap: 70
+    rule: "If any single dimension scores below 60, the overall QA-Visual score is capped at 74 regardless of other dimension scores. A score of 74 guarantees the output cannot reach the 90 APPROVED threshold on the strength of other dimensions alone, forcing a targeted correction loop. The threshold is set at 60 (not 70) to permit outputs that have a genuine weakness in one area but are strong everywhere else to still score in the high 80s, while ensuring catastrophically broken dimensions (broken interaction states, inaccessible DOM, complete motion failure) block approval. The accessibility dimension has an additional hard override: if accessibility scores below 60, the overall cap is further tightened to 70, because inaccessible UIs are structurally incomplete products, not polish gaps, per the framework constitution. MOTION ABSENCE EXEMPTION: when the resolved animation stack is none or css (a deliberately static or CSS-only design), the motion dimension is scored at a 70 baseline as CANNOT-ASSESS rather than from measured failures, its premium signals (choreography, stagger, cubic-bezier vocabulary) are excluded, and this weak-dimension cap is NOT applied on the strength of the motion dimension alone. A static site with no animation is a valid design choice, not a broken dimension."
+  dimensions:
+    - key: layout
+      title: Layout, Grid, Hierarchy, and Whitespace Rhythm
+      weight: 0.18
+      premium:
+        - "A single, coherent spatial system governs all margins, gaps, and padding: every distance is a recognizable multiple of a base unit (4px or 8px), with no arbitrary pixel values outside the system."
+        - Visual hierarchy is established through deliberate variation in size, weight, and position; the eye moves through the page in a predictable, intentional sequence without relying on borders, shadows, or decorative dividers as the primary separators.
+        - "Whitespace is deployed asymmetrically and purposefully: generous breathing room around primary content, tighter grouping between related elements, creating clear gestalt clusters without explicit containers."
+        - Sections have distinct spatial personalities (dense, airy, full-bleed, inset) that alternate to sustain attention and reflect content importance, rather than repeating a single section template at uniform height.
+        - At least one element intentionally breaks the primary content container width (a full-bleed image, an offset composition, an asymmetric grid span), signaling deliberate art direction rather than template reuse.
+        - "Above-the-fold layout communicates a clear information priority within 2 seconds: one undisputed primary message, one secondary message, one action, with no competing focal points at equal visual weight."
+      slop:
+        - Equal padding applied uniformly to every section (e.g., 80px top and bottom everywhere), producing a flat, metronomic rhythm with no spatial drama or variation.
+        - Every section shares the same container max-width with no breaks, bleeds, or offsets, creating a claustrophobic tube-like layout that signals template reuse.
+        - "Hero section is simply a centered title plus subtitle plus button with perfect bilateral symmetry and no compositional interest: indistinguishable from the default output of any AI generation tool."
+        - Cards forced to identical heights via CSS regardless of content length, or arranged in a 3-column grid with no column-span variation, producing artificial mechanical uniformity.
+        - Decorative horizontal rules or gradient divider lines used to separate sections instead of whitespace, revealing that the spacing system was not trusted.
+        - Spacing values that are multiples of 10 or 5 but do not form a coherent scale (e.g., 10px, 25px, 60px, 100px mixed), exposing ad-hoc placement rather than a defined system.
+        - Content stacked in a single center-aligned column with wide empty margins throughout the entire page, never using the full canvas for visual interest or composition.
+        - Z-axis depth (shadows, elevation) applied at identical intensity to every card, button, and container, erasing hierarchy rather than supporting it.
+      measurable:
+        - "Spacing system consistency: extract all computed margin, padding, and gap values across major layout elements; at least 85% of values must be multiples of 4px or 8px; flag any value not in a recognized scale."
+        - "Section height variance: compute the pixel heights of all top-level sections; the coefficient of variation must exceed 0.25, confirming sections differ meaningfully in vertical footprint rather than repeating a template height."
+        - "Max-width breaks: detect whether any element has a wider computed width than the primary content container; at least one element should exceed the main container width to signal intentional layout composition."
+        - "Grid column utilization: for each CSS Grid or Flexbox row, measure how many columns are spanned by each child; flag layouts where every sibling spans exactly the same column count with no exceptions across the entire page."
+        - "Above-fold element count: count interactive elements (buttons, links with role=button, inputs) visible in the 1440x900 viewport without scrolling; optimal range is 1 to 3; more than 5 is flagged as hierarchy failure."
+        - "Spacing uniqueness ratio: count distinct spacing values used in computed styles across all block-level elements; fewer than 6 unique values for a full-page layout signals an over-rigid system; more than 20 signals no system at all."
+      judged:
+        - Does the page feel composed or assembled? A composed layout has sections that feel like deliberate choices in relation to each other; an assembled layout feels like sections were dropped in sequence without reference to the whole.
+        - Is there a clear reading path? Identify the primary focal point, the secondary focal point, and the tertiary, then judge whether a naive viewer would follow that same path naturally.
+        - Does whitespace feel earned or accidental? Generous gaps that frame content correctly feel intentional; identical gaps that appear everywhere feel like a default margin was never overridden.
+        - Does any section break the expected pattern in a way that increases quality? A full-bleed image or asymmetric composition that works signals craft; a pattern break that creates visual noise signals slop.
+        - Does the layout work at a squint? Blur judgment to see only masses of light and dark; a premium layout has a clear tonal map with dominant, secondary, and accent zones; a slop layout is a uniform grey field.
+    - key: typography
+      title: Type Scale, Hierarchy, Rhythm, and Expressiveness
+      weight: 0.15
+      premium:
+        - "A modular type scale is in use: font sizes follow a consistent ratio (1.25, 1.333, or 1.5) rather than being arbitrary round numbers; every heading and body size maps to a named step in the scale with no orphan sizes."
+        - Display headings use tighter tracking (negative letter-spacing) at large sizes, reflecting the optical reality that large glyphs require less inter-character space; body text uses neutral or slightly positive tracking appropriate to its size.
+        - "Line-height is differentiated by role: display headings use 1.0 to 1.2, subheadings 1.2 to 1.4, body text 1.5 to 1.7, captions 1.4 to 1.6; a single line-height value applied globally is a direct fail signal."
+        - Line measure for sustained reading text falls between 55 and 75 characters; the layout constrains column widths to enforce this rather than allowing text to span full-width on large viewports.
+        - "Weight contrast between heading and body levels is substantive: the ratio of font-weight values between the heaviest heading and the lightest body level spans at least 2 steps (e.g., 700 vs 400), not a single-step nudge."
+        - "Paragraph spacing is proportional to line-height: typically 0.75 to 1.25 times the line-height value, creating paragraph rhythm that breathes without creating disconnected islands of text."
+      slop:
+        - Font sizes defined in a round-number sequence (12, 14, 16, 20, 24, 32, 48px) with no underlying ratio, revealing sizes were chosen by convention rather than a system.
+        - A single font-family used for all roles with differentiation achieved only through size and weight, producing a visually flat typographic palette.
+        - Body text set in a container wider than 80 characters at the primary breakpoint, forcing the reader's eye to travel a fatiguing horizontal distance per line.
+        - Uniform line-height of 1.5 applied to all text elements from display headings to captions, signaling the default was accepted without typographic consideration.
+        - Large display headings with positive or zero letter-spacing, producing a loose, airy appearance at display size that reads as unfinished or template-generated.
+        - Heading hierarchy that relies on color (a lighter grey versus a darker grey) rather than size and weight, producing a hierarchy that collapses when color is removed.
+        - Font size differences between adjacent heading levels smaller than 4px at any breakpoint, creating a hierarchy that is technically present but visually imperceptible.
+      measurable:
+        - "Scale ratio detection: extract all distinct computed font-size values in px; compute pairwise ratios between consecutive sizes when sorted; at least 70% of adjacent-step ratios must fall within 0.05 of a common ratio (1.25, 1.333, 1.414, or 1.5); flag if no consistent ratio is detectable."
+        - "Letter-spacing audit: for each element with font-size >= 32px, assert computed letter-spacing is negative (less than -0.01em); for elements with font-size < 18px, assert letter-spacing is >= 0em; flag inversions."
+        - "Line-height by role: query computed line-height for h1 and h2 elements (assert 1.0 to 1.25 times font-size); p elements (assert 1.5 to 1.75); small and caption elements (assert 1.3 to 1.6); flag any role outside its range."
+        - "Measure constraint: for each p or article element containing more than 20 words, measure computed width and divide by approximate character width (font-size times 0.5); flag if character count per line exceeds 80 or falls below 45."
+        - "Weight contrast ratio: extract all distinct font-weight values used on the page; assert the range (max minus min) is at least 300 weight units; flag if all weights fall within a 200-unit band."
+        - "Body text size floor: assert no p or li element containing more than 10 words has a computed font-size below 15px on 1440px viewport or below 14px on 375px viewport."
+      judged:
+        - Does the type feel purposefully selected or defaulted into? Assess whether any font pairing creates meaningful contrast in personality, weight, and optical size, or reads as a system default left in place.
+        - Does the heading hierarchy communicate priority without requiring the viewer to read the words? Can the structural outline of the page be inferred from typographic treatment alone in under 5 seconds of scanning?
+        - Is the body text comfortable to read for a sustained paragraph? Judge tracking, leading, measure, and size holistically, not as isolated metrics.
+        - Does the type scale create visual music when the page is viewed as a whole? A premium type system produces a felt cadence of large, medium, small, large, medium as the viewer scrolls; a slop system produces a monotone band interrupted by arbitrarily large headings.
+        - Are there any runts (single short words on a final line of a heading) or widows (single line of a paragraph at the top of a column) visible at any of the three tested breakpoints?
+    - key: motion
+      title: "Motion Quality: Easing, Duration Discipline, and Choreography"
+      weight: 0.14
+      premium:
+        - "Every UI transition uses a cubic-bezier curve appropriate to its physical metaphor: elements entering use a deceleration curve, elements leaving use an acceleration curve, and elements repositioning in place use a symmetric curve; keyword values without cubic-bezier overrides are treated as a fail signal."
+        - "Duration follows a strict scale tied to element size and distance: micro-interactions (hover color, focus ring) use 80 to 150ms; component state changes (drawer open, modal appear) use 200 to 350ms; page-level transitions do not exceed 500ms."
+        - Choreographed sequences stagger child element entrances by a fixed interval (30 to 60ms per item) so the eye follows a reading-order path rather than seeing everything appear simultaneously.
+        - Scroll-triggered animations use an intersection threshold of 0.15 to 0.25, so elements begin animating when meaningfully visible, not at the pixel they enter the viewport or after the user has already scrolled past them.
+        - "The prefers-reduced-motion media query is honored at the CSS layer: all transitions and animations inside the reduced-motion block collapse to instant or to opacity-only fades at 150ms maximum."
+        - Transform and opacity are the only animated properties in the critical path; no animation touches layout-triggering properties (width, height, top, left, margin, padding) except in explicitly justified cases with will-change declared.
+      slop:
+        - "transition: all 0.3s ease applied at a wildcard or component-root level, causing every property change to animate and producing jank on layout changes."
+        - All transitions use the keyword ease or linear with no cubic-bezier customization, producing a uniform, mechanical feel across every interaction regardless of physical metaphor.
+        - "Duration is identical across all elements regardless of size or importance: micro-interactions and full-page modals both animate at 300ms with the same curve."
+        - Scroll animations trigger at threshold 0 (fires before the user scrolls, animation is complete on arrival) or at threshold 1.0 (never fires on tall elements), breaking the natural reveal pattern.
+        - "No prefers-reduced-motion handling exists: users who have requested reduced motion receive the full animation suite including parallax, auto-playing sequences, and staggered entrances."
+        - "Animation choreography is absent: all elements in a list, card grid, or navigation enter simultaneously with no stagger, creating a visual flash rather than a guided sequence."
+        - "will-change: transform declared on every animated element globally rather than applied and removed dynamically, consuming GPU memory and causing compositing layer explosion on large DOMs."
+      measurable:
+        - "Cubic-bezier audit: query all computed transition-timing-function values across interactive and animated elements; assert fewer than 20% use the keyword values ease, linear, ease-in, or ease-out without a corresponding cubic-bezier override; flag if the proportion exceeds 20%."
+        - "Duration scale check: extract all transition-duration and animation-duration values; assert micro-interaction elements have duration <= 150ms and no page-level transition exceeds 500ms; flag outliers."
+        - "transition:all detection: search all stylesheets for transition: all or transition-property: all; flag every occurrence as a blocking finding."
+        - "Reduced-motion compliance: emulate prefers-reduced-motion:reduce; assert all transition-duration values collapse to <= 150ms or animation-play-state becomes paused for non-opacity animations; fail if any transform animation persists above 150ms."
+        - "Layout property animation detection: scan all @keyframes and transition-property declarations for width, height, top, left, right, bottom, margin, or padding; flag any found unless will-change is also declared on the same selector."
+        - "Stagger detection in lists: for repeated sibling elements with animation-delay or transition-delay, assert delay increments by 20 to 80ms per sibling; flag if all siblings share identical delay."
+      judged:
+        - "Screen recording or frame-by-frame screenshot of a modal or drawer open animation: the motion curve must be visibly decelerating (fast start, soft landing), not linear or symmetrical."
+        - "Staggered list entrance playback: items must enter in reading order with a perceptible but not distracting delay between each, guiding the eye rather than overwhelming it."
+        - "Scroll-reveal timing observation: elements should begin their reveal animation when roughly one quarter of the element is visible, not at the viewport edge and not after full visibility."
+        - "Reduced-motion mode screenshot: the interface must remain fully functional and visually complete with no missing states or broken layouts caused by stripped animations."
+        - "Overall motion coherence: playing through all interactive transitions in sequence, the motion vocabulary must feel unified, as if all animations were designed to the same physical ruleset rather than assembled from separate snippets."
+        - "No transition jank observation: rapid interaction (clicking buttons quickly, scrolling aggressively, toggling states) must not produce stuck intermediate animation states, flicker, or layout shift visible in the screenshot."
+    - key: interaction
+      title: "Interaction Quality: Affordances, States, and Feedback"
+      weight: 0.14
+      premium:
+        - "Every interactive element has four visually distinct states: resting, hover, active/pressed, and disabled; each state is immediately recognizable without needing to interact multiple times to notice the change."
+        - Hover transitions shift exactly one perceptible property (background, border, shadow, or transform) rather than several simultaneously, so the eye tracks a single clear signal.
+        - Focus rings use a high-contrast outline offset from the element boundary, with at least 3px offset and 2px ring width, so keyboard-navigating users receive the same spatial clarity as pointer users.
+        - Active/pressed states apply a subtle downward transform (translateY 1 to 2px) or shadow compression to simulate physical depression, giving tactile feedback through the screen.
+        - Form inputs display a colored left-border or underline accent on focus that matches the primary color token, distinguishing focused fields from adjacent text without relying only on the browser default outline.
+        - "Cursor changes are semantically correct throughout: pointer on clickable elements, text on editable content, grab/grabbing on draggable regions, zoom-in on expandable media."
+      slop:
+        - Hover state is identical to resting state or only changes opacity to 0.8, giving no spatial or color signal that the element is interactive.
+        - Focus ring is the raw browser default outline with no offset, appearing cropped by border-radius or overflow:hidden, causing it to disappear on rounded elements.
+        - "Active state is missing entirely: pressing a button produces no visual compression or color shift, so the click feels unconfirmed."
+        - Disabled inputs retain full opacity and no cursor change, making them visually identical to enabled inputs.
+        - "All interactive elements share one generic :hover { opacity: 0.7 } rule applied via a wildcard selector, producing a flat, undifferentiated interaction layer."
+        - Form validation errors appear only as red border-color changes with no text explanation, failing users who cannot distinguish the color shift.
+        - Focus states exist on some elements but are absent or suppressed on custom-styled components (dropdowns, toggles, sliders), creating an inconsistent keyboard navigation experience.
+      measurable:
+        - "Computed style check: every element with role=button or tag=a must have a :hover rule that changes at least one property from the set {background-color, color, box-shadow, transform, border-color}; flag any that change none."
+        - "Focus ring audit: query all focusable elements via Tab key sequence; for each, confirm outline-width >= 2px and outline-offset >= 2px; fail if either is 0px or if outline-style is none and no box-shadow focus substitute exists."
+        - "Active state presence: Playwright mousedown (without mouseup) on each primary button; assert computed background-color or transform differs from hover state; flag if identical."
+        - "Disabled opacity range: query all [disabled] or [aria-disabled=true] elements; assert computed opacity is between 0.35 and 0.55; flag values outside this range."
+        - "Cursor correctness: for all anchor and button elements, assert computed cursor === pointer; for all [disabled] elements, assert computed cursor === not-allowed."
+        - "Form error completeness: trigger validation on empty required fields; assert presence of role=alert or aria-live region AND visible helper text element AND color change on the input border; flag if only one signal is present."
+        - "State count coverage: for each unique interactive component type detected (button, input, select, checkbox, toggle), assert at least 3 of 4 states (resting, hover, focus, active) produce a distinct computed style snapshot."
+      judged:
+        - "Screenshot comparison of resting vs hover states for the primary call-to-action: the change must be perceptible within 200ms and feel deliberate, not accidental."
+        - "Keyboard navigation walkthrough screenshot sequence: focus ring must be visible on every focused element without clipping, color inversion, or disappearance."
+        - Pressed/active button screenshot must show visible compression (shadow reduction or downward shift) that communicates a physical response.
+        - "Error state screenshot: the affected field must communicate failure through at least two independent visual channels simultaneously visible in the screenshot."
+        - "Overall interaction layer coherence: hover states across all interactive element types should feel like they belong to the same visual language, not a collection of ad-hoc overrides."
+    - key: color
+      title: "Color: Palette Discipline and Semantic Token Integrity"
+      weight: 0.13
+      premium:
+        - "Palette built from a documented semantic layer: every color value traces to a named intent token with no raw hex literals scattered across component styles."
+        - Neutral scale spans at least 9 steps with perceptually even luminance intervals; the darkest and lightest neutrals are used for body text and page background respectively, not arbitrary stops.
+        - Accent color is used in at most two distinct UI roles (e.g., primary action plus highlight mark), never as decoration or fill on non-interactive surfaces.
+        - Dark and light modes share the same semantic tokens but remap to different primitive values; swapping the color scheme does not produce jarring hue or saturation shifts because the mapping was designed for both contexts simultaneously.
+        - Gradients, when present, are constructed from two adjacent stops on the same hue axis or two complementary hues no more than 60 degrees apart on the wheel, producing smooth transitions without muddy midpoints or neon banding.
+        - Inter-surface contrast is calibrated so layered backgrounds (page, card, popover) step in consistent luminance increments of at least 8 points on a 0 to 100 scale, creating clear visual depth without resorting to heavy borders.
+      slop:
+        - Raw hex literals appear inline in component styles or hardcoded in class strings, bypassing the token layer entirely.
+        - Primary brand color is an unmodified saturated blue that could belong to any productivity software product with no differentiation from the category default.
+        - Gradients span more than 90 degrees of hue rotation (rainbow effect) or include a pure white or pure black stop that creates an abrupt lightness cliff at one end.
+        - "Dark mode implemented by inverting lightness universally (filter: invert or brightness flips) rather than remapping semantic tokens to dark-appropriate primitives."
+        - Accent color appears on decorative backgrounds, section dividers, icon containers, and interactive buttons simultaneously, destroying its signaling function.
+        - Semantic colors (success, warning, error) are missing entirely or mapped directly to default browser green, yellow, and red without any palette adaptation.
+        - Color choices change arbitrarily between sections with no shared token source, producing an incoherent patchwork rather than a unified palette.
+      measurable:
+        - "Count CSS custom properties whose names begin with --color-: a premium output declares at least 20 semantic color tokens; fewer than 12 is a fail signal."
+        - Scan all computed background-color and color values on rendered elements; if more than 15% of unique color values do not correspond to a declared CSS custom property, flag raw-hex proliferation.
+        - For every visible text node, compute contrast ratio against its background using the WCAG relative luminance formula; zero violations below 4.5:1 (body text) and 3:1 (large text) required for APPROVED.
+        - Count distinct hue families (grouped within 30-degree arcs) in the top-20 most-used color values; a premium palette uses 1 to 3 hue families; more than 5 families signals palette sprawl.
+        - "In dark mode (prefers-color-scheme: dark), re-compute element color values and compare to light-mode values; if more than 30% of semantic token computations are identical (no remapping), flag missing dark-mode token mapping."
+        - "Count the number of UI roles where the accent token appears: buttons, links, decorative fills, icon containers, section backgrounds; more than 3 distinct role types flags accent overuse."
+      judged:
+        - Does the palette read as intentional and industry-appropriate, or does it feel like a default color scheme pulled from a utility CSS framework example page?
+        - Is there a clear visual hierarchy between page background, surface, raised surface, and overlay layers, or does everything feel flat at the same luminance level?
+        - Do gradients feel refined and directional, or garish and decorative? A premium gradient is almost invisible at first glance and reveals itself on close inspection.
+        - Does the dark mode feel like it was designed for darkness, with warm or cool-tinted neutrals that feel restful, or does it look like a crude inversion with harsh pure-black backgrounds?
+        - Is the accent color used with restraint so that interactive elements immediately pop, or is it sprinkled everywhere so it stops drawing the eye?
+    - key: spacing_composition
+      title: "Spacing and Composition: Scale Consistency, Density, and Optical Harmony"
+      weight: 0.11
+      premium:
+        - All spacing values resolve to a declared scale with a consistent base unit (4px or 8px); no arbitrary pixel values appear in margin, padding, or gap properties outside of single-pixel border offsets.
+        - "Section vertical rhythm follows a geometric or rational progression: consecutive sections alternate between at least two distinct vertical padding tiers (e.g., compact: 64px, standard: 96px, generous: 144px) rather than every section having the same padding."
+        - "Negative space is used deliberately: hero sections and feature callouts have substantially more breathing room than content-dense sections, creating intentional pacing as the user scrolls."
+        - The ratio between the densest and most spacious sections on the same page is at least 2:1, creating genuine rhythm without either feeling cramped or wastefully empty.
+        - Component-level spacing uses component-specific tokens that reference the base scale, so components maintain internal proportion across different viewport sizes.
+        - Max content width is constrained to prevent line lengths from becoming unreadable on ultra-wide viewports, with full-bleed moments clearly marked as intentional art direction rather than absent containment.
+      slop:
+        - Section padding is a single uniform value on every section, producing a monotonous drumbeat with no rhythm variation between sections of different visual weight.
+        - Spacing values include arbitrary pixel offsets (23px, 37px, 15px) that do not correspond to any declared scale, indicating properties were tuned by eye or left at browser defaults.
+        - The gap between a heading and its descriptive paragraph is identical to the gap between two sibling sections, collapsing the hierarchy of proximity and making it unclear which elements belong together.
+        - Cards and list items have inconsistent internal padding with no token governing the value, revealing ad-hoc construction.
+        - On mobile, padding is simply halved from desktop values rather than reconsidered for the viewport, causing either cramped content or excessive vertical scroll before substance.
+        - "Empty sections or placeholder areas appear with no deliberate negative space purpose: white space exists because content is missing, not because it was composed."
+      measurable:
+        - Extract all computed padding and margin values from section-level elements; bucket into declared-scale values vs off-scale values; a premium output has at least 90% of spacing values matching scale stops; below 75% is a fail signal.
+        - Identify maximum and minimum vertical padding values on top-level sections; compute the ratio (max divided by min); a ratio below 1.5 flags rhythm monotony; a ratio above 4 may flag inconsistency.
+        - Compute the computed width of the primary content container as a percentage of the viewport width at 1280px; values above 95% flag full-bleed content layouts lacking column constraint.
+        - For every card component detected (elements with a computed background-color different from the page background and a computed border-radius greater than 0), extract internal padding values; if the standard deviation of padding-top values across all cards exceeds 8px, flag inconsistent card density.
+        - At 375px viewport width, extract the smallest computed horizontal padding on any full-width content block; values below 16px flag edge-to-edge content collision.
+        - Count unique spacing values (margin, padding, gap) that do not resolve to a CSS custom property; more than 8 unique off-token values is a fail signal.
+      judged:
+        - Does scrolling through the page feel like moving through a composed sequence of sections with intentional breathing, or does it feel like a stack of identically spaced cards with no pacing?
+        - "Does the hierarchy of proximity work: are related elements visually grouped, and is the space between groups larger than the space within them?"
+        - On mobile, does the layout feel deliberately reconfigured for a narrow viewport, or does it feel like a shrunk-down desktop layout that happens to fit?
+        - "Does the page have a sense of visual weight distribution: heavy moments balanced by lighter moments, dense sections contrasting with generous ones?"
+    - key: accessibility
+      title: "Accessibility: Structural Integrity and Inclusive Interaction"
+      weight: 0.1
+      premium:
+        - Every interactive element is reachable by Tab in a logical, document-order sequence that matches the visual reading flow; no focus traps outside modal dialogs; no skip-link omissions on pages with repeated navigation blocks.
+        - "All text meets WCAG 2.1 AA contrast at rendered size: body text >= 4.5:1 against its computed background; large text (>= 18pt or >= 14pt bold) >= 3:1; UI component boundaries and input borders >= 3:1 against adjacent surface."
+        - "Semantic HTML is load-bearing, not decorative: headings form a strict h1-h2-h3 hierarchy (no skipped levels); landmark regions (main, nav, aside, footer) partition the page so a screen reader can jump between areas without scanning all content."
+        - Every form input has a programmatically associated label; required fields are marked with both aria-required=true and a visible indicator that does not rely on color alone; validation errors are linked to their input via aria-describedby and announced to screen readers on submission.
+        - "All animations and transitions respect prefers-reduced-motion: a CSS block exists, disables or replaces every keyframe animation and transition above 200ms, and the effect is verified by both computed styles and screenshot under the reduced-motion flag."
+        - Touch and pointer target sizes meet or exceed 44x44 CSS pixels for all interactive elements; elements that appear smaller visually achieve the target size via padding, so the hit area is large without breaking the layout.
+      slop:
+        - "Placeholder text used as the only label for inputs: the label disappears on focus, leaving the user with no visible reminder of what the field expects."
+        - "Focus ring removed globally with outline: none or :focus { outline: none } in a reset stylesheet, with no replacement indicator; keyboard users lose all positional tracking."
+        - "Heading hierarchy that mirrors visual size rather than document structure: multiple h1 elements per page, h3 used because it renders at the desired font size, headings skipped from h2 to h4 to push a section down visually."
+        - "Color used as the sole differentiator for state: error fields bordered in red with no icon or text label, required fields marked only with a red asterisk whose meaning is never explained."
+        - prefers-reduced-motion block present in CSS but covering only one or two animations while leaving parallax, entrance keyframes, and scroll-triggered motion unaffected; the block exists to pass a lint check, not to protect users.
+        - "Interactive elements below 32x32 CSS pixels with no padding compensation: icon-only buttons, social links, and checkbox labels that fail touch targeting on mobile."
+        - Click handlers on divs without tabindex=0, role=button, and keyboard event handlers for Enter and Space; modal dialogs that do not trap focus, so Tab escapes into the obscured background.
+      measurable:
+        - "Contrast audit via computed styles: flag any text element where the luminance ratio is < 4.5:1 for font-size < 18.67px or < 3:1 for font-size >= 18.67px; zero violations required for APPROVED."
+        - "Focus order audit: programmatically Tab through all focusable elements; assert DOM order matches visual top-to-bottom, left-to-right order; count out-of-order occurrences; threshold: 0 inversions."
+        - "Heading hierarchy integrity: query all h1-h6 elements in DOM order; assert exactly one h1 per page; assert no level jump greater than 1 (e.g., h2 directly followed by h4); threshold: 0 violations."
+        - "Landmark coverage: assert presence of exactly one main element; assert at least one nav element; assert footer exists; assert no content-bearing text nodes are direct children of body; threshold: 0 missing landmarks."
+        - "prefers-reduced-motion coverage: simulate the preference; assert no element has a computed animation-duration > 0.2s or transition-duration > 0.2s after simulation; threshold: 0 uncovered animations."
+        - "Touch target size audit: for every interactive element at 375px viewport, read getBoundingClientRect(); assert width >= 44 and height >= 44; threshold: 0 failures on mobile viewport."
+        - "Form label association: for every input and textarea not of type hidden or submit, assert a label with matching for attribute OR aria-label OR aria-labelledby pointing to a visible element; threshold: 0 unassociated inputs."
+      judged:
+        - "Screenshot under keyboard navigation simulation: is a visible, high-contrast focus ring present on each interactive element as it receives focus? Does the ring surround the element cleanly without clipping?"
+        - "Mobile screenshot (375px viewport): do all buttons, links, and form controls appear large enough to tap comfortably? Do adjacent interactive targets crowd each other below approximately 8px spacing?"
+        - "Screenshot with forced prefers-reduced-motion: does the page look intentionally designed in its reduced-motion state, or does it look broken with elements frozen mid-animation or empty sections where animated content was expected?"
+        - "Error state screenshot on a form with invalid input: is the error communicated through at least two distinct visual channels beyond color (e.g., icon plus text message, border plus inline label)?"
+        - "Color-blindness simulation screenshot (deuteranopia filter applied): do all state distinctions (active/inactive, error/success, selected/unselected) remain distinguishable without relying on hue alone?"
+    - key: performance
+      title: "Performance: Perceptual Speed and Rendering Stability"
+      weight: 0.05
+      premium:
+        - "No measurable layout shift during page load or user interaction: CLS measured via PerformanceObserver is <= 0.05 on first load; images reserve space via explicit width and height attributes or aspect-ratio CSS before image bytes arrive."
+        - "Animations exclusively target compositor-promoted properties: every animated property in keyframe blocks and transition declarations is transform or opacity; no animation touches width, height, top, left, margin, or padding."
+        - "Scroll performance is stable at 60 frames per second: no long tasks (> 50ms) recorded in the main thread during a 3-second programmatic scroll from top to bottom; no forced synchronous layouts triggered by scroll handlers."
+        - "Web fonts load without invisible or jarring text flash: font-display is set to optional or swap with a system fallback stack whose metrics closely match the loaded font; no FOIT lasting > 3000ms."
+        - "The critical rendering path is not blocked by synchronous scripts or render-blocking stylesheets: no script tags without defer or async appear in head before the closing tag except for inline critical CSS."
+        - Largest Contentful Paint is <= 2500ms on a simulated mid-tier connection; the LCP element is identified and its fetch is either inlined, preloaded, or server-pushed.
+      slop:
+        - "Layout shift from unresized images: img elements without width and height attributes or a CSS aspect-ratio on a container, causing the page to reflow as each image loads; a CLS score above 0.1 on the first load even when the network is fast."
+        - "Animations that trigger layout: CSS transitions on width, height, or max-height to animate open/close of drawers or accordions instead of using transform: scaleY() or clip-path transitions."
+        - "All images served at their intrinsic resolution regardless of rendered size: a 4000px wide source image displayed at 400px CSS width with no srcset or picture element, downloading 10x the necessary pixels."
+        - "Font loading with font-display: block (the browser default when the property is absent): text is invisible for up to 3 seconds while the font loads, then swaps in abruptly."
+        - "Render-blocking scripts in head without defer or async: third-party analytics or chat widgets inserted as synchronous script src before the page content, stalling first paint."
+        - "Unbounded stagger delays: a list of 20 cards each staggered 200ms apart means the last card does not animate in until 4 seconds after the section enters the viewport, making the page feel slow and neglected."
+      measurable:
+        - "Cumulative Layout Shift: inject a PerformanceObserver for layout-shift entries during page load and for 5 seconds after; threshold for APPROVED: CLS <= 0.05; threshold for WARNING: 0.05 < CLS <= 0.1; threshold for ERROR: CLS > 0.1."
+        - "Largest Contentful Paint: record last entry's startTime after page stabilizes; threshold for APPROVED: LCP <= 2500ms on an unthrottled local server; flag for WARNING if LCP element is an image without a preload hint."
+        - "Animated property audit: query document.getAnimations() after page load; flag any property that is not transform, opacity, filter, or a will-change-promoted custom property; threshold: 0 layout-triggering animated properties."
+        - "Long task detection during scroll: inject a PerformanceObserver for longtask entries; programmatically scroll the page from top to bottom over 3 seconds; count long tasks (duration > 50ms); threshold: 0 for APPROVED, >= 3 for ERROR."
+        - "Image sizing discipline: for each img element, compare naturalWidth against getBoundingClientRect() width multiplied by window.devicePixelRatio; flag images where intrinsicWidth > renderedCSSWidth times devicePixelRatio times 2.2; threshold: 0 on hero images."
+        - "Font-display policy: query all @font-face rules via document.styleSheets; flag each rule with fontDisplay === block or empty string; threshold: 0 block-display font rules."
+        - "Script load discipline: query all script elements in head with a src attribute; assert each has either defer, async, or type=module; count synchronous blocking scripts; threshold: 0 blocking scripts before first contentful paint."
+      judged:
+        - "Slow-network simulation screenshot sequence: do images load progressively (blur-up or skeleton placeholder visible first) or do they pop in all at once after a blank space, or does the layout shift dramatically as each image arrives?"
+        - "Scroll experience judgment at normal user speed: do entrance animations trigger smoothly at the expected moment (just as content enters the viewport) or do they fire while elements are still off-screen or only after the user has already scrolled past?"
+        - "Font rendering judgment across the load sequence: in a filmstrip of screenshots taken at 200ms intervals from navigation start, is there a visible FOIT (blank text) period longer than 300ms, or a jarring metric shift when the web font replaces the fallback?"
+        - "Above-the-fold judgment on a simulated mid-tier device: is the primary content visible and readable within the first 2.5 seconds of the filmstrip, or is the viewport blank or skeleton-only for a noticeably long period?"
+  anti_slop_catalog:
+    - "Generic saturated blue as the primary brand color with no evidence of deliberate palette selection: the hue communicates no industry affiliation, personality, or differentiation from the default output of any AI generation tool."
+    - Every section padded identically top and bottom (most commonly 80px or 5rem), producing a metronomic vertical rhythm with no spatial drama, no dense sections, no generous sections, no alternation of any kind.
+    - "Centered hero layout with title, subtitle, and a single primary button, perfectly bilaterally symmetric, with no typographic size contrast between title and subtitle, no compositional interest, no art direction: the single most common AI-generation fingerprint."
+    - "transition: all applied at a component root or wildcard selector level, visible in the stylesheet as a single rule covering the entire element: guarantees jank on any class toggle and signals the author did not reason about which properties to animate."
+    - "All CSS transitions using the keyword ease or linear with no cubic-bezier customization: every hover, every modal open, every drawer, every reveal uses the same mechanical timing curve with no physical metaphor."
+    - "Three-column card grid where every card has forced equal height via CSS, every card has the same internal padding, and the cards are the same width with no spans or offsets: the grid reads as a spreadsheet, not a composition."
+    - "Font sizes chosen as round integers (12, 14, 16, 20, 24, 32, 48, 64px) with no underlying ratio connecting them: sizes were chosen by convention or by copying an existing scale, not derived from a modular system."
+    - "outline: none or :focus { outline: none } present in a global reset or base stylesheet with no replacement focus indicator anywhere on the page: keyboard users are completely invisible from the moment focus moves."
+    - Heading hierarchy that skips levels (h1 to h3, h2 to h4) or uses multiple h1 elements per page because heading tags were chosen for their default visual size rather than document structure.
+    - "All list items, all cards, and all navigation items entering the viewport simultaneously with no stagger, no sequencing, no choreography: elements flash in as a single visual event rather than guiding the eye."
+    - Placeholder text used as the sole accessible label for form inputs, disappearing on focus and leaving the user with no visible reminder of the field's purpose.
+    - "Hardcoded hex values scattered across component CSS or className strings, bypassing a token layer entirely: the palette cannot be coherently updated because colors are not referenced symbolically."
+    - Decorative horizontal rules, gradient separator lines, or thick border dividers between every section, substituting for a spacing system that the author did not trust.
+    - All images served at their intrinsic (source) resolution regardless of their rendered size, with no srcset, no picture element, and no width/height attributes causing cumulative layout shift on load.
+    - "Dark mode implemented by applying filter: invert or a CSS variable swap that simply flips lightness values universally, producing washed-out colors, incorrect saturation, and harsh pure-black backgrounds instead of a designed dark palette."

package/framework/domains/constitution.yaml

@@ -1,5 +1,5 @@
 # Constitution Domain — Extracted governance rules for PRISM L0
-# Source: chati.dev/constitution.md (23 Articles + Preamble)
+# Source: chati.dev/constitution.md (25 Articles + Preamble)
 
 summary: >
   Constitution governance: self-validation required (loop until tier-specific threshold met),
@@ -9,7 +9,7 @@ summary: >
   context brackets, memory governance, registry governance,
   session lock, model governance.
 
-articleCount: 22
+articleCount: 25
 
 rules:
   - id: art-i
@@ -77,7 +77,7 @@ rules:
     priority: high
 
   - id: art-xvii
-    text: "Execution mode governance: QA gates >= 95%, other agents >= 90%. Safety net with circuit breaker (3 failures)."
+    text: "Execution mode governance: QA gates >= 95%, other agents >= 90%. Safety net escalates to human once the correction-cycle limit is exceeded at the same gate."
     priority: critical
 
 articles: