FactionOS
Open Demo(external link)Read Docs(external link)

Product overview

The FactionOS surface map.

Local command, visible agent work, optional team signals.

FactionOS connects hook events, a local server, the web cockpit, command-line workflows, and shared protocol contracts. War Room collaboration is optional and separate from the local baseline. Discord, Telegram, and generic HTTPS adapters are optional outbound paths.

  • Defaultlocal-first
  • Controloperator-led
  • Adaptersoptional
Open Demo (external link)Read Docs (external link)

Core workflows start locally; external demos, docs, and adapters are separate, intentional actions.

At a glance

Seven surfaces, one local baseline.

Surfaces
7

Local, optional, outbound, and demo surfaces shown separately.

Runtime baseline
Local

Hooks, server, CLI, and cockpit start on the operator machine.

Transfer
Explicit

External destinations and adapters stay deliberate.

Surface map

Every surface, shown separately.

Local, optional, outbound, demo, and docs paths stay clear so operators know exactly what they are using.

Cockpit

Web cockpit

shipped localOperator view for active agent work.

A local browser surface for watching missions, agent lanes, lifecycle events, and review state.

  • Mission and lane visibility for parallel agent work.
  • Status rings and structured timeline rows instead of raw terminal scrollback.
  • Review checkpoints that keep task intent visible.

Local state is read when the installed product runtime is running.

See cockpit features

Ingest

Hook event pipeline

shipped localSource of local workflow signals.

Development hooks turn prompt lifecycle markers, tool activity, file-touch signals, and validation outcomes into structured local events.

  • Lifecycle events become structured records.
  • File and command signals stay attached to local context.
  • Failures can be shown as visible states rather than silent gaps.

Hook ingest starts on the operator machine; prompts, paths, credentials, and source files stay local by default.

Follow the ingest flow

Control

CLI

shipped localDeveloper entry point and local control plane.

Command-line workflows let operators run, inspect, and validate local FactionOS behavior from the same terminal context as the codebase.

  • Start and inspect local product surfaces.
  • Run validation gates close to the workspace.
  • Keep operator actions explicit instead of invisible automation.

Operators run CLI actions deliberately from their own terminal context.

Review setup flow

Contract

Protocol

shipped localTyped connective tissue between surfaces.

Shared event contracts keep hooks, server state, adapters, and UI surfaces aligned as product boundaries become more complex.

  • Consistent event names and payload shapes.
  • Clear separation between local snapshots and optional outbound notices.
  • Reduced drift between CLI, server, cockpit, and adapters.

Protocol descriptions keep payload expectations explicit without exposing repository content.

Inspect the architecture

Collaboration

Optional War Room

optional localOptional shared view for coordinated work.

A collaboration surface can summarize team-visible mission state when deliberately enabled, with redaction and service boundaries treated as product requirements.

  • Team-readable mission state when configured.
  • Redaction posture belongs next to collaboration controls.
  • Local-only operation remains the baseline product story.

War Room collaboration is optional and separate from the local baseline. Local-only operation remains the baseline.

Review trust boundaries

Notifications

Outbound adapters

outbound optionalOptional external notification path.

Discord, Telegram, and generic HTTPS adapters are optional outbound paths. They can send narrow notifications to external systems such as team chat or downstream automation after an operator opts in.

  • Payloads must be explicit and narrow.
  • External destinations remain separate from core local work.
  • Operators control whether a notification path exists.

Adapters stay outbound-only in this overview. Operators control whether a notification path exists.

Compare adapter scope

Preview

Guided demo

guided previewZero-install product preview.

The public demo is a separate guided preview for inspecting product feel without setup.

  • Product-like UI without local setup.
  • Product-like flow for public inspection.
  • Clear separation from real prompts, paths, and replay data.

The zero-install demo is a guided preview and stays separate from local sessions.

Understand demo scope

Operating model

Local-first by default, explicit when a signal leaves.

