Uvilo OS AGENTS
Purpose
Design, maintain, and reason about the uvilo-os repository structure, naming conventions,
and infrastructure. This is the original system design project.
Read First
- State — current status, completed work, and remaining items
- Spec — authoritative reference for all repo conventions (naming, branching, project layout, agentic execution)
- SKILL.md — agent skill definition for this project
Key Files
| File | Purpose |
|---|---|
Uvilo_OS_State.md | Living todo list and output summary |
Uvilo_OS_Spec.md | Full design spec (15 sections) |
Uvilo_OS_Requirements.md | Original requirements |
Uvilo_OS_Research.md | Architecture research and platform decisions |
Uvilo_OS_History.md | Session history (compressed) |
Uvilo_OS_Postponed.md | Deferred items |
Uvilo_OS_Plan_Infrastructure.md | Railway deployment plan (historical) |
Uvilo_OS_Plan_Shell.md | uvilo-shell MCP server design (historical) |
Uvilo_OS_Plan_Trash_MCP.md | uvilo-trash MCP server design (historical) |
Constraints
- The Spec is the source of truth — always check it before making structural changes
- Many sub-projects have been extracted from Uvilo OS — check
Forge/Projects/for active work - Infrastructure plans are historical; current setup is documented in
Forge/Forge_Infrastructure.md - The
Architecture/top-level folder no longer exists — content was split intoProduct/Projects/andForge/Projects/