prochattools · stevewesthoek · Sep 29, 2026 · Sep 28, 2026 · Sep 29, 2026 · Sep 29, 2026
diff --git a/PRODUCT.md b/PRODUCT.md
@@ -23,9 +23,9 @@ Mastermind — separate free, open-source planning/orchestration product
 
 ## Public website contract
 
-Canonical routes are `/`, `/evermind`, `/nevermind`, `/mastermind`, `/docs`, `/contact`, `/privacy`, and `/terms`. This cinematic visual contract applies to the first four routes only. The remaining public routes retain their existing page-specific presentation and legal substance; do not redesign them as part of the cinematic release.
+Canonical routes are `/`, `/evermind`, `/nevermind`, `/mastermind`, `/docs`, `/contact`, `/privacy`, and `/terms`. The first four routes use one shared, scroll-driven cinematic template with one full-width navigation, two narrative sections, an intentional 80vh transition spacer, Golos Text display headings, and no footer. The utility routes `/docs`, `/contact`, `/privacy`, and `/terms` use the quieter static cinematic utility shell with one navigation, readable content, and no footer; legal-page meaning remains unchanged.
 
-The home page product sentence is: “Evermind remembers. Nevermind brings context. Mastermind directs the work.” Preserve the distinct product roles and use accurate route-specific calls to action.
+The homepage lead is: “A human-owned system for AI work — from memory to context to controlled execution.” The product-sequence line is: “Evermind remembers. Nevermind brings context. Mastermind directs the work.” Preserve the distinct product roles and use accurate route-specific calls to action. Current implementation and release evidence live in `docs/implementation-plan.md`, `docs/roadmap.md`, and `docs/repo-status.md`; older design/strategy briefs are historical unless those active documents explicitly adopt them.
 
 ## Copy and claim boundaries
 

diff --git a/README.md b/README.md
@@ -67,13 +67,10 @@ Use these docs for website implementation only:
 5. `docs/design/` — design principles, visual language, product visual library, copy-to-visual mapping, motion storyboards, design-lab rules, and component contracts.
 6. `docs/platform/` — page architecture, responsive strategy, accessibility strategy, and performance strategy.
 7. `docs/migration/` — foundational legacy sweep, migration matrix, and content, route, component, style, motion, asset, and dependency audits.
-8. `docs/homepage-design-spec.md` — central homepage design brief and closed decisions.
-9. `docs/homepage-visual-storyboard.md` and `docs/homepage-example-data.md` — visual states and sanitized prototype content.
-10. `docs/homepage-technical-design.md` and `docs/homepage-design-orchestration.md` — historical build-planning evidence; check current source before relying on details.
-11. `docs/homepage-validation-plan.md` — visual, motion, accessibility, performance, and release gates.
-12. `docs/roadmap.md` — canonical 15-phase public-platform roadmap and continuous-governance status.
-13. `docs/implementation-plan.md` — dependency-gated implementation tasks with validation, rollback, and commit boundaries.
-14. `docs/auth-status.md`, `docs/deployment.md`, `docs/content-platform.md`, and related implementation docs — runtime and deployment facts.
+8. `docs/homepage-validation-plan.md` — active visual, motion, accessibility, performance, and release checks.
+9. `docs/implementation-plan.md` and `docs/roadmap.md` — current website implementation status and active follow-up.
+10. `docs/homepage-design-spec.md`, `docs/homepage-visual-storyboard.md`, `docs/homepage-example-data.md`, `docs/homepage-technical-design.md`, and `docs/homepage-design-orchestration.md` — historical/pre-build evidence; check current source before relying on details.
+11. `docs/auth-status.md`, `docs/deployment.md`, `docs/content-platform.md`, and related implementation docs — runtime and deployment facts.
 
 ## Architecture overview
 

diff --git a/docs/ai-guidelines.md b/docs/ai-guidelines.md
@@ -4,11 +4,11 @@ These rules describe how AI-assisted development and internal automation may int
 
 ## Current product boundary
 
-The canonical public products are Memory, Memory for QA, and Workbench. The public site also exposes Docs, Contact, Privacy, and Terms.
+Evermind and Nevermind are the connected Infinite Brain product system; Mastermind is a separate ProChat product. ProChat Memory for QA is paused/historical. The public site also exposes Docs, Contact, Privacy, and Terms.
 
 Retired Kits, ProChat OS, AI Workflows, Studio, Proof, Prompts, generated Docs, checkout/licensing, and MailerLite systems are historical only. Do not restore them because older docs or Git history mention them.
 
-BuildFlow may appear only where a technical/internal compatibility identifier is required by Workbench implementation contracts.
+BuildFlow may appear only where a technical/internal compatibility identifier is required by Mastermind implementation contracts.
 
 ## Repository safety
 