Local-first by default for the core workflow. Product surfaces coordinate local events, cockpit state, and optional notifications without hiding where a signal goes.

  1. Hook ingest captures a compact event.

    A CLI or editor hook records a lifecycle marker such as prompt started, tool requested, file touched, or validation completed.

    In Developer workflow signalOut Structured local event

    No prompt body, path list, credential, or source file is uploaded by default.

  2. The local server normalizes state.

    The local FactionOS server accepts the event, aligns it to the protocol contract, and prepares a small snapshot.

    In Structured local eventOut REST snapshot

    The server belongs to the installed product runtime.

  3. The cockpit refreshes operator visibility.

    A local browser cockpit can read snapshots and stream updates through WebSocket behavior when the runtime is installed.

    In State changeOut Mission and lane update

    Live streams and replay belong to the installed product runtime.

  4. Optional outbound notifications stay explicit.

    If configured, an adapter can send a narrow status notice to an external destination under that adapter contract.

    In Operator-approved stateOut External notice if enabled

    Adapters are optional, outbound-only, and operator-approved.

Held local by default

  • no upload
    Prompts

    Prompt bodies are not part of the default public-site workflow.

  • local scope
    Local paths

    Repository paths and file names remain local unless an operator chooses an explicit integration.

  • sample only
    Terminal output

    Terminal transcripts stay in the operator environment.

  • preview
    Replay data

    The demo and preview panels stay separate from real replay data.

  • never asked
    Credentials

    Secrets and tokens are not requested by this public page.

  • not read
    User code

    User-provided source code stays outside the public-site workflow.

Product proof

Command surfaces you can inspect.

Mission boards, hook queues, CLI rails, adapters, and previews show how FactionOS organizes agent work.

Mission board

Cockpit mission board

shipped local

A mission board can show lanes, statuses, and review checkpoints when the local runtime is installed.

Lanes
3

Planner, builder, and review lanes.

State
structured

Status summaries instead of raw logs.

The board shows lane shape, status, and review context.

Local event lane

Hook ingest queue

shipped local

Hook events normalize local lifecycle signals before the cockpit reads state.

Input
hook event

Local lifecycle marker.

Output
snapshot

Structured state for UI consumption.

Prompt bodies, paths, credentials, and user code stay out of the public preview.

Operator rail

CLI operator rail

shipped local

The CLI keeps local setup and validation commands close to the development workflow.

Mode
local

Operator-run commands.

Visibility
explicit

Operator actions stay visible.

Terminal actions stay operator-run and explicit.

Protocol lane

Protocol contract lane

shipped local

Shared contracts keep event names and payload expectations aligned across surfaces.

Shape
typed

Named event and state fields.

Drift
reduced

One contract vocabulary across surfaces.

Contract examples keep event names and payload expectations clear.

Optional shared surface

War Room collaboration

optional local

A team view can expose mission posture after redaction and service boundaries are configured.

Default
off

Local baseline remains primary.

Posture
redacted

Shared state must stay intentionally narrow.

Optional collaboration is not a default hosted account or public replay guarantee.

Adapter sample

Outbound notification path

outbound optional

Adapters can publish narrow status messages to chosen destinations when an operator enables them.

Direction
outbound

Explicit external notice.

Trigger
operator

Operator-approved path.

Adapters are outbound notifications only here, not inbound control or analytics channels.

Public preview

Guided public demo

guided preview

The demo lets readers inspect a product-like surface before installing anything.

Mode
guided

Product preview rows.

Runtime
separate

External demo destination.

The demo stays separate from real local sessions and replay data.

Next step

Inspect the demo, then keep the docs open.

Zero-install product preview hosted separately from this website. Use the public docs for setup context. The related pages split deeper details into features, workflow, and trust boundaries.

Open Demo (external link)Read Docs (external link)

Demo and docs open as separate destinations. Local product state remains under operator control.