Engineering teams
Give operators a mission picture for parallel agent work while keeping prompts, paths, credentials, and review state local by default.
Engineering teams need a common way to understand what agents are doing, where review is needed, and which local signals support a change.
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 Status is inferred from terminal scrollback, chat updates, or stale PR notes.
After A local cockpit can summarize active lanes, mission posture, and review checkpoints.
Boundary Cockpit visibility is product runtime behavior, not a live public website feed.
Before Reviewers ask what changed, which tool ran, and why an agent moved to the next step.
After File, tool, validation, approval, and lifecycle signals stay attached to the mission.
Boundary Signals must stay bounded and avoid raw secrets, full source, or broad path dumps.
Before Planner, builder, and reviewer agents drift because ownership is not visible.
After Lanes, subagent lineage, and checkpoints give operators a shared map.
Boundary Lineage is event context, not a promise that every external provider is supported.
Before Broken hooks or validation gaps become invisible until someone audits manually.
After Diagnostics and validation state surface as visible local product signals.
Boundary Diagnostics copy must expose failure states without leaking sensitive output.
Relevant surfaces
These mappings distinguish local runtime behavior, optional collaboration, outbound-only adapters, static demo previews, and docs-owned setup detail.
Cockpit
Mission lanes, agent roster, review state, and bounded timeline context.
Guardrail Not a hosted workspace or team account surface.
FeaturesHooks
Prompt lifecycle, tool activity, validation, and file-touch signals become local events.
Guardrail No default upload of prompt bodies, credentials, or source files.
How It WorksWar Room
A team-readable mission view can exist only when deliberately configured.
Guardrail War Room collaboration is optional and separate from the local baseline.
SecurityProof examples
The examples show product meaning and review posture while keeping demo data, local runtime data, and public website copy separate.
A mission row can show owner, status, validation state, and next review action.
Boundary Example rows are authored copy and are not live team telemetry.
Role copy keeps prompt bodies, local paths, credentials, and source code out of website claims.
Boundary Local-first behavior is the baseline unless a later integration is explicit.
Team path
Use product and features pages to compare the local cockpit and review surfaces, or open the external demo to inspect a synthetic version of the flow.
Boundary The zero-install demo is synthetic and separate from real local sessions. It is not a hosted customer workspace, analytics stream, or team-management surface.