# SOPHIAClaw — Master Documentation > AI with Guardrails for Growing Businesses — the first Thalamus AI product using the master documentation structure. **Status:** Internal Validation **Bible Version:** 0.1 (2026-02-24) **Documentation Version:** 1.0 **Current Sprint:** [Sprint 1: Foundation](00-command-center/CURRENT_SPRINT.md) --- ## Quick Links | Link | Purpose | Start Here When... | | ----------------------------------------------------- | ----------------------------------------------- | ------------------------------------------------- | | [Bible (Start Here)](00-command-center/BIBLE.md) | Master living document — single source of truth | Beginning any work session; loading AI context | | [Current Sprint](00-command-center/CURRENT_SPRINT.md) | Active work and immediate priorities | Checking what's being worked on right now | | [Decision Log](00-command-center/DECISION_LOG.md) | Every strategic and architectural decision | Wondering "why did we do it this way?" | | [Roadmap](02-product/ROADMAP.md) | Phased delivery plan with dependencies | Planning next quarter or evaluating timeline | | [Ecosystem Map](07-reference/ECOSYSTEM_MAP.md) | How SOPHIAClaw connects to Thalamus ecosystem | Understanding integration points and dependencies | --- ## Documentation Map ### 00 — Command Center **Purpose:** Daily operations, source of truth, current state **Status:** Foundation laid — Sprint 1 | Document | Purpose | Key Content | | -------------------------------------------------------- | ---------------------- | ---------------------------------------------------------- | | [BIBLE.md](00-command-center/BIBLE.md) | Master living document | Product vision, current state, roadmap summary, open risks | | [CURRENT_SPRINT.md](00-command-center/CURRENT_SPRINT.md) | Active work tracker | What's being built now, blocked items, completed work | | [DECISION_LOG.md](00-command-center/DECISION_LOG.md) | Decision history | Timestamped decisions with rationale, reversible? | | [OPEN_QUESTIONS.md](00-command-center/OPEN_QUESTIONS.md) | Parking lot | Unresolved questions, blocking status, resolution tracking | **Start here for:** Every work session. Load the Bible into AI context first. --- ### 01 — Strategy **Purpose:** Business case, market analysis, pricing, go-to-market **Status:** Hypothesis phase — awaiting validation | Document | Purpose | Key Content | | ------------------------------------------------------------------ | --------------------- | ------------------------------------------------------- | | [VISION_AND_POSITIONING.md](01-strategy/VISION_AND_POSITIONING.md) | What and why | Product vision, target market, differentiation strategy | | [MARKET_ANALYSIS.md](01-strategy/MARKET_ANALYSIS.md) | Market opportunity | TAM/SAM/SOM, market dynamics, trends | | [COMPETITIVE_LANDSCAPE.md](01-strategy/COMPETITIVE_LANDSCAPE.md) | Competition | Competitor analysis, positioning matrix, moat strategy | | [IDEAL_CUSTOMER_PROFILE.md](01-strategy/IDEAL_CUSTOMER_PROFILE.md) | Who we serve | ICP definition, segmentation, persona details | | [PRICING_MODEL.md](01-strategy/PRICING_MODEL.md) | How we price | Pricing tiers, unit economics, validation status | | [REVENUE_MODEL.md](01-strategy/REVENUE_MODEL.md) | Financial projections | Revenue targets, margin goals, growth model | | [GO_TO_MARKET.md](01-strategy/GO_TO_MARKET.md) | Launch strategy | Channels, partnerships, launch phases | **Start here for:** Strategic discussions, investor conversations, market planning --- ### 02 — Product **Purpose:** What we're building, for whom, and when **Status:** Requirements defined — awaiting implementation | Document | Purpose | Key Content | | --------------------------------------------------------------------- | ---------------------- | ------------------------------------------------------ | | [PRODUCT_REQUIREMENTS.md](02-product/PRODUCT_REQUIREMENTS.md) | Master PRD | Features, priorities, constraints, acceptance criteria | | [ROADMAP.md](02-product/ROADMAP.md) | Delivery plan | Phased milestones, dependencies, timeline | | [USER_JOURNEYS.md](02-product/USER_JOURNEYS.md) | End-to-end flows | Persona-specific workflows and interactions | | [INFORMATION_ARCHITECTURE.md](02-product/INFORMATION_ARCHITECTURE.md) | Navigation & structure | Content hierarchy, taxonomy, organization | | [UX_PRINCIPLES.md](02-product/UX_PRINCIPLES.md) | Design philosophy | Interaction patterns, design system, accessibility | **Features Subdirectory:** | Document | Purpose | |----------|---------| | [\_FEATURE_TEMPLATE.md](02-product/features/_FEATURE_TEMPLATE.md) | Template for new features | | [GATEWAY_DASHBOARD.md](02-product/features/GATEWAY_DASHBOARD.md) | Gateway web dashboard spec | | [TELEGRAM_INTEGRATION.md](02-product/features/TELEGRAM_INTEGRATION.md) | Telegram channel feature spec | **Start here for:** Feature development, UX decisions, scope discussions --- ### 03 — Architecture **Purpose:** How we're building it, technical decisions, integrations **Status:** Foundation defined — awaiting detailed specs | Document | Purpose | Key Content | | -------------------------------------------------------------------------- | ------------------ | ------------------------------------------------------------- | | [TECHNICAL_REQUIREMENTS.md](03-architecture/TECHNICAL_REQUIREMENTS.md) | Master TRD | System requirements, constraints, non-functional requirements | | [SYSTEM_ARCHITECTURE.md](03-architecture/SYSTEM_ARCHITECTURE.md) | High-level design | Components, relationships, data flow | | [DATA_MODEL.md](03-architecture/DATA_MODEL.md) | Data structures | Schema definitions, relationships, migrations | | [API_SPECIFICATION.md](03-architecture/API_SPECIFICATION.md) | API contracts | Endpoints, auth, rate limits, versioning | | [INTEGRATION_REQUIREMENTS.md](03-architecture/INTEGRATION_REQUIREMENTS.md) | External systems | SYNAPTICA touchpoints, third-party integrations | | [SECURITY_ARCHITECTURE.md](03-architecture/SECURITY_ARCHITECTURE.md) | Security framework | Auth, encryption, compliance, zero-trust | | [INFRASTRUCTURE.md](03-architecture/INFRASTRUCTURE.md) | Operations | Deployment, scaling, monitoring, cost | **Decisions Subdirectory:** | Document | Purpose | |----------|---------| | [\_ADR_TEMPLATE.md](03-architecture/decisions/_ADR_TEMPLATE.md) | Template for ADRs | | [ADR-001-gateway-local-first.md](03-architecture/decisions/ADR-001-gateway-local-first.md) | Local-first architecture decision | **Start here for:** Technical implementation, architecture decisions, integration work --- ### 04 — Validation **Purpose:** Continuum validation methodology, evidence collection, metrics **Status:** Phase 1 planning — awaiting execution | Document | Purpose | Key Content | | ---------------------------------------------------- | ------------------ | ---------------------------------------- | | [CONTINUUM_PLAN.md](04-validation/CONTINUUM_PLAN.md) | Validation roadmap | Phases, exit criteria, timeline, metrics | **Subdirectories:** - `feedback/` — Per-partner or per-cohort feedback files (created during beta) - `transparency-reports/` — Monthly reports once in beta **Start here for:** Validation planning, metrics tracking, evidence review --- ### 05 — Operations **Purpose:** Running SOPHIAClaw in production — deployment, support, incidents **Status:** Not yet created — will be populated during internal validation **Planned Documents:** - RUNBOOK.md — Deployment procedures, rollback, maintenance - SUPPORT_PLAYBOOK.md — Common issues, escalation paths, SLAs - ONBOARDING.md — Customer onboarding flow - INCIDENT_RESPONSE.md — Incident classification and response - COMPLIANCE.md — Regulatory requirements, audit trails **Start here for:** Deployment, operations, support, compliance --- ### 06 — Content **Purpose:** Marketing, messaging, sales enablement **Status:** Not yet created — will be populated during validation phases **Planned Documents:** - MESSAGING_FRAMEWORK.md — Voice, positioning, key messages - CONTENT_CALENDAR.md — Planned content tied to milestones - LANDING_PAGE.md — Landing page copy and structure **Subdirectories:** - `case-studies/` — Post-validation case studies - `sales-enablement/` — Pitch decks, one-pagers, objection handling **Start here for:** Marketing, content creation, sales preparation --- ### 07 — Reference **Purpose:** Glossary, ecosystem map, version history **Status:** Complete — v1.0 | Document | Purpose | Key Content | | ------------------------------------------------- | --------------- | ---------------------------------------------------------- | | [GLOSSARY.md](07-reference/GLOSSARY.md) | Terminology | 20+ product-specific terms and definitions | | [ECOSYSTEM_MAP.md](07-reference/ECOSYSTEM_MAP.md) | Integration map | SYNAPTICA connections, sibling products, external services | | [CHANGELOG.md](07-reference/CHANGELOG.md) | Version history | Changes across all master documentation | | `archive/` | Superseded docs | Historical versions of documents | **Start here for:** Understanding terms, integration planning, version tracking --- ## AI Context Loading Guide When starting an AI session about SOPHIAClaw, load documents in this order: ### Quick Session (Brainstorming, Questions) 1. [BIBLE.md](00-command-center/BIBLE.md) only ### Deep Session (Architecture, Implementation) 1. [BIBLE.md](00-command-center/BIBLE.md) 2. Relevant [03-architecture/](03-architecture/) documents 3. [DECISION_LOG.md](00-command-center/DECISION_LOG.md) ### Validation Session (Metrics, Feedback) 1. [BIBLE.md](00-command-center/BIBLE.md) 2. [04-validation/](04-validation/) documents 3. [CURRENT_SPRINT.md](00-command-center/CURRENT_SPRINT.md) ### Full Context (New Collaborator Onboarding) 1. [BIBLE.md](00-command-center/BIBLE.md) 2. [ECOSYSTEM_MAP.md](07-reference/ECOSYSTEM_MAP.md) 3. [VISION_AND_POSITIONING.md](01-strategy/VISION_AND_POSITIONING.md) --- ## Status Indicators Throughout the documentation, you'll see these status labels: | Status | Meaning | | ----------------------- | ------------------------------------------- | | **Draft** | Early work in progress, may be incomplete | | **Internal Validation** | Being tested internally, subject to change | | **Beta** | In controlled external testing | | **Commercial** | Generally available, commercially supported | | **Mature** | Stable, well-established, minimal changes | | **Deprecated** | Being phased out, migration recommended | | **Archived** | Superseded, kept for historical reference | --- ## Assumption Tagging Claims prefixed with `[ASSUMPTION]` haven't been validated through Continuum yet. When validated, the tag is removed and replaced with an evidence reference. Example: - `[ASSUMPTION] Users prefer Telegram over Slack for SOPHIAClaw interactions` - `✓ Validated: 70% of beta users chose Telegram as primary channel (Beta Cohort 1 Feedback, 2026-03-15)` --- ## Contributing to Master Documentation ### When to Update | Document Type | Trigger | | -------------- | ----------------------------------- | | Bible | Biweekly review or strategic shifts | | Current Sprint | Weekly minimum or priority changes | | Decision Log | Real-time — every decision | | Open Questions | Weekly or when questions resolve | | Strategy Docs | Monthly or market changes | | Product Docs | Per sprint or feature changes | | Architecture | Per change or new ADR | | Validation | Per phase or new evidence | | Operations | Per release or incident | | Content | Per milestone | | Reference | As needed | ### Version Discipline 1. Update the document's version in its frontmatter 2. Add an entry to [CHANGELOG.md](07-reference/CHANGELOG.md) 3. Move superseded versions to [07-reference/archive/](07-reference/archive/) 4. Never delete documentation history --- ## About This Structure This master documentation structure follows the [Thalamus AI Blueprint](master-documentation-blueprint.md). It is designed for: - **ADHD-optimized workflows** — External memory system with clear organization - **Continuum validation** — Structupurple evidence collection across phases - **Multi-product ecosystems** — Understanding ripple effects across Thalamus products **SOPHIAClaw** is the first Thalamus AI product using this structure. It serves as the template for future products. --- ## Questions? - Documentation structure questions: See [master-documentation-blueprint.md](master-documentation-blueprint.md) - Product questions: Start with [BIBLE.md](00-command-center/BIBLE.md) - Technical questions: Check [SYSTEM_ARCHITECTURE.md](03-architecture/SYSTEM_ARCHITECTURE.md) - Integration questions: Review [ECOSYSTEM_MAP.md](07-reference/ECOSYSTEM_MAP.md) --- **Last Updated:** February 24, 2026 **Version:** 1.0 **Next Review:** March 3, 2026 (weekly during Sprint 1)