Engineering team
Build faster. Ship safer. Keep ownership.
Delivery data lives in five systems and nobody agrees on "how often do we deploy" or "what's our failure rate." An engineering team uses OpenX to crystallize those into shared sources of truth any agent can read and build on - while keeping what ships a human call.
1. Connect your delivery data
Add a connection fed by your deploy/CI events and route it onto a Delivery surface (a simulator
stands in while you wire the real feed).
2. Crystallize the metrics
run_adhoc_warm_query, then proposes deploys-per-day + change-failure-rate via manage_proposals; you accept.3. Read from any AI - in your editor
Install the workshop into your agents (fai mcp install …/oi-api/mcp). Now Cursor, Claude Code, or a
local model answers "what's our change-failure rate this week?" against the same source of truth - in
the editor, no dashboard hunt.
4. Build the next - reviewed
Ask your agent to "add a feed for incident counts and combine it with deploys." It proposes the new connection + combined query; you accept in the portal. Building is open to any agent; what goes live is your team's call - the confidence layer.
THE BOUNDARY
Open to build, human to ship
Any agent can propose - new feeds, new queries, wiring. There is no accept tool over MCP by design. You ship fast and keep control.
5. Compound
Every accepted query is shared, versioned, and reachable by every teammate's AI. The metrics stop being arguments. Next: Enterprise team.