Agent library
13 atomic agents · 5 engine-nodesOrchestration
The control plane. Routes work across agents by use-case context, runs fan-out/parallel stages, isolates failures, and enforces the HIL + audit policies. Humans reach it via UI, machines via API, agents via A2A.
RunContextrouted tasks → final stateRetrieval & Knowledge
Agentic retrieval loop that grounds an answer in a corpus and cites its source. The retriever is a swappable tool — the same loop serves internal precedent or live external sources.
Query { text, filters?, k? }CitedAnswer { answer, passages[], sources[] }Understanding
Turns an artifact into structured fields or labels against a supplied taxonomy. The output schema is user-defined — you choose what to extract.
Artifact { text | record }user-defined schema (configurable)Builds a structured reasoning model of the target (e.g. a knowledge graph of modules, data flows, and trust boundaries) that downstream agents reason over.
Target { root, adapter }Model { nodes[], edges[], summary }Proposes that two records are the same entity using embeddings, surfacing suggestions for human review — never auto-merges.
Record[]MergeSuggestion[] { a, b, score }Testing & Validation
Reasons like a tester: forms specific hypotheses against the model, gathers evidence via a static analyzer, and confirms or rejects each with cited evidence.
Model | TargetFinding[] { claim, evidence, verdict, severity }The only agent that executes the target rather than reading it. Launches it, probes endpoints or drives a browser, and reports live failures.
Target { launch, endpoints? }Finding[] { probe, status, detail }Given a checklist or spec, verifies each item against the artifact and reports satisfied / not-satisfied with the supporting evidence.
{ artifact, checklist[] }Result[] { item, satisfied, evidence }Pure-LLM design/architecture review over a supplied model — single points of failure, coupling, scalability, missing resilience or observability.
ModelFinding[] { concern, rationale, severity }Analysis
Consolidates raw findings from many agents into a small set of deduplicated, prioritized items and tracks each across runs (new / persisting / resolved).
Finding[]Gap[] { id, theme, priority, status }Action
Executes a disposition through a connector — open a ticket, notify, pull evidence, remediate — and records the structured result.
Disposition | RequestActionResult { name, ref, status }Reporting
Turns structured results into an audience-shaped narrative — a board summary, a regulator report, or a plain-English explanation of a single finding.
DataReport { sections[] }Monitoring
Watches a live signal against a baseline and flags drift or anomalies across assets, vendors, or behavior.
Signal streamAnomaly[] { entity, kind, score }Interactive
An interactive assistant that answers open-ended questions by calling deterministic engine tools and reasoning over their structured results.
Question (+ history)Answer (+ tool calls)Governance
Deterministic fail-closed pre-filter. Evaluates hard rules and can short-circuit the whole workflow (e.g. a known false-positive is auto-cleared).
CaseDecision { pass, rule?, reason }Deterministic scoring engine. Computes a severity vector and priority from weighted signals — the model never does this math.
SignalsScore { vector, priority }Deterministic network math over a policy graph: reachability, CIDR overlap, rule shadowing, cross-tool path tracing.
PolicyGraphPaths[] | Overlaps[]Deterministic detection of language, framework, and package manager by inspecting which files exist — never executes project code.
Target { root }Stack { language, framework, pkgManager }Deterministically merges records into canonical entities using stable keys — the confident half of identity resolution.
Record[]Entity[]