Architecture
The Agent Assurance system boundary, components, data flow, and control-plane responsibilities.
System Boundary
Agent Assurance is the commercial control plane. It should orchestrate OSS engines, not reimplement them.
flowchart LR
Sources["Docs, schemas, traces, policies"] --> Runner["Self-hosted runner"]
Runner --> DocPull["docpull OSS"]
Runner --> PolicyStrata["policystrata OSS"]
DocPull --> Artifacts["Run artifacts"]
PolicyStrata --> Artifacts
Artifacts --> API["Agent Assurance API"]
API --> Web["Dashboard and review UI"]
Web --> Packs["Evidence packs"]
Packs --> Releases["Release decisions"]Components
| Component | Repo/Path | Responsibility |
|---|---|---|
| Web app | app/, components/, lib/ | Marketing, docs, dashboard, review, releases |
| Runner contract | runner/ | Executes OSS tools locally and emits normalized artifacts |
| JSON schemas | schemas/ | Stable contracts across runner, API, UI, and audit packs |
| Demo scenarios | examples/ | Reproducible design-partner and sales demos |
| DocPull engine | raintree/oss/docpull | Context sync, diffs, citations, packs |
| PolicyStrata engine | raintree/oss/policystrata | Policy drift, witnesses, invariant checks |
Data Flow
- A self-hosted runner executes in CI, a developer machine, or a customer-controlled environment.
- The runner invokes DocPull and PolicyStrata against configured sources, policies, schemas, traces, and release inputs.
- The runner emits normalized assurance-run artifacts and optional evidence packs.
- The Agent Assurance API persists metadata, findings, artifact references, release state, and reviewer decisions.
- The dashboard presents blockers, release history, and audit-ready evidence.
Boundary Rules
- Keep source credentials, raw documents, private traces, schemas, and customer rows out of the hosted web app by default.
- Store normalized metadata, summarized findings, hashes, tool versions, and artifact references.
- Use runners and worker services for engine execution.
- Keep DocPull and PolicyStrata independently useful as OSS engines.
Design constraint
The hosted control plane should be useful without becoming the place where raw governed data accumulates.