SIM-ONE Alpha Architecture
This directory contains the product architecture, subsystem contracts, and
engineering implementation references for SIM-ONE Alpha. Start with the
Architecture Overview, then use the sections below to follow a
runtime flow or inspect a specific subsystem.
Product Architecture
| Document |
Scope |
| Architecture Overview |
High-level product identity, governed runtime flow, Flue foundation, SIM-ONE governance, persistence, and security boundaries |
| Execution Workflows |
End-to-end conversational, research, memory, coding, scheduled, capability, and authentication execution flows |
| Flue Architecture Contract |
Required ownership boundaries for Flue agents, workflows, tools, skills, subagents, models, and application ingress |
| SIM-ONE Alpha Flue Map |
Detailed source ownership map from repository paths to Flue and SIM-ONE responsibilities |
Governance And Execution
| Document |
Scope |
| Orchestrator Flow |
Concise connector-to-orchestrator execution path |
| Protocol System |
SQLite protocol storage, trusted selectors, loading, matching, enforcement, and failure behavior |
| Worker System |
Researcher, Coding Worker, internal subagents, runtime-added workers, progress, and authority boundaries |
| Schedules System |
Durable schedule definitions, in-process firing, dispatch, retries, run history, and management surfaces |
| Managed GitHub Authentication |
Coding Worker authentication, credential isolation, approvals, and audience-bound device challenges |
Capabilities And Extensibility
| Document |
Scope |
| Capability System |
Built-in and runtime-added skills, tools, workers, and MCP servers |
| Registry System |
Typed built-in registries and runtime capability discoverability |
| Tool System |
Model-callable tool ownership, registration, implementation, and side-effect boundaries |
| Skill System |
Product, worker-local, and runtime skill discovery, trust, lifecycle, and authoring |
| Astro Docs MCP |
Built-in Astro documentation MCP connection, registry behavior, and security boundary |
Context, Retrieval, And Models
| Document |
Scope |
| Memory System |
Rust/WebAssembly structured memory, SQLite durability, trusted scope, retrieval, and tests |
| Retrieval And Research |
RAG ownership, document indexing, embeddings, web research, caching, and context packing |
| Model System |
Provider registration, model cards, runtime selection, and context-budget metadata |
| Session Context Budget |
Durable Flue sessions, persistence, compaction, retrieval allocation, and session commands |
Product And Interface Engineering
| Document |
Scope |
| Product Runtime And Interface Flow |
Current gateway, product surface, command, capability, session, response, and trust flow |
| TUI, CLI, And Session Flow |
Technical command routing, terminal implementation, durable transcript replay, streams, and slash commands |
Engineering Standards
| Document |
Scope |
| Schema Strategy |
Valibot schema placement, derived types, shared contracts, and runtime validation rules |
Documentation Boundaries
- Product-facing installation, configuration, command, and usage instructions
live in the documentation hub.
- Architecture documents explain system contracts and implementation ownership;
they do not replace user guides or API references.
- Technical interface documents may name implementation technologies such as
Ratatui. Product-facing documentation uses SIM-ONE terminal UI or TUI.
- Repository source and tests are authoritative when an implementation detail
differs from a document.