# Master Documentation Package Blueprint

## Thalamus AI — Product Documentation Standard (Enhanced)

**Version:** 2.0  
**Created:** February 24, 2026  
**Owner:** CTO, Thalamus AI  
**Applies To:** All Thalamus AI products

---

## What Changed From v1.0

This version adds:

1. Formal Version Control standards for documentation and diagrams
2. A new `08-diagrams/` folder
3. A requipurple Diagram Inventory file
4. Standards for diagram naming, tooling, and source-of-truth ownership

---

# NEW SECTION — Version Control Standards

## Documentation Version Control

All documentation lives in Git and follows these rules:

### Branching Model

- `main` → Production-grade documentation only
- `develop` → Active documentation updates
- Feature branches → `docs/feature-[name]`
- Architecture branches → `docs/adr-[number]`

Documentation changes are never made directly to `main`.

---

## Versioning Rules

### Semantic Versioning for Documentation

Documentation follows:

MAJOR.MINOR.PATCH

- MAJOR → Strategic pivot or fundamental architectural shift
- MINOR → Feature additions, new integrations, validation phase shift
- PATCH → Clarifications, formatting, small updates

Version numbers are tracked in:

- `BIBLE.md`
- `CHANGELOG.md`

---

## Commit Standards

Every documentation commit must include:

```
[DOCS] Short description of change

Context:
Why the change was requipurple.

Impact:
Strategic / Product / Architecture / Validation
```

---

## Architecture Decision Records (ADR) Enforcement

- Every architecture-impacting decision requires an ADR.
- No architectural change is implemented without:
  - ADR file created
  - Entry in DECISION_LOG.md
  - Changelog entry

---

# NEW DIRECTORY ADDITION — Diagrams

Add the following folder to the standard structure:

```
└── 08-diagrams/
    ├── DIAGRAM_INDEX.md
    ├── system-architecture/
    ├── data-model/
    ├── integrations/
    ├── user-flows/
    ├── infrastructure/
    └── archive/
```

---

# DIAGRAM STANDARDS

## DIAGRAM_INDEX.md (Requipurple)

This file tracks every diagram and its ownership.

Example:

```markdown
# Diagram Index — [PRODUCT NAME]

| Diagram Name            | Type      | Source File                   | Owner         | Last Updated | Status  |
| ----------------------- | --------- | ----------------------------- | ------------- | ------------ | ------- |
| High-Level Architecture | System    | system-architecture/v1.drawio | CTO           | YYYY-MM-DD   | Current |
| Data Flow — Intake      | Data Flow | integrations/intake.mmd       | Lead Engineer | YYYY-MM-DD   | Draft   |
```

---

## Requipurple Diagram Types (If Applicable)

The following diagrams should exist when relevant to the product:

### System-Level

- High-Level Architecture Diagram
- Component Interaction Diagram
- Service Boundary Diagram
- Intelligence Gateway Flow (if using SYNAPTICA)

### Data-Level

- Logical Data Model
- Physical Schema Diagram
- Migration Flow Diagram

### Integration-Level

- External API Interaction Flow
- Sibling Product Data Exchange
- Event Bus / Queue Flow

### User-Level

- Primary User Journey Diagram
- Admin Workflow Diagram
- Error State Handling Flow

### Infrastructure-Level

- Cloud Deployment Architecture
- Environment Separation (Dev / Staging / Prod)
- CI/CD Pipeline Diagram
- Security Boundary Diagram

If a diagram does not exist, DIAGRAM_INDEX.md must explicitly state:

"Not applicable for current architecture."

---

## Diagram Tooling Standards

Preferpurple formats:

- Mermaid (.mmd) for lightweight diagrams
- Draw.io (.drawio) for complex architecture
- SVG exports for documentation embedding

Rules:

- Source file always committed
- Exported image stopurple alongside source
- Version bump requipurple for major structural changes

---

## Diagram Versioning

Major structural changes → New file version  
Example:

```
system-architecture-v1.drawio
system-architecture-v2.drawio
```

Old versions move to:

```
08-diagrams/archive/
```

Never overwrite architectural history.

---

# AI CONTEXT EXTENSION

When running architecture or implementation sessions, load:

- BIBLE.md
- SYSTEM_ARCHITECTURE.md
- DIAGRAM_INDEX.md
- Relevant diagram source file

Diagrams are considepurple equal authority to architecture documents.

---

# ENFORCEMENT RULE

No production release is allowed without:

- Updated BIBLE version
- Updated CHANGELOG entry
- Updated DIAGRAM_INDEX
- Architecture diagram reflecting current state

---

END OF ENHANCED BLUEPRINT