Skip to content
loomster

Platform team

llms.txt lists every page for a coding agent.

Works

Section titled “Works”
  • Every piece you already own is a seam: network, KMS, ECR, DNS, certificate, agent role, backend and frontend roles, database, Cognito pool.
  • One instance per boundary with a shared Cognito pool, from the same source.
  • Generated pipelines that follow the component graph, a gated deploy, and scheduled Ops behind repository variables.
  • Loom bumps as a pin change plus an upgrade Op that snapshots first.

Differs

Section titled “Differs”
  • Light builds its own VPC; the production tiers always need yours.
  • Per-agent role stacks and the DNS zone from loom-dns-setup live outside the component graph, so teardown leaves them.
  • CloudFormation keeps the state; there is no backend to run.

First step

Section titled “First step”

Bring your own network and IAM.

Proof

Section titled “Proof”

src/examples/byo/adoption.test.ts builds every seam as reference-existing on all three tiers (Bring your own everything); Validation lists what has run live.

Then read

Section titled “Then read”

Tasks: Share a Cognito pool, Bring your own KMS, ECR and database, Run a second deployment, Add CI to your forge, Upgrade Loom.

Explanation: Provision, reference or omit, Tiers and instances.

Reference: Adoption seams, Build parameters, Components, Naming and tagging.