Website North Star

0. Intelligence Systems Identity

SMARTHAUS engineers mathematically-governed intelligence systems.
RFS is the first field-native memory substrate that makes them possible.

This site must reflect that identity at all times.
Intelligence systems are the structural outcome of our architecture:

RFS (Memory) → AQL (Chemistry) → AEF (Physics) → AIOS (Biology) → TAI/AIVA (Organisms)

This is the core narrative behind every page and every structural decision.

Purpose

This document defines the governing truth for the SMARTHAUS website.

The website is not a marketing asset. It is not a design showcase. It is not meant to look “impressive.”

The website is the public interface to a scientific company building mathematically-governed intelligence systems with field-native memory substrates.

Design mandate:

Minimalist
Thinking‑machines aesthetic (blue, tan, neutral field‑native colors)
No decorative visuals
No gradients or animations unless functional
Precision over personality
Depth over style

The site must communicate RFS-first, mathematical, field-native, deep‑tech, not “startup polished.”

Strategic Identity

SMARTHAUS is a deep‑tech scientific architecture company pioneering mathematically-governed intelligence systems.

Everything on the website must reinforce:

RFS → Mathematical Autopsy → Systems → Research → Company

RFS is the flagship and the beginning of the SmartHaus revolution. All other systems are downstream of RFS and MA. No exceptions.

Layout Mandate (Updated)

We are keeping the existing website layout and navigation structure. This update is a refocusing, not a redesign.

All pages must follow:

The RFS-first narrative
Mathematical Autopsy as the governing discipline
Systems presented as architectural components, not products
AIVA and TAI referenced as RFS-powered archetypes (inside Systems/Research), not top-level pages
No new navigation items
Homepage remains: Hero (RFS) → Autopsy → Systems → Research
Thinking-machines aesthetic enforced (deep blue + tan, engineered minimalism)
Textual clarity and density over decoration

This preserves the IA while updating the meaning and presentation of each page.

Problem statement

Domain: public marketing + deep‑tech architecture communication for SMARTHAUS’ field‑native systems
Audience: hardware executives, AI system architects, enterprise buyers, researchers, partners, candidates
Business goals:
- Establish RFS as the flagship breakthrough
- Demonstrate Mathematical Autopsy as the engineering method
- Clarify the Systems stack (CAIO, MAIA, ALQ, AEF, VFE, VEE, NME, AIVA)
- Position Advisory as an implementation layer, not a primary pillar
- Build credibility as a deep‑tech company in field‑native AI architecture

Information architecture & navigation

Top‑level navigation MUST be:

Systems (links to /platforms)
- TAI (Temporal autonomy interface) - Research status
- AIVA (Adaptive intelligence architecture) - Research status
Research (links to /research)
- Research Overview
- Proofs Library
- Insights
- Benchmarks
Company (links to /company)
- About
- Careers
- Contact
Get Started (CTA button)

Rules

Systems MUST appear first after the logo.
Research MUST appear second.
Company MUST appear third.
Systems dropdown contains TAI and AIVA (both marked as Research systems).
Research dropdown contains Research Overview, Proofs Library, Insights, and Benchmarks.
Company dropdown contains About, Careers, and Contact.
RFS is accessible via /platforms/rfs (not a top-level nav item).
Mathematical Autopsy is accessible via research pages (not a top-level nav item).
No Advisory in primary navigation.

Visibility & status

Primary Emphasis

RFS (flagship)
Mathematical Autopsy (engineering method)

Systems Visibility (Correct Stack)

CAIO — visible, full page
MAIA — visible, full page
ALQ — visible, full page
AEF — visible, full page
VFE — visible, full page
VEE — visible, full page
NME — visible, full page
AIVA — visible with an “Under Development” badge

Platforms

TAI — visible as a platform built on top of the Systems stack, NOT equal to Systems components

Advisory