diff --git a/docs/archive/retired-systems/github-entitlements.md b/docs/archive/retired-systems/github-entitlements.md
@@ -96,7 +96,7 @@ The entitlement state is therefore spread across:
 
 ## Required environment variables
 
-The env contract lives in [environment.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs-public/environment.md).
+The env contract lives in [environment.md](../../../docs-public/environment.md).
 
 GitHub App-specific values:
 
@@ -120,6 +120,6 @@ This doc should not be read as a generic entitlement framework. It documents the
 
 ## Related references
 
-- [integrations.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs/integrations.md)
-- [environment.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs-public/environment.md)
-- [production-lifecycle.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs/production-lifecycle.md)
+- [integrations.md](../../integrations.md)
+- [environment.md](../../../docs-public/environment.md)
+- [production-lifecycle.md](../../production-lifecycle.md)
diff --git a/docs/archive/retired-systems/mailerlite-funnel.md b/docs/archive/retired-systems/mailerlite-funnel.md
@@ -28,7 +28,7 @@ Current behavior:
 
 ## Environment variables
 
-Canonical env documentation lives in [environment.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs-public/environment.md).
+Canonical env documentation lives in [environment.md](../../../docs-public/environment.md).
 
 Current values used by the route (required):
 
@@ -70,6 +70,6 @@ The route does not currently store subscriber records in Prisma.
 
 ## Related references
 
-- [integrations.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs/integrations.md)
-- [environment.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs-public/environment.md)
-- [content-platform.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs/content-platform.md)
+- [integrations.md](../../integrations.md)
+- [environment.md](../../../docs-public/environment.md)
+- [content-platform.md](../../content-platform.md)
diff --git a/docs/automation-routes.md b/docs/automation-routes.md
@@ -155,6 +155,6 @@ Required env:
 
 ## Related references
 
-- [integrations.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs/integrations.md)
-- [environment.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs-public/environment.md)
-- [development.md](/Users/Office/Repos/Organisation/ProChat/Web/prochat/docs/development.md)
+- [integrations.md](integrations.md)
+- [environment.md](../docs-public/environment.md)
+- [development.md](development.md)
diff --git a/docs/content-platform.md b/docs/content-platform.md
@@ -7,9 +7,9 @@ This document describes the current root-domain public content and SEO contract.
 The active canonical public surface is intentionally small:
 
 - `/`
-- `/memory`
-- `/memory-qa`
-- `/workbench`
+- `/evermind`
+- `/nevermind`
+- `/mastermind`
 - `/docs`
 - `/contact`
 - `/privacy`
@@ -19,7 +19,7 @@ The root sitemap emits only those eight routes.
 
 ## Documentation
 
-The active `/docs` route is a repository-oriented hub for Memory for QA and Workbench. It links readers to repository documentation, issues, and beta/contact paths.
+The active `/docs` route is a reading-friendly hub for Evermind, Nevermind, and Mastermind. It links readers to product routes and contact; canonical product documentation remains with the relevant repositories.
 
 The former generated public documentation system is retired. In particular:
 
@@ -45,11 +45,11 @@ Current SEO behavior is deliberately bounded:
 - compatibility aliases redirect into canonical public routes rather than publishing duplicate bodies
 - retired product/content routes are not emitted by the sitemap
 
-Structured data and page metadata should describe only active Memory, Memory for QA, Workbench, Docs, Contact, and legal surfaces.
+Structured data and page metadata should describe only active Evermind, Nevermind, Mastermind, Docs, Contact, and legal surfaces.
 
 ## Compatibility boundaries
 
-Some historical URLs remain only as redirect compatibility, including BuildFlow / ProChat OS aliases to Workbench, Learn aliases to Docs, legal aliases to the current Privacy/Terms pages, and waitlist aliases into the Memory for QA beta contact flow.
+Some historical URLs remain only as redirect compatibility, including BuildFlow / ProChat OS aliases to Mastermind, Learn aliases to Docs, legal aliases to the current Privacy/Terms pages, and retired waitlist aliases into Contact.
 
 Compatibility routes must not restore retired product bodies or duplicate canonical content.
 

diff --git a/docs/design-system.md b/docs/design-system.md
@@ -1,11 +1,13 @@
 # ProChat Design-System Implementation Bridge
 
-**Status:** repository-local implementation guidance  
+**Status:** historical design-system migration guidance
 **Canonical design truth:** `DESIGN.md` and `brand-spec.md`  
 **Canonical strategy and company design:** Mind
 
 This file explains how the approved ProChat design system should be introduced into the existing website repository.
 
+> This migration plan predates the current cinematic and utility route systems. Its planned token files, GSAP direction, and migration sequence are not current implementation facts. For the live route contract and stylesheet ownership, use `docs/overview.md`, `docs/implementation-plan.md`, and `docs/homepage-validation-plan.md`.
+
 Existing tokens, themes, gradients, fonts, hero components, and page-specific styles remain implementation inventory. They are not canonical design authority and must not be extended by default.
 
 ## Required reading order

