SIM-ONE Alpha is a governed, multi-purpose AI employee system built by Gorombo. It combines the Flue agent runtime with the SIM-ONE Framework governance model.
Pre-release boundary: the orchestrator, Protocol Tool, trusted-event lookup, SQLite provider, base protocol records, workers, and approval services are implemented. The complete release policy set, trusted fail-closed pre-execution enforcement, and orchestrator/critic scoring across every path are release gates. See Pre-Release Status.
Flue provides the durable execution architecture. SIM-ONE defines how that architecture applies protocols, context, delegation, scoring, approvals, and memory. SIM-ONE Alpha is the product implementation of both layers.
Gorombo company
SIM-ONE Alpha product and AI employee system
SIM-ONE governance and execution framework
Flue TypeScript agent runtime and harness
sim-one product command
Workers are internal SIM-ONE Alpha executors, not independent products or public agent endpoints.
The complete release flow is:
Terminal / connector / Web API / schedule
-> Secure gateway
-> Trusted normalized event
-> Durable Flue orchestrator session
-> SQLite protocol lookup
-> Orchestrator/critic admission
-> Memory, RAG, tools, workers, workflows, or MCP
-> Structured result returned to orchestrator/critic
-> Protocol scoring and response validation
-> Approval, revision, rejection, or response
The orchestrator is the middleman for every agent action and flow. It owns security, protocol application, governance, delegation, and final validation. Workers perform bounded work and report results back; they do not approve their own work or bypass the orchestrator.
Flue supplies:
SIM-ONE Alpha mounts the Flue runtime behind its gateway and keeps application orchestration out of the HTTP entrypoint.
See:
The SIM-ONE Framework adds the control plane applied around Flue execution:
The protocol database is outside model context. The model receives the applicable protocol bundle through a tool call; it does not author or silently change the governing rules.
See the SIM-ONE Framework for the framework model and protocols.
Protocols are mandatory runtime rules stored in SQLite. They are not skills, prompts, or optional capability instructions.
Protocol matching can use:
connector
actor and user
client
project
task
workflow
message type
priority
enabled state
Chat ingress and orchestrator instructions require loading the applicable bundle before final reasoning, tool execution, delegation, or response generation. Trusted runtime enforcement of that ordering is a release gate.
See Protocol System.
The orchestrator is responsible for:
Workers are specialized executors. The built-in researcher owns source-backed web research. The Coding Worker owns code planning, editing, testing, review, and approval-gated Git and GitHub actions. Internal worker subagents remain private to their owning worker. File-edit approval enforcement is a release gate.
Progress from tool calls, worker handoffs, verification, approvals, and state transitions is emitted as structured runtime activity rather than hidden background work.
See Worker System and Execution Workflows.
SIM-ONE Alpha exposes two capability layers:
| Layer | Contents |
|---|---|
| Built-in Flue layer | Product-shipped skills, tools, workers, workflows, and MCP connections |
| Runtime registry | User- or agent-added skills, tools, workers, and MCP servers |
Enabled runtime capabilities merge into the same governed Flue surfaces as built-ins. They do not override protocols, trusted scope, approvals, or orchestrator validation.
See:
Protocols tell the system which rules apply. Memory and RAG provide the context needed to perform the work.
SIM-ONE Alpha separates:
Structured-memory scope comes from trusted connector, actor, conversation, thread, and project data, not model-selected arguments.
See Memory System and Retrieval And Research.
The gateway owns:
Connectors normalize external messages and return responses through the initiating channel. They do not contain orchestration logic.
Ingress rate limiting is part of the release gateway contract but is not implemented in the current source checkout. It remains a pre-release gate.
See:
Flue SQLite stores durable runtime state such as sessions, submissions, runs, and event streams. SIM-ONE application databases store protocols, logical session metadata, structured memory, schedules, capabilities, retrieval data, and approvals.
Keeping these stores distinct allows Flue to resume execution while SIM-ONE Alpha controls rules, context, identity, and product-owned state.
SIM-ONE Alpha applies security at multiple boundaries:
DM pairing, allow lists, API authentication, and connector permissions protect ingress. The architectural difference is that the orchestrator remains the governing authority between every admitted request and every executable action.