Who it's for
Platform engineer or founding SRE who wants a local evaluator path before paying for signed live events.
Offline CI — prove the mesh without Docker
Run committed scenario tests for ingest, linking, and agent eval without Docker or live connectors. Prove the harness on fixtures first. Wire PagerDuty and GitHub when you want signed events. Slack waits. Create a workspace when ready.
The problem
Teams jump to Docker compose and live connectors before they know whether ingest, linking, and agent eval pass. The harness is unproven; committed fixture legs never ran.
Outcome
A local evaluator path: committed scenario tests for ingest, linking, and agent eval without Docker or live connectors. Prove the harness on fixtures first, then wire PagerDuty and GitHub when you want signed events on the paid mesh.
Multi-horizon BI
Offline CI is the local evaluator path before live pulses: fixture ingest, link, and agent-eval first; signed events later.
Real-time
Committed scenario fixtures for ingest, linking, and agent eval — no live connector pulse required.
Short-term
Re-run the same fixture legs as you change harness code; prove pass/fail before paying for signed events.
Long-term
When the harness is proven, wire PagerDuty and GitHub for signed events on the paid mesh. Slack waits.
Local fixture proof before live ingress is how you avoid a connector pilot that cannot tell ingest from linking from eval.
Workflow map (2026)
Local smoke for ingest, linking, and agent eval — no Docker, no live connectors. Prove the harness before the first signed event.
Platform engineerFounding SREEval harness owner
Build
Committed scenario fixtures for ingest, linking, and agent eval — no Docker, no live connectors.
Steer
Prove the harness on fixtures before the first signed event.
Compound
Wire PagerDuty and GitHub later for signed events on the paid mesh. Slack waits. Create a workspace when you are ready.
Learning loop
Prove fixtures first. Wire PagerDuty and GitHub when you want signed events. Slack waits.
Questions agents answer
- Did the ingest fixture leg pass without Docker?
- Did linking join the planted fixture rows?
- Did agent eval find the planted needle on committed testdata?
How it works on I/O Mesh
Step 1
Run committed fixtures
Execute the ingest, linking, and agent-eval scenario tests on committed testdata — no Docker compose and no live connectors.
Step 2
Prove the harness first
Treat fixture pass/fail as the first proof. Do not start with signed webhook ingress until those legs are green.
Step 3
Wire PagerDuty and GitHub later
When you want signed events on the paid mesh, connect PagerDuty then GitHub. Slack waits — it is not a ships-today step on this path.
Step 4
Create a workspace when ready
Open console signup and create a workspace once the local harness is proven and you want the paid mesh.
Departments
- Engineering
- Platform
Operational mesh
dept.* stream patterns
- dept.engineering.events.pagerduty
- dept.engineering.events.github
What ships today
- Local scenario tests for ingest, linking, and agent eval
- No Docker and no live connectors required to prove the harness
- Committed fixtures as the first proof
- PagerDuty and GitHub as a later step for signed events on the paid mesh
- Typical company stage
- enterprise
- Evaluation path
- Prove ingest, link, and agent-eval fixtures locally. Wire PagerDuty and GitHub when you want signed events. Slack waits. Create a workspace when ready.
Related solutions
B2B SaaS
PLG-to-enterprise learning loops across engineering, product, sales, CS, and support — governed dept.* products agents can consume, not a company-wide vector dump.
Platform engineering and SRE
AI-SRE-ready context plane for incidents, deploys, and on-call evidence as governed dept.* products — agents investigate with lineage, not another alert chat box.
Start compounding this workflow — create a workspace with the use case pre-selected.
Create a workspace Explore platform Browse all use cases