Glossary
llms.txt lists every page for a coding agent.
AgentCore
Section titled “AgentCore”Amazon Bedrock AgentCore, the AWS service that runs Loom’s agents: Runtime,
Memory, Gateway, workload identity and Evaluations. Loom drives it through its
control plane (bedrock-agentcore-control) and data plane (bedrock-agentcore).
The second run of every claim. With BREAK=1 the claim breaks its own
property on purpose and must report caught. See Claims.
The infrastructure-as-code tool loomster is written in. It types and lints the stacks, synthesizes CloudFormation, orders the components, runs the Ops and generates CI. You run loomster by its verbs and need to know little chant. chant’s docs, and Choosing chant for the reasons loomster uses it.
chant/lifecycle
Section titled “chant/lifecycle”The git branch chant records Op runs, gates and approvals on (the ledger). A gated Op reads its approval from it. See Gated Ops.
A script in test/claims/<area>/<part>.sh that checks one statement these docs
make and prints one verdict line. See Claims and
Validation.
Component
Section titled “Component”One CloudFormation stack in the deploy graph, declared in
src/components/<name>.component.ts: shared-foundation, loom-cognito,
loom-db, loom-frontend, loom-backend, loom-agents and the
verification-only downstream-stub. See Components.
Composite
Section titled “Composite”The typed building block behind a component, in src/composites/. A composite
takes tier, naming and seam props and returns the resources.
A local AWS emulator. loomster runs the managed pieces of the stack (RDS, Cognito, S3, ECR, ECS, the AgentCore control plane) on Floci for the local run and the Floci claims. What it does not reproduce is in Local caveats.
A step in an Op that stops the run (exit code 3) until someone records an
approval with chant approve <op> <gate>. See Gated Ops.
A person’s permission for a coding agent to run named claims or E2E
scripts that hold real infrastructure, given with just grant. See
Claims.
Instance
Section titled “Instance”The LOOM_INSTANCE segment of every name and stack. Two instance values are two
separate Looms in one account and region. See
Tiers and instances.
awslabs/loom, the AWS Labs application for building, deploying and governing agents on AgentCore. loomster deploys Loom v1.9.0.
A lifecycle workflow in ops/<name>.op.ts, run with chant run <name>: backup,
restore, upgrade, rotate, teardown, seed, drift watch and the rest. See
Ops.
A point where a composite lets you provision a piece of infrastructure, reference one you already have, or omit it. See Provision, reference or omit and the seam matrix.
Seed profile
Section titled “Seed profile”What loom-seed writes into Loom’s database through its API: foundation,
demo or none. See Screens.
stackOutput
Section titled “stackOutput”chant’s cross-stack reference. A component reads another component’s
CloudFormation output by name, and chant run --components passes the value
along, so no parameter files are copied between stacks.
light, production or production-ha (LOOM_TIER): the size and shape of
one Loom. See Tiers and instances and
Tiers and targets.
A set of components with no dependency between them, deployed together.
npx chant graph --components prints the waves.