Founders
Show the product wedge clearly: local mission control for agent work, a synthetic demo for exploration, and docs for setup context.
Founders need to understand whether FactionOS makes agent work more controllable without leaning on unverifiable traction, ROI, or productivity metrics.
Before and after
Each row keeps the pain point, the FactionOS path, and the implementation boundary together so role copy does not turn into a broad hosted-service claim.
Before Parallel agents create progress without a single operating picture.
After A mission view can keep lanes, lineage, status, and checkpoints visible.
Boundary No remote execution or hosted production validation claim is made.
Before Agent tooling reads as another terminal helper or generic dashboard.
After FactionOS is positioned as local mission control for agent coding work.
Boundary Copy stays concrete and avoids ROI, speed, or traction metrics.
Before Visitors need a way to inspect the product feel before setup.
After The external demo shows a synthetic product-like preview.
Boundary The zero-install demo is synthetic and separate from real local sessions.
Before Agent autonomy can look impressive while review risk remains vague.
After Approval, replay, and diagnostic language keeps control points visible.
Boundary The website cannot grant approvals, run tools, or validate production hosts.
Relevant surfaces
These mappings distinguish local runtime behavior, optional collaboration, outbound-only adapters, static demo previews, and docs-owned setup detail.
Cockpit
The primary product surface for seeing missions, lanes, and review state.
Guardrail Cockpit behavior is local product runtime, not this static route.
ProductDemo
A separate synthetic preview for inspecting product feel without setup.
Guardrail The zero-install demo is synthetic and separate from real local sessions.
Open Demo (external link)Docs
Public docs own setup context, runtime details, and validation guidance.
Guardrail Docs are separate from the website and do not create hosted accounts.
Read Docs (external link)Proof examples
The examples show product meaning and review posture while keeping demo data, local runtime data, and public website copy separate.
The product story stays centered on local visibility, review, and coordination.
Boundary No productivity percentage, ROI, or traction claim is included.
Visitors can open the demo to inspect a product-like surface without setup.
Boundary The demo does not connect to local state or hosted customer data.
Founder path
Synthetic zero-install demo hosted separately from this website. Use the product page for surface boundaries, and the docs when you want setup detail.
Boundary This path is for exploration. It does not imply a hosted account, analytics dashboard, customer workspace, or quantified outcome.