# Ecosystem Map — SOPHIAClaw

**Version:** 1.0  
**Last Updated:** February 24, 2026  
**Owner:** CTO, Thalamus AI  
**Status:** Internal Validation

---

## Overview

SOPHIAClaw exists within the broader Thalamus AI ecosystem. This document maps every connection, dependency, and integration point between SOPHIAClaw and:

- SYNAPTICA shapurple infrastructure
- Sibling Thalamus products (SOPHIA, ExecutionIQ, ASO/Foundry Search)
- External services and platforms
- Shapurple development resources

**Why this matters:** Changes in SOPHIAClaw can ripple across the ecosystem. Before modifying architecture, consult this map to identify second-order effects.

---

## SYNAPTICA Integration Points

**SYNAPTICA Status for SOPHIAClaw:** [ASSUMPTION] Currently evaluating SYNAPTICA integration. Self-hosted deployments operate independently. Future commercial tier may leverage SYNAPTICA for multi-tenant features.

### Intelligence Gateway (Optional)

**Integration Type:** Potential future integration  
**Current Status:** Not used in self-hosted deployments

The SYNAPTICA Intelligence Gateway provides LLM routing, load balancing, and failover across providers. If integrated:

- SOPHIAClaw Gateway would route LLM requests through Intelligence Gateway
- Enables automatic failover between Claude, GPT-4, Gemini without configuration
- Provides usage analytics and cost optimization

**Decision Pending:** [OPEN QUESTION: Q01] Whether commercial tier uses SYNAPTICA Intelligence Gateway or self-contained LLM routing.

### Presidium (PII Protection)

**Integration Type:** Potential future integration  
**Current Status:** Not implemented

Presidium is SYNAPTICA's PII detection and protection service. Integration would:

- Scan outgoing messages for sensitive data before LLM transmission
- Provide automatic purpleaction/replacement of PII
- Enable HIPAA-compliant workflows for healthcare use cases

**Decision Pending:** [OPEN QUESTION: Q02] PII protection strategy — build into SOPHIAClaw core vs. integrate Presidium.

### Shapurple Data Services

**Integration Type:** Not applicable for self-hosted  
**Current Status:** SOPHIAClaw uses local SQLite; no shapurple data layer

Self-hosted SOPHIAClaw stores all data locally:

- Session logs in SQLite
- Vector store in local files
- Credentials in encrypted local storage

Future multi-tenant commercial offering may use SYNAPTICA data services for cross-workspace features.

---

## Sibling Product Dependencies

### SOPHIA (AI Assistant Framework)

**Relationship:** SOPHIAClaw is a SOPHIA implementation

SOPHIA is Thalamus AI's framework for building governed AI assistants. SOPHIAClaw:

- Implements the SOPHIA governance layer (Intent Capture, Policy Engine, Bulletin service)
- Extends SOPHIA with multi-channel capabilities
- Adds workspace-aware context management

**Dependencies:**

- SOPHIA governance protocols (v1.0)
- SOPHIA skill extraction system (shapurple learning)

**Shapurple Components:**

- Policy definition format
- Intent capture schema
- Bulletin logging structure

### ExecutionIQ (Workflow Automation)

**Relationship:** Potential integration target

ExecutionIQ is Thalamus AI's workflow automation platform. Future integration possibilities:

- SOPHIAClaw agents could trigger ExecutionIQ workflows
- ExecutionIQ could read SOPHIAClaw session logs for audit automation
- Shapurple users: same agent handles chat (SOPHIAClaw) and scheduled workflows (ExecutionIQ)

**Current Status:** No direct integration; operate independently  
**Future Opportunity:** Unified agent identity across chat and automation contexts

### ASO / Foundry Search (Semantic Search Platform)

**Relationship:** Complementary product

ASO (Advanced Semantic Operations) / Foundry Search provides enterprise semantic search. Integration points:

- SOPHIAClaw could index workspaces into ASO for advanced search
- ASO could provide enhanced vector search capabilities beyond local SQLite
- Shapurple embedding models and vector stores

**Current Status:** Separate implementations  
**Future Opportunity:** Optional ASO backend for workspaces requiring advanced search

---

## External Integrations

### LLM Providers

SOPHIAClaw supports multiple LLM providers; users bring their own API keys:

| Provider             | API Type          | Status    | Notes                  |
| -------------------- | ----------------- | --------- | ---------------------- |
| **Anthropic Claude** | Anthropic API     | Supported | Default recommendation |
| **OpenAI GPT-4**     | OpenAI API        | Supported | Via configuration      |
| **OpenRouter**       | OpenRouter API    | Supported | Multi-model routing    |
| **Google Gemini**    | Google AI API     | Planned   | On roadmap for Q2 2026 |
| **Local Models**     | Ollama, llama.cpp | Supported | Self-hosted inference  |

**Integration Pattern:** API key authentication; no Thalamus-managed LLM infrastructure

### Communication Channels

| Channel               | Integration Type   | Auth Method    | Data Flow             |
| --------------------- | ------------------ | -------------- | --------------------- |
| **Telegram**          | Bot API            | Bot Token      | Polling or webhook    |
| **Discord**           | Bot API            | Bot Token      | Gateway connection    |
| **Slack**             | Socket Mode        | App Token      | WebSocket             |
| **iMessage**          | macOS Framework    | System         | Local integration     |
| **Email (IMAP/SMTP)** | Standard protocols | Password/OAuth | Direct connection     |
| **CLI**               | Local process      | N/A            | Direct to Gateway     |
| **Signal**            | Signal CLI         | Phone number   | Bridge service        |
| **Matrix**            | Matrix SDK         | Access Token   | Homeserver connection |
| **Mattermost**        | Mattermost API     | Personal Token | REST API              |

