A handoff map of what to read, change, or teach depending on your goal.
You now have a map of the whole Alembic monorepo. The next step depends on your role:
packages/contracts/src/registry.ts.Collector in @alembic/ingestion.@alembic/coda.apps/cli/src/args.ts and commands.ts.generateCourse and publish via loop-engineering scripts.Every change should be proven at the real boundary: run the command or test that exercises the modified path.
Think of it like… a subway map: you now know all the lines and can plan any route.
Key entry points for each package: @alembic/contracts/src/index.ts, @alembic/adapters/src/index.ts, @alembic/etl/src/index.ts, @alembic/ingestion/src/index.ts, @alembic/swarm/src/index.ts, @alembic/mission/src/index.ts, @alembic/vm/src/index.ts, @alembic/forge/src/index.ts, @alembic/coda/src/index.ts, @alembic/harness/src/index.ts, @alembic/web/src/index.ts, @alembic/tui/src/index.ts, @alembic/marketing-factory/src/index.ts, @alembic/factory/src/index.ts, @alembic/infra/src/index.ts, apps/cli/src/index.ts.
# run the full test suite pnpm -r typecheck && pnpm -r build && pnpm -w test # run just the CLI tests pnpm --filter @alembic/cli test
The canonial verification command is pnpm -r typecheck && pnpm -r build && pnpm -w test. It checks every package, builds dist, and runs the full Vitest suite. The CI workflow runs the same steps plus alembic doctor --json and impeccable detect.
Pick one package and read its src/index.ts. Identify its three most important exports and how the CLI uses them.