Sharpen the site into a pre-commitment feasibility gate

[TonyQ7]

Phase 1 of PLAN.md. The visual identity is deliberately untouched — hero headline, survey plates, contour generator, palette, typography, grid, spacing and motion language are all unchanged. What changes is what the site claims to be.

The previous copy could be read as a beautiful workforce-analysis consultancy. It now sells one thing: a pre-commitment talent feasibility gate for a named business decision, with the wedge stated in the hero so a visitor can self-select out in one screen.

Narrative

• Hero — paid design-partner program, Sweden first; the decision the gate runs before; the wedge (10–25 critical roles, 1–3 Nordic locations, 90 days).
• One CTA name everywhere — "Discuss one workforce decision".
• The gate — "One workforce plan enters. A go, change, or stop decision leaves." Console relabelled illustrative decision logic; What the plate argues for → Decision implication.
• Decisions become triggers — when to run the gate, not questions to ponder.
• Pilot — unmistakably paid and founder-led. Price uncertainty replaced with Format. "Pre-product" replaced with design-partner stage.
• Positioning — "Where Capasight sits": a decision layer over four named inputs. The excluded-categories list moves to the FAQ rather than giving competitors the centre of the page.
• Footer — repository link removed; Stockholm provenance line.

Enforcement, not intention

Config is split so the verifier checks real typed records rather than regexing source: copy.ts, claims.ts and scenarios.ts are free of Astro env imports; site.ts alone resolves the booking URL.

The evidence gate gains three rules:

1. Illustrative scenarios may carry no counts at all — an "illustrative" label does not stop 18 roles reading as measurement. Durations ("three quarters") are allowed; counts are not. A record opts out only via dataClass: 'user-provided-sample', meaning the figures are the customer's own. Writing this rule caught two counts I had missed.
2. No claim exceeding reality — customers, partnerships, data rights, proof, ROI.
3. Placeholder booking URLs are rejected in production.

⚠️ The CTA is still a placeholder

The placeholder ban is suspended by an explicit, greppable ALLOW_PLACEHOLDER_BOOKING_URL. While it is set, the no production CTA is a placeholder test reports as skipped with its reason in every CI run rather than quietly passing. Enforcement is one deleted variable away.

This knowingly misses the plan's "No live link is a placeholder" Definition of Done, per an explicit decision to ship the narrative now.

Quality

93 Playwright tests pass on Chromium, Firefox and WebKit (3 skipped = the placeholder gate). Lint and astro check clean, no axe violations, no horizontal overflow at 360/768/1024/1440. On mobile the masthead gives up the wordmark's text rather than shortening the CTA, so the action keeps one name everywhere.

🤖 Generated with Claude Code