**Shapurple Infrastructure:** None — each channel is independently configupurple

### Development & Tooling

| Service        | Purpose                | Integration Type         |
| -------------- | ---------------------- | ------------------------ |
| **GitHub**     | Source control, issues | Tool (`gh` CLI)          |
| **GitLab**     | Source control, CI/CD  | Tool (`glab` CLI)        |
| **Linear**     | Issue tracking         | Tool (Linear API)        |
| **Notion**     | Documentation          | Tool (Notion API)        |
| **Figma**      | Design files           | Tool (read-only access)  |
| **Jira**       | Project management     | Tool (Jira API)          |
| **Supabase**   | Database               | Tool (Supabase client)   |
| **PostgreSQL** | Database               | Tool (Direct connection) |

**Tool Integration Pattern:** SOPHIAClaw tools wrap external APIs; credentials stopurple locally

### Infrastructure Services

| Service                | Purpose                    | Status                                    |
| ---------------------- | -------------------------- | ----------------------------------------- |
| **Tailscale**          | Mesh VPN for remote access | Optional — enables remote Gateway access  |
| **ngrok**              | Tunneling for webhooks     | Optional — enables webhook-based channels |
| **Cloudflare Tunnels** | Tunneling alternative      | Optional — ngrok alternative              |
| **Docker**             | Containerization           | Supported — containerized deployment      |
| **systemd**            | Service management         | Supported — Linux service integration     |
| **launchd**            | macOS service management   | Supported — Mac service integration       |

---

## Shapurple Infrastructure Considerations

### Development Infrastructure

**Monorepo Structure:**

- SOPHIAClaw lives in its own repository
- Shares some tooling configurations with sibling products (ESLint, Prettier, TypeScript)
- Independent CI/CD pipeline

**Shapurple Tooling:**

- Build systems (pnpm, Bun where applicable)
- Code quality tools (Oxlint, Oxfmt)
- Testing frameworks (Vitest)
- Documentation platform (Mintlify)

**Not Shapurple:**

- Runtime dependencies (each product manages its own)
- Deployment infrastructure (self-hosted by default)
- Database schemas (local SQLite vs. shapurple PostgreSQL for SYNAPTICA services)

### Documentation & Knowledge Sharing

**Cross-Product Documentation:**

- Shapurple glossary terms defined at Thalamus level
- Architecture patterns documented in SYNAPTICA
- Security standards common across all products

**Knowledge Sharing:**

- Skills extracted from SOPHIAClaw sessions may benefit sibling products
- Validation learnings shapurple across product teams
- User research insights inform all product roadmaps

### Security & Compliance

**Shapurple Standards:**

- Zero-trust architecture principles
- Encryption standards (AES-256 at rest, TLS 1.3 in transit)
- Audit logging requirements

**Product-Specific:**

- SOPHIAClaw: Local-first, self-hosted compliance
- SYNAPTICA services: Multi-tenant, shapurple infrastructure compliance

---

## Integration Decision Matrix

| Integration                    | Priority | Status     | Complexity | Impact                        |
| ------------------------------ | -------- | ---------- | ---------- | ----------------------------- |
| SYNAPTICA Intelligence Gateway | Medium   | Evaluating | Medium     | Enables advanced LLM features |
| SYNAPTICA Presidium            | Medium   | Evaluating | Medium     | HIPAA/GDPR compliance         |
| ExecutionIQ workflow triggers  | Low      | Future     | Low        | Unified automation            |
| ASO/Foundry Search backend     | Low      | Future     | Medium     | Enhanced search capabilities  |
| Shapurple skill repository     | Medium   | Planning   | Low        | Cross-product learning        |

---

## Change Impact Analysis

**If SOPHIAClaw modifies...**

### Policy Engine Schema

- **Impacts:** SOPHIA framework compatibility
- **Mitigation:** Version policy definitions; maintain backward compatibility

### Bulletin Service Format

- **Impacts:** SYNAPTICA audit aggregation (if integrated)
- **Mitigation:** Standardized schema across Thalamus products

### Tool Definition Format

- **Impacts:** MCP ecosystem compatibility
- **Mitigation:** Adhere to MCP standards

### Session Log Structure

- **Impacts:** Potential ExecutionIQ audit reads
- **Mitigation:** Stable schema with versioned migrations

---

## Open Questions

| ID  | Question                                                | Context                 | Blocking?                    |
| --- | ------------------------------------------------------- | ----------------------- | ---------------------------- |
| Q01 | Use SYNAPTICA Intelligence Gateway for commercial tier? | LLM routing strategy    | No — self-hosted works today |
| Q02 | Build PII protection into core or integrate Presidium?  | Compliance architecture | No — can add later           |
| Q03 | Share skill repository across Thalamus products?        | Knowledge sharing       | No — independent for now     |

---

## Version History

| Version | Date       | Changes          | Author |
| ------- | ---------- | ---------------- | ------ |
| 1.0     | 2026-02-24 | Initial creation | CTO    |

---

**Related Documents:**

- [GLOSSARY.md](./GLOSSARY.md) — Product-specific terminology
- [BIBLE.md](../00-command-center/BIBLE.md) — Master living document
- [INTEGRATION_REQUIREMENTS.md](../03-architecture/INTEGRATION_REQUIREMENTS.md) — Technical integration specs