01 Prompt lifecycle
Before Prompt starts, tool calls, file touches, and completions blur together.
After Lifecycle markers can become reviewable local mission state.
Boundary Lifecycle markers do not mean prompt bodies upload by default.
Power users
Keep local agent work visible while you stay in control.
Use mission state, prompt lifecycle markers, approvals, replay context, and diagnostics without turning the public site into a runtime shell.
Power users need fast local feedback and enough structure to revisit decisions, troubleshoot gaps, and keep risky steps visible.
Before and after
What changes for Power Users.
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.
-
- 02 Approvals
Before Risky moments depend on memory or raw terminal context.
After Approval and review surfaces can keep the next decision visible.
Boundary The website cannot grant approvals or bypass local tool trust prompts.
- 03 Diagnostics
Before Missing hook events or broken local setup produce confusing gaps.
After Diagnostics can show failure posture and setup health explicitly.
Boundary Diagnostics must avoid exposing raw secrets, env values, or local paths.
- 04 Replay and demo
Before It is hard to revisit what happened or inspect the product before setup.
After Replay is local product context, and the public demo remains a synthetic preview.
Boundary The zero-install demo is synthetic and separate from real local sessions.
Relevant surfaces
Surfaces with explicit boundaries.
These mappings distinguish local runtime behavior, optional collaboration, outbound-only adapters, static demo previews, and docs-owned setup detail.
CLI
apps/cli
Local commands keep setup, validation, and operator posture close to the terminal.
Guardrail Command examples on the website are static and cannot run on behalf of visitors.
Read Docs (external link)Cockpit
apps/web cockpit
Mission state, replay context, approvals, and diagnostics become inspectable locally.
Guardrail Cockpit state is local runtime behavior when the install is running.
FeaturesDemo
synthetic public demo
A zero-install preview lets power users inspect the feel before local setup.
Guardrail The zero-install demo is synthetic and separate from real local sessions.
Open Demo (external link)Proof examples
Static examples, not live telemetry.
The examples show product meaning and review posture while keeping demo data, local runtime data, and public website copy separate.
Prompt and tool state
Prompt lifecycle and tool activity can be reviewed as bounded local events.
- Evidence
- Useful when a power user wants to understand why work moved forward.
Boundary Do not expose prompt bodies, secrets, or source files by default.
Approval posture
Approval and replay surfaces keep high-friction moments visible.
- Evidence
- Useful when a local operator wants context before continuing risky work.
Boundary Public website copy is descriptive and cannot change local tool permissions.
Power user path
Try the synthetic preview, then read the setup docs.
Synthetic zero-install demo hosted separately from this website. Use features to compare control surfaces and docs for the local setup path.
Boundary The demo and docs are separate external destinations. They do not create an account or upload your local agent state by default.