Skip to main content

Glossary

TermMeaning
EcosystemA multi-agent workflow declared in YAML. Compiled into one Step Functions state machine.
AgentA single role in an ecosystem — a prompt, tools, an output_kind, and a place in the DAG.
SwarmA named group of agents that can run in parallel.
DAGThe directed acyclic graph formed by agents' depends_on edges.
output_kindThe contract the runtime applies to an agent (analyst, synthesizer, challenger, reporter, drafter, creative, chat, operator).
output_formatAn optional typed artifact an agent produces (markdown/json/yaml/html).
Memory namespaceA shared store agents read/write to pass context within a run.
Report agentAuto-injected agent (when report: true) that assembles the final report.
Challenger agentAuto-injected agent (when quality.challenger: true) that stress-tests the output.
GroundingChecking claims against sources — internal (Bedrock Guardrail) and external (web search).
DomainA knowledge scope defining what to ingest and how.
CatalogThe grounded, versioned knowledge store agents cite.
IngestThe build pipeline that populates the catalog (make ingest).
SynthesisA catalog stage where agents derive higher-order entities from ingested facts.
QuorumA deliberation model where a panel of scrutineer personas reach a verdict.
ScrutineerA persona (with a lens) used in quorum deliberation.
MissionThe operator's request for a run, supplied via the ecosystem's inputs.
ReportThe final structured deliverable of a run.
AgentCore RuntimeThe single Bedrock AgentCore container that runs every agent.
AgentCore GatewayExposes MCP tools to agents.
AgentCore MemoryThe shared, namespace-isolated memory store.
Seedmake seed — publish content + compile ecosystems (fast).
Evaluation harnessOffline capability eval + regression deploy-gate + online monitoring for an ecosystem.
Golden setVersioned, labelled test cases (cases.jsonl) with known-correct answers.
ScorecardThe aggregated result of an eval run (per-metric median ± band, gate decision, miss-rates).
Noise bandThe variance envelope across replicates; a change is a regression only if it clears the band.
Deploy gategate: block | warn | off — what a failing eval threshold does at deploy.
Online evalAsync, zero-latency evaluation of live production runs for drift detection.
Eval State MachineThe per-ecosystem Step Functions machine compiled when an ecosystem declares evaluation:.
Bedrock EvaluationsLLM-as-judge scoring service used by the bedrock_judge scorer.
Step FunctionsAWS orchestration; one state machine per ecosystem (plus catalog and eval machines).
Verified PermissionsAWS authorization service; per-ecosystem access via Cedar policies.

See also​