Dev Docs

Internal development documentation for Legio v3. These are frozen historical records — snapshots of decisions, plans, and research at the time they were written.

Structure

Folder	Purpose
Plans	Implementation plans, design documents, and work item breakdowns
Notes	Research notes, architecture explorations, and technical investigations
Memos	Standing reference material — vocabulary, conventions, patterns
Fixes	Audit reports and fix logs

Naming Convention

All dev-docs follow the pattern:

{YYYYMMDD}-{HHMM}-{brief-name}.md

Date-time of creation, 2-4 hyphenated words. Files are never modified after implementation — they serve as historical records.

Plans

• Legio v3 Design — The complete v3 implementation plan with 33 decisions
• Telegram UX Plan — Full UX plan with mission scoping and TOTP authorization
• Telegram UX Design — UX design research: commands, attribution, threading
• Telegram UX Implementation — Refined implementation plan with work items A-G
• Telegram Interactive Mode — Feasibility study for Claude Code features via Telegram
• Aerarium Cost Tracking — Token and USD cost tracking module design

Notes

• Filesystem Architecture — Three-layer model: code, blueprints, castra
• Headless Browser Research — Browser automation solutions for centuriones
• Telegram Markdown Rendering — Strategies for rendering LLM markdown in Telegram
• Telegram Reply Context — Passing quoted message context to the LLM on swipe-replies
• claude-flow Research — Investigation of ruvnet/claude-flow and enrichment potential for Legio
• Chat History Management — Dual-history model, gaps, and multi-agent design decisions

Memos

• Domain Vocabulary — Complete Roman-to-English term mapping
• Website Components — YouTube and Audio embed components

Fixes

• Audit Fix Report — Comprehensive audit findings and fix plan