@@ -0,0 +1,93 @@
+---
+target: current landing page
+total_score: 34
+p0_count: 0
+p1_count: 3
+p2_count: 2
+timestamp: 2026-05-26T14-19-22Z
+slug: app-page-tsx
+---
+# Critique: app/page.tsx
+
+## Design Health Score
+
+| # | Heuristic | Score | Key Issue |
+|---|---|---|---|
+| 1 | Visibility of System Status | 3 | Invite-only state & roadmap shipped/upcoming both communicate well. Minor: open-source posture could be more visible above the fold. |
+| 2 | Match System / Real World | 3 | Internal taxonomy leaks in Core Features (Narrative Memory, Social Network, Jobs & Long Tasks). |
+| 3 | User Control and Freedom | 4 | N/A on landing. |
+| 4 | Consistency and Standards | 4 | Truly consistent, possibly over-consistent. |
+| 5 | Error Prevention | 4 | N/A. |
+| 6 | Recognition Rather Than Recall | 3 | Some scenario titles need light inference. |
+| 7 | Flexibility and Efficiency | 3 | Fast to skim. |
+| 8 | Aesthetic and Minimalist Design | 3 | Three consecutive identical card grids (Setup, Scenarios, Core Features). |
+| 9 | Error Recovery | 4 | N/A. |
+| 10 | Help and Documentation | 3 | On-page FAQ, docs link, footer surface. |
+| Total | | 34 / 40 | Good. |
+
+## Anti-Patterns Verdict
+
+LLM: avoids first-order AI-startup trap (no dark+neon+glass, no gradient hero); sits in the second-order editorial-typographic lane (5 of 6 fingerprint markers). Grandfathered as identity but worth knowing.
+
+Deterministic (manual fallback, bundled detector unavailable):
+- 16 em-dashes in user-facing copy (severe; DESIGN.md bans them).
+- backdrop-blur-sm in components/header.tsx (minor glassmorphism on sticky header).
+- 0 hits for: border-radius, bg-clip-text, box-shadow, side-stripe borders, gradient keyword.
+
+Browser visualization: not attempted (no browser MCP in this session).
+
+## Overall Impression
+
+Visual identity is coherent and committed. Page rhythm is flat: three identical card grids in a row makes the body of the page feel monotonous. Core Features uses internal module names where it should use scenarios. Final CTA reprints the hero.
+
+## What's Working
+
+1. Editorial discipline is intact and coherent across all sections.
+2. Roadmap is the strongest individual section (and the only non-card-grid one).
+3. Setup-in-3-steps lands the PDF brief exactly.
+
+## Priority Issues
+
+### [P1] Em-dashes everywhere (16 user-facing instances)
+DESIGN.md explicitly bans them. Easy global fix; high signal.
+Suggested command: clarify.
+
+### [P1] Three identical card grids in a row (Setup, Scenarios, Core Features)
+Triggers the "identical card grids" absolute ban. Visual monotony, eye gets no climax.
+Suggested command: layout, distill.
+
+### [P1] Core Features speaks product-internal taxonomy
+Violates PRODUCT.md principle "concrete over abstract." Mainstream non-technical visitors won't decode module names.
+Suggested command: clarify.
+
+### [P2] Final CTA duplicates the hero
+Wastes peak-end rule. Same 4 buttons, same invite line, similar copy.
+Suggested command: distill, clarify.
+
+### [P2] Linotype Blue is 0% of the homepage
+The secondary accent in DESIGN.md is unused on the homepage. Either embrace monochrome or find one earned moment.
+Suggested command: colorize.
+
+## Persona Red Flags
+
+Jordan (Confused First-Timer): stops at Narrative Memory; skips Social Network and Team Collaboration cards; recovers in FAQ.
+
+Casey (Distracted Mobile): 4 CTAs stack and consume ~60% of the first mobile fold; wall-of-buttons before any trust.
+
+Mainstream non-technical visitor: charmed by Scenarios, disengaged at Core Features (module names not features), saved by FAQ. Final CTA repeats hero, so the page does not feel like it landed.
+
+## Minor Observations
+
+- header.tsx backdrop-blur-sm is the only glassmorphism artifact. Either grant a documented "sticky-header exception" or remove it.
+- Core Features cards have no icons; Setup and Scenarios cards do. PDF asked for icons on most blocks.
+- "What you can put it to work on." is clunky as an h2.
+- All three primary fonts (Space Grotesk + Inter + DM Mono) appear on brand.md's reflex-reject list. Grandfathered as identity.
+- 72-pixel grid texture at 4% opacity is nearly invisible. Either commit or remove.
+
+## Questions to Consider
+
+- What if Core Features spoke in scenarios, not module names?
+- What if the Final CTA had one button, not four?
+- What if one section had real imagery (screenshot, loop)?
+- What if Linotype Blue appeared exactly once, earned?
+- What if Core Features and Scenarios traded positions, so the page goes concrete, concrete, concrete, roadmap?