docs(reed): voice rewrite + README gateway + legacy deprecation

gt-va002, gt-va004 / convoy-032

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: auge2u

CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to Platform4Sync will be documented in this file.
 
 This project adheres to [Semantic Versioning](https://semver.org/).
 
+## [0.5.1] - 2026-02-22
+
+### Voice Alignment (convoy-032)
+
+- **gt-va002: Command voice rewrite** — applied voice guidelines across all command files:
+  - `ha.md`: Reframed cultural tokens as the baseline (Shu level), not a Ha deviation. Ha is choosing which culture and whether to deviate from a pre-built identity. Updated from 10 to 12 curated identities with full list. Added `ha:domain` section for T1 partner domain routing decisions.
+  - `finish.md`: Updated from 10 to 12 curated identities with full list. Reframed to "integrate your chosen identity" instead of "build a token system."
+  - `shu.md`: Replaced "scaffold a new project" with "adopt the platform structure." Reframed language around adoption of proven patterns rather than creation.
+  - `site.md`: Replaced "scaffold a new project" with "initialize your project to the platform structure."
+- **gt-va004: README gateway rewrite** — replaced essay-style README with gateway format: one-line description, install block, three bullet points (12 identities, multi-tenant isolation, graduated auth), docs link, and anti-positioning line.
+- **gt-va004: Legacy deprecation cleanup** — added `(DEPRECATED)` to title of all 9 legacy `wp4s*` commands. Forwarding notices to frame equivalents already present and verified correct.
+
 ## [0.5.0] - 2026-02-22
 
 ### Security Hardening

README.md

@@ -1,13 +1,15 @@
 # Platform4Sync
 
-Platform standards, skills, and scaffold templates for building multi-tenant SaaS applications on Cloudflare Workers + Neon PostgreSQL.
-
-## Install as Claude Code Marketplace
-
-Add to your project's `.claude/settings.json`:
+Production multi-tenant infrastructure for Claude Code. Greenfield or brownfield.
 
 ```json
 {
+  "permissions": {
+    "allow": ["WebFetch"],
+    "deny": []
+  },
+  "mcpServers": {},
+  "customInstructions": "",
   "extraKnownMarketplaces": {
     "webplatform4sync": {
       "source": {
@@ -19,37 +21,13 @@ Add to your project's `.claude/settings.json`:
 }
 ```
 
-## What's Inside
-
-- **Skills** — Claude Code skills for multi-tenant architecture, graduated auth, Neon isolation, and design tokens
-- **Scaffolds** — Project templates for greenfield, brownfield, and overlay adoption
-- **Contracts** — Shared type definitions ensuring cross-skill compatibility
-- **Validators** — Token and tenant configuration validators
-
-## Documentation
-
-- [What is Platform4Sync?](docs/what-is-platform4sync.md) — Overview and technical architecture
-- [Architecture Rationale](docs/rationale.md) — Design decisions and review history
-- [Contributing](docs/contributing.md) — How to add skills and templates
-
-## Skills
-
-Each skill has a `skill.md` entry point. Point Claude Code at the skill directory and describe your task:
-
-| Skill | Purpose |
-|-------|---------|
-| `skills/multi-tenant-platform/` | 3-tier tenant architecture (Platform/Partner/Customer) |
-| `skills/graduated-auth/` | Anonymous → Preview → OAuth → Full Account |
-| `skills/neon-multi-tenant/` | Neon branches, Hyperdrive, Drizzle ORM |
-| `skills/theme-inspired-tokens/` | Culturally-grounded design tokens (W3C DTCG) |
+- **12 cultural identities** — Swiss International, Nihon Traditional, Nordic Modern, Tang Imperial, Shuimo Modern, Nihon Minimal, Renaissance, Art Deco, Wiener Werkstaette, Milanese Design, De Stijl, Swiss Modernist
+- **Multi-tenant isolation** — 3-tier architecture (Platform / Partner / Customer) with RLS, Neon PostgreSQL, and Drizzle ORM
+- **Graduated auth** — Anonymous to Preview to OAuth to Full Account, with Better Auth sessions and Firebase identity
 
-## Scaffolds
+[Documentation](https://docs.syncupsuite.com)
 
-| Template | When to Use |
-|----------|-------------|
-| `scaffold/greenfield/` | New project from scratch |
-| `scaffold/brownfield/` | Migrating existing project to standards |
-| `scaffold/overlay/` | Adding design token system only |
+Not a template. The same patterns shipping in brandsyncup.com and legalsyncup.com.
 
 ## License
 

commands/finish.md

@@ -48,7 +48,7 @@ If no subcommand, present this menu grouped by concern.
 | Subcommand | What it does |
 |-----------|-------------|
 | `tokens` | Culturally-grounded design token system — DTCG JSON + Tailwind 4 output + React artifact |
-| `theme` | Full theme: token system + identity picker (10 curated designs) + live preview |
+| `theme` | Full theme: identity picker (12 curated identities) + live preview |
 | `ui` | Web components and pages requiring distinctive visual design |
 
 ### Accessibility
@@ -99,10 +99,12 @@ If no subcommand, present this menu grouped by concern.
 ## Key decisions at this stage
 
 **Design identity selection**
-> *"Ten curated identities are available — Swiss International, Nihon Traditional,
-> Nordic Modern, and seven others. Admin picks one; it propagates to all tenant
-> instances. This is the Mac wallpaper model: you commit to an identity, not
-> to arbitrary tokens. Run `finish:theme` to preview before committing."*
+> *"Twelve curated identities are available — Swiss International, Nihon
+> Traditional, Nordic Modern, Tang Imperial, Shuimo Modern, Nihon Minimal,
+> Renaissance, Art Deco, Wiener Werkstaette, Milanese Design, De Stijl,
+> and Swiss Modernist. Admin picks one; it propagates to all tenant instances.
+> This is the Mac wallpaper model: you integrate your chosen identity, not
+> arbitrary tokens. Run `finish:theme` to preview before committing."*
 
 **Accessibility scope**
 > *"WCAG 2.2 Level AA is the minimum. Level AAA for public-facing forms.

commands/ha.md

@@ -55,7 +55,7 @@ If no subcommand, present this menu grouped by concern.
 | Subcommand | What it does |
 |-----------|-------------|
 | `tokens` | Culturally-grounded design token system — every color, font, and spacing has a source |
-| `theme` | Full theme: token system + identity picker (10 curated designs) + live preview |
+| `theme` | Full theme: identity picker (12 curated identities) + live preview |
 
 ---
 
@@ -106,17 +106,28 @@ happen implicitly inside a tool invocation.
 > permanently. Name your spectrum before building the scaffold."*
 
 `ha:tokens`
-> *"The token system traces every design decision to a cultural or aesthetic source.
-> 'This blue is Hanada blue from Japanese indigo dyeing' — not 'I liked this hex.'
-> What is the cultural frame for this product? That question is the starting point,
-> not the color picker."*
+> *"Cultural tokens are the baseline — every identity in the system traces its
+> colors, typography, and spacing to a documented cultural source. That is Shu.
+> The Ha decision is which culture to adopt, and whether to deviate from one
+> of the 12 pre-built identities. You are not choosing whether to use cultural
+> theming. You are choosing which cultural foundation fits your product."*
 
 `ha:theme`
-> *"Ten curated identities are available. You pick one; it propagates everywhere.
+> *"Twelve curated identities are available: Swiss International, Nihon
+> Traditional, Nordic Modern, Tang Imperial, Shuimo Modern, Nihon Minimal,
+> Renaissance, Art Deco, Wiener Werkstaette, Milanese Design, De Stijl,
+> and Swiss Modernist. You pick one; it propagates everywhere.
 > This is the Mac wallpaper model — not a color scheme, an identity. Swiss
 > International carries precision and neutrality. Nihon Traditional carries
 > restraint and depth. Which one fits the product's voice?"*
 
+`ha:domain`
+> *"Does each T1 partner resolve to one domain or many? Primary, alias, vanity —
+> this is a Ha decision. The standard model assumes one canonical domain per
+> partner. If your partners need vanity domains or locale-specific subdomains,
+> name the routing model before implementing. Domain mapping shapes tenant
+> resolution and SSL provisioning."*
+
 ---
 
 ## Document the deviation

commands/shu.md

@@ -35,7 +35,7 @@ If no subcommand, present this menu and ask which to run.
 | `envrc` | Create or update `.envrc` with standardized environment config (auto-detects stack) |
 | `tune` | Analyze and optimize Claude Code configuration for this project's stack |
 | `clean` | Find and safely remove space-wasting artifacts from repos |
-| `scaffold` | Scaffold a new project — greenfield (new), brownfield (existing), or overlay (tokens only) |
+| `scaffold` | Adopt the platform structure — greenfield (new), brownfield (existing), or overlay (tokens only) |
 
 **Recommended order**: `scaffold` or `init` first, then `envrc`, then `tune`.
 
@@ -56,17 +56,17 @@ If no subcommand, present this menu and ask which to run.
 ## How to run a Shu command
 
 Do not ask for customizations at the Shu stage. The purpose of Shu is to
-establish the standard pattern first, then diverge in Ha with understanding.
+adopt the proven pattern first, then diverge in Ha with understanding.
 
 If the user requests customization during a Shu command:
 
 > *"That customization makes sense — note it down and we will apply it when
-> we reach Ha on this concern. For now, let the standard scaffold establish
-> the baseline so you have something concrete to deviate from."*
+> we reach Ha on this concern. For now, adopt the platform standard to
+> establish the baseline so you have something concrete to deviate from."*
 
 If the user resists and insists on customizing now, proceed — but name it:
 
-> *"We are jumping to Ha on [concern] before the standard is established.
+> *"We are jumping to Ha on [concern] before the standard is adopted.
 > That is a valid choice if you already know why the standard does not fit.
 > Let us document the reason so the deviation is intentional, not accidental."*
 

commands/site.md

@@ -31,7 +31,7 @@ If no subcommand, present this menu and ask which to run.
 | `envrc` | Create or update `.envrc` with standardized environment config (auto-detects stack) |
 | `tune` | Analyze and optimize Claude Code configuration for this project's stack |
 | `clear` | Find and safely remove space-wasting artifacts from repos |
-| `scaffold` | Scaffold a new project — greenfield (new), brownfield (existing), or overlay (tokens only) |
+| `scaffold` | Initialize your project to the platform structure — greenfield (new), brownfield (existing), or overlay (tokens only) |
 
 ---
 

commands/wp4s1_discover.md

@@ -5,7 +5,7 @@
 
 ---
 
-# wp4s1_discover
+# wp4s1_discover (DEPRECATED)
 
 > Step 1 of 9 — Scan project against the Platform4Sync standard
 > Previous: none | Next: `wp4s2_scaffold`

commands/wp4s2_scaffold.md

@@ -5,7 +5,7 @@
 
 ---
 
-# wp4s2_scaffold
+# wp4s2_scaffold (DEPRECATED)
 
 > Step 2 of 9 — Generate project structure
 > Previous: `wp4s1_discover` | Next: `wp4s3_tenant`

commands/wp4s3_tenant.md

@@ -5,7 +5,7 @@
 
 ---
 
-# wp4s3_tenant
+# wp4s3_tenant (DEPRECATED)
 
 > Step 3 of 9 — Set up 3-tier tenant model
 > Previous: `wp4s2_scaffold` | Next: `wp4s4_database`

commands/wp4s4_database.md

@@ -5,7 +5,7 @@
 
 ---
 
-# wp4s4_database
+# wp4s4_database (DEPRECATED)
 
 > Step 4 of 9 — Configure Neon database with tenant-scoped queries
 > Previous: `wp4s3_tenant` | Next: `wp4s5_auth`