diff --git a/docs/design/MOTION_STORYBOARD.md b/docs/design/MOTION_STORYBOARD.md
@@ -1,9 +1,9 @@
 # ProChat Motion Storyboard
 
-**Status:** canonical motion planning document  
+**Status:** historical pre-build motion planning document
 **Authority:** `docs/homepage-visual-storyboard.md`, `DESIGN.md`
 
-> Historical pre-cinematic storyboard. Its Memory/QA-specific sequences are not the current public route specification. Current routes `/`, `/evermind`, `/nevermind`, and `/mastermind` share two full-viewport sections, an intentional 80vh empty spacer, and one scroll-driven cinematic media layer. Other public routes are outside this visual redesign. See `docs/homepage-validation-plan.md` and `docs/implementation-plan.md` for active behavior and evidence.
+> Historical pre-build storyboard. Its Memory/QA-specific sequences are not the current public route specification. Current routes `/`, `/evermind`, `/nevermind`, and `/mastermind` share three ordered product stages, one scroll-driven cinematic media layer, and shared geometry. `/docs`, `/contact`, `/privacy`, and `/terms` use the static utility shell; legal body copy remains unchanged. See `docs/homepage-validation-plan.md` and `docs/implementation-plan.md` for active behavior and evidence.
 
 ## Purpose
 

diff --git a/docs/development.md b/docs/development.md
@@ -27,9 +27,9 @@ npm run build
 The active public website is exactly:
 
 - `/`
-- `/memory`
-- `/memory-qa`
-- `/workbench`
+- `/evermind`
+- `/nevermind`
+- `/mastermind`
 - `/docs`
 - `/contact`
 - `/privacy`
@@ -39,7 +39,7 @@ Compatibility aliases may redirect into those routes, but new public work should
 
 ## Documentation workflow
 
-Internal repository documentation lives under `docs/` and `docs-public/`. The active public `/docs` page is a lean repository hub for Memory for QA and Workbench.
+Internal repository documentation lives under `docs/` and `docs-public/`. The active public `/docs` page is a reading-friendly hub for Evermind, Nevermind, and Mastermind, presented in the shared static utility shell. Contact and legal routes use that shell too; legal body text remains unchanged.
 
 The former Nextra/generated `src/content/docs` + `scripts/docs` pipeline is retired.
 

diff --git a/docs/docs-automation.md b/docs/docs-automation.md
@@ -15,7 +15,7 @@ The cleanup removed the generated documentation system, including:
 
 ## Current documentation model
 
-The active public documentation surface is the lean `/docs` repository hub for Memory for QA and Workbench. Canonical product documentation should live with the relevant repositories and be linked from that hub.
+The active public documentation surface is a reading-friendly `/docs` hub for Evermind, Nevermind, and Mastermind. Canonical product documentation should live with the relevant repositories and be linked from that hub.
 
 Internal repository documentation remains under `docs/` and `docs-public/` as appropriate.
 

diff --git a/docs/getting-started.md b/docs/getting-started.md
@@ -29,9 +29,9 @@ The default local port is `3056` unless overridden by `PORT`.
 Canonical public routes:
 
 - `/`
-- `/memory`
-- `/memory-qa`
-- `/workbench`
+- `/evermind`
+- `/nevermind`
+- `/mastermind`
 - `/docs`
 - `/contact`
 - `/privacy`

diff --git a/docs/homepage-design-orchestration.md b/docs/homepage-design-orchestration.md
@@ -1,9 +1,11 @@
 # ProChat Homepage Design Orchestration
 
-**Status:** approved pre-build workflow  
+**Status:** historical pre-build workflow
 **Source skills:** Brain `ai/skills`  
 **Scope:** design research, specification, prototyping, implementation, review, and polish
 
+> This workflow is retained as historical planning evidence, not as current release authority. Follow the active source and validation references in `docs/overview.md`, `docs/implementation-plan.md`, and `docs/homepage-validation-plan.md`.
+
 This document defines how GPT-5.6 Sol uses the Brain design skills across research, specification, prototyping, implementation, review, and polish. It prevents duplicated design authority, conflicting methods, and unstructured execution.
 
 ## Operating principle

diff --git a/docs/homepage-design-spec.md b/docs/homepage-design-spec.md
@@ -1,13 +1,15 @@
 # ProChat Homepage Design Specification
 
-**Status:** approved pre-build design brief  
+**Status:** superseded pre-build design brief; retained as historical evidence
 **Canonical copy:** Mind `canonical-homepage-copy.md`  
 **Design system:** `DESIGN.md` and `brand-spec.md`  
 **Visual specification:** `docs/homepage-visual-storyboard.md`  
 **Technical architecture:** `docs/homepage-technical-design.md`  
 **Skill workflow:** `docs/homepage-design-orchestration.md`
 
