Skip to main content

How to Use This Portal

This portal serves four audiences. Every documentation page has three depth levels accessible via tabs:

Audience Roles

RoleTab to UseWhat You'll Find
Investors & Stakeholders"Executive Summary"High-level compliance posture, market strategy, risk management approach, competitive differentiation
Jesse (Founder)"Working Knowledge"Plain-language explanations of every system, decision rationale, what to say in meetings, McKinsey readiness
Engineering Team"Technical Spec"Implementation details, code examples, data schemas, API designs, deployment architecture
Enterprise ProcurementAll tabsSecurity controls, certifications, DPA structure, procurement packet contents

For the McKinsey Meeting

  1. Overview — Executive Summary tab
  2. SOC 2 & ISO 27001 — Working Knowledge tab
  3. Procurement Packet — Executive Summary tab
  4. Evidence Packs — Working Knowledge tab (this is the differentiator)
  5. Stage Gates — Working Knowledge tab (shows compliance timeline)
  6. ADR-001: US-First Strategy — full page

For Engineering Onboarding

  1. Overview — Technical Spec tab
  2. Data Model — Technical Spec tab
  3. Roles & Access — Technical Spec tab
  4. Tech Stack — full page
  5. API Design — full page
  6. Sasha AI Engine — Technical Spec tab
  7. Data Lifecycle — Technical Spec tab

For Investor Presentations

  1. Overview — Executive Summary tab
  2. Vision & Strategy — Executive Summary tab
  3. Roadmap Overview — Executive Summary tab
  4. AI Risk Register — Executive Summary tab

For Deep Dive (Jesse's Learning)

Read everything in order:

  1. Overview → Vision & Strategy → Audience Guide
  2. Privacy (all pages) → Security (all pages) → Compliance (all pages) → AI Governance (all pages)
  3. Compliance Roadmap (all stages)
  4. Architecture Decisions (all ADRs)
  5. Glossary (reference)

How Tabs Work

Every content page uses three tabs. Click the tab that matches your depth need:

  • Executive Summary: 2-3 paragraphs, suitable for board decks and investor conversations
  • Working Knowledge: Detailed but non-technical, suitable for founder-level understanding and stakeholder meetings
  • Technical Spec: Full implementation details with code, schemas, and diagrams for engineering handoff
tip

The tab selection persists as you navigate between pages. If you select "Working Knowledge" on one page, it stays selected on the next.