AI platform teams
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.
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 Each agent surface reports different lifecycle fields and failure modes.
After Compatible producers can speak a shared protocol shape for bounded local events.
Boundary Compatible producers can use the generic event API shape.
Before Hook, server, and adapter failures are hard to distinguish from missing activity.
After Diagnostics can expose setup health, event flow, and failure categories.
Boundary Diagnostics output must stay sanitized and avoid raw credentials or local secrets.
Before Platform teams depend on broad logs to explain what happened.
After Mission, lifecycle, tool, file, validation, and review states stay structured.
Boundary Structured events do not mean prompt bodies or source files upload by default.
Before External automations can blur into remote control or analytics.
After Adapters remain optional outbound notices with explicit payload scope.
Boundary Adapters are not inbound command channels, remote executors, or visitor analytics.
Relevant surfaces
These mappings distinguish local runtime behavior, optional collaboration, outbound-only adapters, static demo previews, and docs-owned setup detail.
Protocol
Typed event and state contracts keep producers, server, adapters, and UI aligned.
Guardrail Protocol examples must avoid visitor-provided code or secrets.
How It WorksHooks
Hooks describe local workflow events without replacing provider auth or trust settings.
Guardrail Provider setup remains operator-controlled and explicit.
Read Docs (external link)Adapters
Discord, Telegram, and generic HTTPS adapters are optional outbound paths.
Guardrail Outbound-only means no inbound commands from external systems.
SecurityProof examples
The examples show product meaning and review posture while keeping demo data, local runtime data, and public website copy separate.
Lifecycle, mission, review, validation, and diagnostic fields can be named explicitly.
Boundary Field examples are descriptive and do not expose visitor data.
Adapter payloads should remain narrow status notices after an operator enables them.
Boundary No inbound command, analytics, or automatic background upload claim.
Platform path
Use the how-it-works page for pipeline shape, the docs for setup detail, and the product page for surface boundaries.
Boundary Examples on the website are static. Complete setup and provider trust review belong in operator-controlled local tooling and public docs.