-This is the central repository-local brief for the ProChat homepage. It explains what must be designed, why it matters, and which decisions are already closed.
+> This specification describes the retired Memory-first/Memory-for-QA/Workbench homepage direction. It is not current product, copy, route, or acceptance authority. Current direction is defined by Mind and the shipped implementation; use `docs/homepage-validation-plan.md`, `docs/implementation-plan.md`, and `docs/roadmap.md` for current website state.
+
+This document preserves the original pre-build design rationale and closed decisions for historical reference only.
 
 ## Objective
 

diff --git a/docs/homepage-technical-design.md b/docs/homepage-technical-design.md
@@ -1,9 +1,11 @@
 # ProChat Homepage Technical Design
 
-**Status:** approved pre-build architecture  
+**Status:** superseded pre-build architecture; retained as historical evidence
 **Scope:** homepage design system, prototypes, implementation, motion, validation, and production hardening  
 **Does not authorize:** production homepage implementation before prototype and plan-review gates pass
 
+> This was a pre-build plan and does not describe the current renderer or authorize further implementation. Current source and acceptance authority are `docs/implementation-plan.md`, `docs/homepage-validation-plan.md`, and `docs/roadmap.md`.
+
 ## Current repository stack
 
 Verified current stack:

diff --git a/docs/homepage-validation-plan.md b/docs/homepage-validation-plan.md
@@ -1,7 +1,7 @@
 # ProChat public-site validation plan
 
 **Status:** current validation contract for the cinematic public website
-**Applies visually to:** `/`, `/evermind`, `/nevermind`, and `/mastermind`. Other canonical routes are regression-only.
+**Applies visually to:** `/`, `/evermind`, `/nevermind`, `/mastermind`, `/contact`, and `/docs`. `/privacy` and `/terms` share the static utility shell; their legal body meaning remains outside visual copy changes.
 
 Product truth comes from `mind/organizations/prochat/brand/`; implementation state comes from current source and `docs/implementation-plan.md`. Older homepage/page-architecture plans are historical unless explicitly reconciled.
 
@@ -10,7 +10,7 @@ Product truth comes from `mind/organizations/prochat/brand/`; implementation sta
 - Evermind is free, open-source, human-owned memory; Nevermind is its paid capability/convenience layer; Mastermind is a separate free planning/orchestration product.
 - ProChat Memory for QA is paused/historical, not a current public product.
 - Home communicates the product family accurately; each product route explains its own role and CTA destination.
-- Product identities on the four cinematic routes match Mind; do not change Contact/Docs copy or navigation in this release.
+- Product identities on all active routes match Mind. Contact and Docs use Evermind/Nevermind/Mastermind terminology; legal shell changes must not rewrite legal body copy.
 - Claims about privacy, security, integrations, pricing, availability, and outcomes match Mind and verified implementation. Privacy/Terms meaning must not be changed by a shell migration.
 
 ## Shared cinematic-page checks
@@ -23,7 +23,7 @@ For `/`, `/evermind`, `/nevermind`, and `/mastermind` verify:
 - shared route data changes copy without changing geometry or visual system;
 - capability display is one translucent glass panel, with background media visibly present through it;
 - media visibly scrubs with scroll, forward and reverse; adjacent frames blend and renderer handoffs stay continuously painted;
-- two stages activate in reading order, without text overlap or jarring chapter jumps;
+- the Evermind / Memory, Nevermind / Context, and Mastermind / Execution stages activate in reading order, without text overlap or jarring chapter jumps;
 - every CTA is usable and remains on one line without clipping.
 
 ## Responsive and motion matrix
@@ -32,6 +32,10 @@ Check widths `1440`, `1280`, `1024`, `768`, `430`, `390`, and `360` pixels. Revi
 
 Under `prefers-reduced-motion: reduce`, verify all stages and links remain available, no scroll scrubbing occurs, media freezes to one stable poster/frame, video and canvas are not visibly duplicated, and layout geometry remains understandable. Include a reduced-motion desktop screenshot.
 
+## Static utility shell
+
+For `/contact`, `/docs`, `/privacy`, and `/terms`, verify one transparent full-width navigation, no legacy footer or dark capsule, no video/canvas animation, Golos Text display headings, no horizontal overflow, and readable glass surfaces. Verify Contact submission and mobile navigation; verify Docs content remains readable at desktop, laptop, tablet, and mobile widths. Privacy and Terms body copy must remain semantically unchanged.
+
 ## Accessibility, performance, and runtime
 
 - Keyboard, focus-visible, accessible names/landmarks, form labels/errors, and target sizes pass.