Agent infrastructure can become a pile of provider-specific logs and scripts. FactionOS gives platform teams a shared vocabulary for event shape, diagnostics, and optional handoffs while keeping integration direction and trust boundaries visible.
AI platform teams
A provider-neutral event story with clear integration guardrails.
Align hooks, protocol fields, diagnostics, and outbound adapters without implying inbound command channels or hosted control.
AI platform teams need event visibility and integration boundaries that can survive provider differences and local-first trust requirements.
- Focusprotocol
The problem
Where the work loses its shape.
Before and after
What changes with an operating picture.
Provider events
Before
Each agent surface reports different lifecycle fields and failure modes.
With FactionOS
Compatible producers can speak a shared protocol shape for structured local events.
Compatible producers can use the generic event API shape.
Diagnostics
Before
Hook, server, and adapter failures are hard to distinguish from missing activity.
With FactionOS
Diagnostics can expose setup health, event flow, and failure categories.
Diagnostics output must stay sanitized and avoid raw credentials or local secrets.
Event visibility
Before
Platform teams depend on broad logs to explain what happened.
With FactionOS
Mission, lifecycle, tool, file, validation, and review states stay structured.
Structured events do not mean prompt bodies or source files upload by default.
Outbound handoff
Before
External automations can blur into remote control or analytics.
With FactionOS
Adapters remain optional outbound notices with explicit payload scope.
Adapters are not inbound command channels or remote executors.
Surface mapping
Which surface does the job.
Availability and guardrail columns keep local, optional, and outbound clearly separated.
| Capability | Surface | Availability | Guardrail |
|---|---|---|---|
| Protocol | packages/protocolTyped event and state contracts keep producers, server, adapters, and UI aligned. | local | Protocol examples avoid user-provided code or secrets. |
| Hooks | Claude Code, Codex CLI, compatible producersHooks describe local workflow events without replacing provider auth or trust settings. | local | Provider setup remains operator-controlled and explicit. |
| Adapters | apps/adaptersDiscord, Telegram, and generic HTTPS adapters are optional outbound paths. | outbound | Outbound-only means no inbound commands from external systems. |
Operator proof
How this path shows up in the cockpit.
Contract
Structured event field set
Lifecycle, mission, review, validation, and diagnostic fields can be named explicitly.
Evidence Useful when platform teams compare event producers without normalizing raw logs.
Field examples are descriptive and avoid user-provided data.
Guardrail
Outbound adapter posture
Adapter payloads should remain narrow status notices after an operator enables them.
Evidence Useful when integrating team chat without turning chat into command control.
No inbound command or automatic background upload.
Boundaries
What stays true for this role.
- outboundDirection
Adapters are described as outbound-only notices, not remote command channels.
- scopedProvider
Provider-neutral copy does not promise full compatibility with every agent provider.
Platform path
Follow the hook-to-cockpit flow.
Use the how-it-works page for pipeline shape, the docs for setup detail, and the product page for surface boundaries.
Complete setup and provider trust review belong in operator-controlled local tooling and public docs.