Skip to content

Topogram Beta Launch

Topogram beta is for teams that want a living app map agents can safely work from.

Status: current Audience: evaluators, engineering leads, maintainers, agents, and package authors Use when: you need the public beta story, first commands, proof paths, limits, and useful feedback asks.

Topogram keeps app intent, contracts, ownership, and proof in a topo/ workspace. Humans and agents use that map to understand what exists, what is owned by generators, what is maintained by people, and what proof should run before a change is trusted.

The beta product wedge is brownfield plus agents:

  1. extract reviewable candidates from existing code;
  2. adopt only the candidates a human reviewed;
  3. query a focused slice for one task or surface;
  4. change maintained code or generate owned output;
  5. verify with the commands named by the map.

Generation is still important, but it is one realization path for the app map, not the whole product.

  • Teams experimenting with coding agents on existing apps.
  • Maintainers who want contracts and proof around brownfield code.
  • Product engineers who want generated starts but expect to graduate parts of the app to maintained ownership.
  • Package authors building generator or extractor packs for a stack.
  • Release owners who want consumer proof, public smoke, and package rollup checks before shipping.

From this repo, run the published CLI smoke:

Terminal window
TOPOGRAM_CLI_PACKAGE_SPEC=@topogram/cli@latest npm run smoke:beta-evaluator

That command installs the public CLI and first-party extractor packages in a clean temp project. It creates a small brownfield app, extracts review-only candidates, adopts a reviewed bundle, emits agent packets, validates the adopted topo/, and writes a portable report.

For your own app, use the same shape manually:

Terminal window
npx topogram extract ./existing-app --out ./imported-topogram
cd ./imported-topogram
npx topogram extract plan
npx topogram adopt --list
npx topogram query extract-plan ./topo --json
npx topogram query single-agent-plan ./topo --mode extract-adopt --json
npx topogram check

Start with package-backed extractors when the stack is known:

Terminal window
npm install --save-dev @topogram/cli @topogram/extractor-express-api @topogram/extractor-prisma-db
npx topogram extractor recommend ./existing-app --from db,api
npx topogram extractor policy init
npx topogram extractor policy pin @topogram/extractor-express-api@1
npx topogram extractor policy pin @topogram/extractor-prisma-db@1
npx topogram extract ./existing-app --out ./imported-topogram --from db,api --extractor @topogram/extractor-express-api --extractor @topogram/extractor-prisma-db

Use the proof repos when you want a complete story with branches, tags, SDLC records, agent packets, artifacts, and npm run verify at every checkpoint.

  • init, copy, extract, adopt, generate, emit, and query command vocabulary.
  • topo/ workspace ownership and project config.
  • Brownfield extraction with bundled and first-party package-backed extractors.
  • Review-only adoption plans and explicit adopt --write.
  • Agent briefs, focused context slices, SDLC readiness, and proof-gap queries.
  • Web UI semantic contracts, widget realization reports, and i18n/ARIA obligation markers for generated web output.
  • Widget-first design realization matrices that show component refs, platform coverage, variant/state coverage, token/a11y/i18n gaps, and review work.
  • Release preflight, strict release status, first-party consumer rollup, proof consumer tracking, and secret scanning.

Topogram beta does not promise:

  • pixel-perfect UI parity;
  • complete runtime translation catalog management;
  • full automated accessibility audit coverage;
  • production deployment orchestration;
  • automatic source mutation during extraction;
  • silent adoption of brownfield candidates;
  • enterprise audit exports, signed history, or external issue tracker sync.

Native generation and some workflow extractor families are preview/future work.

Useful beta feedback is concrete:

  • Which command or artifact was unclear?
  • Which candidate was noisy, missing, or unsafe to adopt?
  • Which slice gave an agent too much or too little context?
  • Which proof command failed to build trust?
  • Which stack needs a generator or extractor pack?
  • Which beta limit blocks real evaluation?

Attach the command, the relevant topo/ file or candidate artifact, and the expected next action when possible.