Removed from primary navigation
Advisory content may exist at /advisory/* routes but is not a primary navigation item
Explicitly NOT a homepage pillar
Not part of the main site navigation structure

Homepage Focus

The homepage must be severe, minimal, and engineered—not ornamental.

1. Establish SMARTHAUS as a scientific company

One sentence must make this unmistakable: "SMARTHAUS engineers mathematically-governed intelligence systems. RFS is the first field-native memory substrate that makes them possible."

2. RFS is the hero

No animation, no fluff, no fancy graphics. A single, powerful, minimal block:

“RFS: The first field‑native memory architecture with mathematical guarantees.”

CTA: Explore RFS (only one hero CTA allowed)

3. Mathematical Autopsy is the second section

A concise, surgical explanation of MA:

math-first
notebook-first
invariants
proofs before implementation

CTA: Learn Mathematical Autopsy

4. Systems (Research)

Two organism archetypes built on the RFS → AQL → AEF → AIOS stack:

TAI (Personal intelligence system prototype)
AIVA (System-building architecture for intelligent applications)

Both marked as "Research system" status.

This is NOT a product grid. It is a pointer to the research architecture.

5. Research Section

Research carousel showcasing proofs, benchmarks, and field experiments that validate RFS and the Autopsy method.

6. Design Aesthetic Enforced

Blue / tan / neutral palette
No decorative illustrations
Everything must feel engineered
Layouts must resemble scientific and mathematical documentation
Typography: technical, calm, precise

Scope

In‑scope:
- The public-facing SMARTHAUS.ai website
- All RFS, Mathematical Autopsy, and Systems content (CAIO, MAIA, ALQ, AEF, VFE, VEE, NME, AIVA)
- Platform pages (TAI) as layers built on top of the Systems stack
- Research, proofs, technical insights, systems architecture documentation
- Advisory overview pages (AIDF + Autopsy) as supporting content
Out‑of‑scope:
- Any positioning that treats Advisory as a primary pillar or navigation item
- Deprecated naming or legacy architectures (AIUCP, LQL, LEF, VBE, LATTICE, "holographic memory")
- Experimental or internal tooling not intended for the public website
- Any content that contradicts the RFS‑first → Autopsy‑second hierarchy
- Inline styles (style={{}} props) - all styling must use CSS classes

Outcomes and SLOs

Performance

CI Lighthouse: Performance ≥ 90; Accessibility ≥ 90; Best Practices ≥ 90; SEO ≥ 90
Bundle size (first load shared): < 10 MB; Build time < 5 minutes
Local runs may warn; CI enforces thresholds

Accessibility

Key flows a11y‑scanned; no critical issues; semantic landmarks and focus states present

SEO & Content

Every page.tsx has metadata (title, description, OG/Twitter where applicable)
No broken internal links; sitemap valid; canonical branding terms enforced (SMARTHAUS, AIVA, TAI, RFS)

Reliability & Quality

Tests pass; coverage ≥ 80%
make ai-validate green on PRs and before release
Deterministic builds; no 404s in primary navigation

Guardrails & Invariants

Branding & Terminology Rules

SMARTHAUS must always appear in uppercase.
RFS is the flagship and must always be presented first on the homepage.
Mathematical Autopsy is the engineering method and must appear second on the homepage.
Systems stack references: TAI and AIVA are research systems built on RFS → AQL → AEF → AIOS stack.
Remove all references to "conscious systems" or "consciousness" - use "intelligence systems" instead.
Remove all references to "holographic memory."
No deprecated acronyms allowed (AIUCP, LQL, LEF, MAI, VBE, LATTICE).
Use "mathematically-governed intelligence systems" not "mathematically-engineered conscious systems."

Structure Rules

Homepage MUST follow: Hero (RFS messaging) → RFS Section → Autopsy → Systems (Research) → Research.
Advisory must NOT appear anywhere on the homepage or primary navigation.
Systems navigation contains TAI and AIVA (both research systems).
RFS must have its own dedicated landing page at /platforms/rfs.
All pages must use CSS classes, not inline styles (see Design Standards).

CI / Quality Rules

Terminology lint MUST block incorrect names.
Navigation must match the Information Architecture exactly.
No missing metadata, broken links, or structural violations.
No placeholder pages in primary nav.
No inline styles - Linter must flag style={{}} usage (except for truly dynamic runtime values).
CSS must be organized: global utilities in design-system.css, component styles in CSS modules.

Design standards

Source of truth:
- apps/web/app/styles/design-system.css (design tokens, component styles)
- apps/web/app/styles/palette.css (color palette)
- apps/web/app/styles/global.css (global styles and imports)
- apps/web/app/styles/fonts.css (typography)
- CI gate: scripts/ci/design_system_gate.py (enforcement where applicable)
MANDATORY: No inline styles - All styling must use CSS classes from the design system or CSS modules
North Star requires adherence to brand colors, fonts, and spacing from these docs
CSS architecture:
- Global utilities in design-system.css
- Component-specific styles in CSS modules (.module.css files)
- Page-specific styles in route-level CSS modules (page.module.css)
- No style={{}} props except for truly dynamic runtime-calculated values

Quality gates & thresholds (CI)

Content gate: branding, metadata completeness, internal links
Performance gate: bundle size, build time, Lighthouse (CI‑enforced)
Governance gate: structure, package configs, tsconfig, coverage ≥ 80%
Rigor privacy gate: sensitive data, PII patterns, privacy docs present
Docs gate: structure, links, header hierarchy for root/docs

Commands: make ai-validate, make website-quality-gate, make quality-gate

Milestones & acceptance (updated)

Phase 1 — Identity Foundation

Apply RFS‑first homepage rewrite
Apply Autopsy‑second section
Remove homepage Advisory content entirely
Update all branding + terminology to new stack

Phase 2 — Systems Alignment

Systems navigation contains TAI and AIVA (both marked as Research systems)
TAI and AIVA are presented as research systems built on RFS → AQL → AEF → AIOS stack
RFS has dedicated landing page at /platforms/rfs
Systems dropdown reflects research status for both TAI and AIVA

Phase 3 — Research & Proof Integration

Add dedicated RFS deep‑dive + proof references
Integrate ALQ/AEF technical notes where applicable
Migrate selected philipsiniscalchi.com articles to Insights

Phase 4 — Advisory Realignment

Remove Advisory from primary navigation
Advisory content remains accessible at /advisory/* routes but is not promoted
Ensure Advisory cannot outrank Systems in navigation or SEO structure

Acceptance Criteria

A release is acceptable ONLY IF:

RFS is the hero of the homepage.
Autopsy appears immediately after hero.
Systems reflect the correct stack and naming.
No deprecated terminology exists anywhere.
Advisory does not appear as a homepage section or in primary navigation.
All navigation matches the updated IA (Systems, Research, Company).
No inline styles - all styling uses CSS classes from the design system.
No 404s, missing metadata, or broken links.

Ownership & roles

Website Owner: product direction, acceptance
Gates Owner: CI gates health, thresholds, and remediations
Content Owner(s): branding, metadata, link hygiene

Metrics & telemetry

Web Vitals (LCP, CLS, INP) tracked on key pages (target: Core Web Vitals pass)
Bundle size trend; build time; Lighthouse deltas per release

Risks & assumptions

Local perf variance; CI is source of truth for budgets
Content churn can regress metadata/links → content gate required on PRs

Dependencies

Next.js 14 (App Router), Node 22.x, Playwright/Jest test stack
Vercel deployment with preview environments

References

Execution plan: docs/website/EXECUTION_PLAN.md
Rigor implementation: docs/RFS_RIGOR_IMPLEMENTATION.md
Vercel compatibility: docs/VERCEL_RIGOR_COMPATIBILITY.md
Privacy: docs/PRIVACY.md, docs/DATA_RETENTION.md
Cleanup plan: docs/CLEANUP_PLAN.md (comprehensive inline style removal and file cleanup)