Cockpit
Cockpit navigation
Top-level lanes let operators move between missions, agents, review states, settings, and diagnostics.
- Surface
- apps/web cockpit
- Guardrail
- Navigation is runtime UI, not a hosted account surface.
Feature inventory
Agent work you can review while it happens.
Cockpit visibility, review control, lineage, and outbound notifications stay separated by boundary.
The features page turns the product overview into concrete capability groups: what the local cockpit shows, where approvals and replay fit, how subagent work is traced, and which optional outputs leave the machine only when configured.
Capability matrix
Scan features by workflow, surface, and boundary.
The matrix keeps cockpit, mission, review, orchestration, adapter, export, and audit capabilities concrete. Each row includes the owned surface and a guardrail so capability copy does not drift into hosted-service or execution claims.
Cockpit
Live roster
Active agent and lane posture is visible as bounded status instead of hidden background work.
- Surface
- apps/web cockpit
- Guardrail
- Roster state is local runtime state when the local install is running.
Missions
Mission feed
Mission rows group lifecycle, review, and validation activity so operators can scan active work.
- Surface
- apps/web cockpit
- Guardrail
- Feeds summarize bounded events and do not turn the website into live telemetry.
Missions
Battlefield map
The visual map gives product context for agents, work zones, alerts, and tactical state.
- Surface
- apps/web and demo
- Guardrail
- The zero-install demo is synthetic and separate from real local sessions.
Missions
Mission detail
A focused mission view keeps objectives, current state, files, and follow-up signals together.
- Surface
- apps/web cockpit
- Guardrail
- Details should stay bounded and avoid exposing secrets or full raw transcripts by default.
Review
Replay
Replay helps revisit a local sequence of events and decisions without implying public replay hosting.
- Surface
- apps/web cockpit
- Guardrail
- Replay data is local product state unless an explicit later integration says otherwise.
Review
Approvals
Review gates keep risky actions and checkpoints visible to the operator before work proceeds.
- Surface
- apps/web cockpit
- Guardrail
- This page does not grant approvals or bypass local tool trust prompts.
Review
File and tool timelines
File touches and tool activity are grouped as reviewable event context instead of free-form log sprawl.
- Surface
- protocol and cockpit
- Guardrail
- Timeline copy must avoid displaying credentials, raw source, or broad local paths.
Review
Prompt lifecycle
Prompt start, tool use, completion, and validation markers become lifecycle state for review.
- Surface
- hooks and protocol
- Guardrail
- Lifecycle markers do not mean prompt bodies are uploaded by default.
Trust
Diagnostics
Health, validation, and hook status signals help spot broken local setup or missing events.
- Surface
- CLI, server, cockpit
- Guardrail
- Diagnostics should produce explicit failure states rather than silent gaps.
Trust
Settings
Local preferences and reset affordances keep operator control visible without claiming full erasure.
- Surface
- apps/web cockpit
- Guardrail
- Settings are not a broad trusted erasure claim or hosted identity control.
Orchestration
Orchestration deck
Planner, builder, and review lanes can be compared so parallel work stays understandable.
- Surface
- apps/web cockpit
- Guardrail
- Orchestration visibility does not imply remote execution from the website.
Orchestration
Subagent lineage
Subagent handoffs and parent-child work context stay attached to the mission story.
- Surface
- protocol and cockpit
- Guardrail
- Lineage is event context, not a claim that every external agent provider is supported.
Adapters
Outbound adapters
Discord, Telegram, and generic HTTPS adapters are optional outbound paths. Each adapter sends narrow notifications only when enabled.
- Surface
- apps/adapters
- Guardrail
- Adapters are outbound notifications only, not inbound commands or remote execution.
Export
Export
Export paths support review and handoff without turning the website into hosted storage.
- Surface
- local product surface
- Guardrail
- Exports remain local or explicitly operator-directed.
Trust
Audit trail
Bounded event history helps explain what happened, what changed, and where review occurred.
- Surface
- protocol and cockpit
- Guardrail
- Audit wording must avoid certification or compliance claims this release does not own.
Workflow groups
Capabilities grouped by the operator job they support.
Feature groups keep the copy tied to observable workflow jobs: watching active work, reviewing risky moments, understanding multi-agent lineage, and deciding what leaves the local machine.
Cockpit
See the active mission without reading every log line.
Cockpit surfaces translate local hook and server state into mission, roster, battlefield, and detail views that an operator can scan during real work.- Navigation and roster Move between mission lanes, active agents, alerts, settings, and diagnostics with local runtime context.
- Mission feed and map Use feed rows and battlefield state to understand active work without treating demo data as live telemetry.
- Mission detail Keep objectives, state, file/tool context, and next review action together for one mission.
Boundary The public site describes these surfaces. It does not connect to a visitor workspace, collect local state, or open runtime streams.
Review
Turn lifecycle noise into checkpoints an operator can inspect.
Prompt lifecycle, approvals, replay, file timelines, and tool timelines keep review state explicit while limiting what needs to be exposed.- Prompt lifecycle Represent prompt started, tool requested, file touched, validation completed, and failure markers as bounded events.
- Approvals and replay Keep high-friction moments visible without implying this website approves tools or hosts replay data.
- File and tool timelines Show review context as grouped activity while avoiding secret values, broad paths, or raw source by default.
Boundary Review features depend on local product runtime behavior. Website examples are static and cannot authorize commands.
Orchestration
Track parallel agent work by lane, mission, and lineage.
FactionOS is built for multi-agent coordination where planner, builder, reviewer, and subagent work should remain tied to one operating picture.- Orchestration deck Compare lane ownership, progress, and review posture across simultaneous local agent work.
- Subagent lineage Preserve parent-child context and handoffs so delegated work remains explainable.
- Diagnostics Surface hook, server, and validation health so missing events do not become invisible failures.
Boundary Orchestration visibility is not a remote executor claim. Remote control remains out of scope without a later threat model.
Handoffs
Send only the outputs an operator has chosen to send.
Outbound adapters, export paths, and audit trails make handoff deliberate, narrow, and reviewable instead of ambient telemetry.- Outbound adapters Discord, Telegram, and generic HTTPS adapters are optional outbound paths.
- Export Prepare local or operator-directed handoff material without claiming hosted storage by default.
- Audit trail Preserve event history for review without claiming a security certification or full compliance program.
Boundary Adapters do not become inbound command channels, website analytics, background upload, or remote execution.
Next
Compare the product map, then inspect the demo.
Use the product overview for surface boundaries, the how-it-works page for the hook pipeline, and the external demo for a synthetic preview. Synthetic zero-install demo hosted separately from this website.
Boundary External demo and docs destinations are separate sites. Internal links remain static pages, not account or telemetry actions.