Operator Guides¶
AIT has three peer tools and one workbench:
- Seam observes and rewrites traffic.
- meshmapper turns saved artifacts into deterministic targeting hypotheses.
- Assay optionally validates impact claims with oracle evidence.
- ait coordinates complete workflows and records run artifacts.
Operate, Map, Validate¶
Use the tools in this order for most work:
- Operate with Seam. Produce schema-valid transcripts, trace rules, and rewrite complete decoded messages.
- Map with meshmapper. Ingest transcripts and saved discovery artifacts, then emit graph and unvalidated path hypotheses.
- Validate with Assay when needed. Run direct and laundered probes through Seam and accept only oracle-observed side effects.
- Report with Assay or ait. Render a human-readable report from findings and related artifacts when there is a validation claim.
The root workbench is the quickest path when a lab already exists:
python3 -m ait.cli lab run full-agent-mesh --scenario content_rewrite --trials 1
Which Tool Should I Use?¶
| Need | Use |
|---|---|
| See whether agent traffic is A2A, MCP, or unknown HTTP | Seam tap |
| Rewrite a complete decoded message | Seam proxy |
| Test whether a rewrite rule fires | Seam rules commands |
| Turn transcripts into a topology | meshmapper |
| Validate a side effect happened | Assay |
| Run a whole lab and collect artifacts | ait |
Safety Boundary¶
All examples are for authorized systems. Seam is not a transparent TLS interception appliance. It operates on traffic you route to it explicitly, such as local HTTP fixtures, configured clients, stdio MCP servers, WebSocket endpoints, or API-managed intercepts.