Files

Ezra (Archivist) 1411fded99 [BURN] Matrix scaffold verification, room bootstrap automation, cutover plan

- Verify #183 scaffold completeness (MATRIX_SCAFFOLD_VERIFICATION.md)
- Add bootstrap-fleet-rooms.py for automated Matrix room creation (#166)
- Add CUTOVER_PLAN.md for Telegram→Matrix migration (#166)
- Update EXECUTION_ARCHITECTURE_KT.md with new automation references

Progresses #166, verifies #183

2026-04-05 18:42:03 +00:00

caddy

Add Caddy reverse proxy configuration for Matrix (#183 )

2026-04-05 00:08:31 +00:00

conduit

[ezra] Environment template for Conduit (#183 )

2026-04-05 05:10:55 +00:00

docs

[ezra] ADRs + Execution KT for Matrix/Conduit (#183 , #166 )

2026-04-05 18:20:46 +00:00

scripts

[BURN] Matrix scaffold verification, room bootstrap automation, cutover plan

2026-04-05 18:42:03 +00:00

.env.example

Add Conduit environment variable template (#183 )

2026-04-05 00:06:14 +00:00

conduit.toml

Add Conduit configuration scaffold (#183 )

2026-04-05 00:06:13 +00:00

deploy-matrix.sh

Add Matrix deployment script (#183 )

2026-04-05 00:07:06 +00:00

docker-compose.yml

Add Conduit Docker Compose configuration (#183 )

2026-04-05 00:06:12 +00:00

EXECUTION_RUNBOOK.md

[ezra] #166 : Master execution runbook for Matrix/Conduit deployment

2026-04-05 12:46:02 +00:00

GONOGO_CHECKLIST.md

docs: add Matrix deployment go/no-go checklist (#166 unblocking artifact)

2026-04-05 17:30:47 +00:00

host-readiness-check.sh

Add host readiness checker for Matrix/Conduit deployment (#166 )

2026-04-05 12:16:16 +00:00

prerequisites.md

Add Matrix/Conduit prerequisites documentation (#183 )

2026-04-05 00:05:25 +00:00

README.md

Add Matrix/Conduit deployment scaffold README (#166 , #183 )

2026-04-05 00:05:24 +00:00

SCAFFOLD_INVENTORY.md

[ezra] #183 : Canonical scaffold inventory and audit

2026-04-05 12:46:01 +00:00

README.md

Matrix/Conduit Deployment Scaffold

Parent: #166 | Scaffold task: #183

This directory contains an executable deployment path for standing up a Matrix homeserver (Conduit) for sovereign human-to-fleet encrypted communication.

Status

Component	State
Deployment scaffold	✅ Present
Target host	⚠️ Requires selection
Reverse proxy (Caddy/Nginx)	⚠️ Pending host provisioning
TLS certificates	⚠️ Pending DNS + proxy setup
Federation	⚠️ Pending DNS SRV records
Fleet bot integration	⚠️ Post-deployment

Quick Start

cd /path/to/timmy-config/infra/matrix
# 1. Read prerequisites.md — ensure host is ready
# 2. Edit conduit.toml with your domain
# 3. Copy .env.example → .env and fill secrets
# 4. Run: ./deploy-matrix.sh

Architecture

┌─────────────────────────────────────────────────────────────┐
│                        Host (VPS)                           │
│  ┌─────────────────┐      ┌──────────────────────────────┐  │
│  │  Caddy/Nginx    │─────▶│  Conduit (Matrix homeserver) │  │
│  │  :443/:8448     │      │  :6167 (internal)            │  │
│  └─────────────────┘      └──────────────────────────────┘  │
│           │                            │                    │
│           ▼                            ▼                    │
│     TLS termination          SQLite/RocksDB storage         │
│     Let's Encrypt            Config: conduit.toml           │
└─────────────────────────────────────────────────────────────┘

Files

File	Purpose
`prerequisites.md`	Host requirements, ports, DNS, decisions
`docker-compose.yml`	Conduit + optionally Element-Web
`conduit.toml`	Homeserver configuration scaffold
`deploy-matrix.sh`	One-command deployment script
`.env.example`	Environment variable template
`caddy/Caddyfile`	Reverse proxy configuration

Post-Deployment

Create admin account via registration or CLI
Create fleet rooms (encrypted by default)
Onboard Alexander as operator
Deploy fleet bots (Hermes gateway with Matrix platform adapter)
Evaluate Telegram-to-Matrix bridge (mautrix-telegram)

Decisions Log

Homeserver: Conduit (lightweight, Rust, single binary, SQLite default)
Database: SQLite for single-host; migrate to PostgreSQL if scale demands
Reverse proxy: Caddy (automatic HTTPS) or Nginx (existing familiarity)
Client: Element Web (optional, self-hosted) + native apps
Federation: Enabled (required for multi-homeserver fleet topology)