See which acceptance criteria have linked tests and which have none.
Coming soon
Atlas is the browser reader over your FACET records. It runs on your machine, reads the repository you point it at, and rebuilds the page for whoever is reading: leadership, developers, reviewers, authors, owners, newcomers, or an agent.
Start Atlas
The configured FACET distribution includes Atlas. Run /facet:setup in your project to resolve the binary and set up the shell link. Then open Atlas from the terminal:
You do
facet uiYou see
The address on the first line, http://127.0.0.1:7317 unless that port is taken, and a browser opening at it. The server listens on your own machine only. Ctrl-C stops it.
| Option | When you need it |
|---|---|
--no-open | no desktop to open a browser on (SSH, container, CI): print the address only |
--port N | port 7317 is taken by something you want to keep; a taken port falls back to a free one anyway |
--record ID | open straight at one record; the id is in the address, so that address is the one to share |
--registry NAME | a monorepo with several registries; without it, the first declared one is read |
--companion-model NAME | the model Atlas AI answers with; without it, whatever is set to |
--companion-bin PATH | the program Atlas AI runs, when it is not claude on your PATH |
Atlas streams its reading while it happens: records, then the file count, then the search for anchors, with the files going past. Reload the page and it reads the repository again, which is how it stays current while you edit.
Three depths
Atlas is one surface with three depths. A path bar at the top says where you are, and only the depth you are on takes focus.
- RegisterEvery record, acceptance criterion and drift finding, with the situation summed up in one sentence.
- RecordOne feature: what it is for, its requirements, the code anchored to it, and where they differ.
- Acceptance criterionOne scenario, with every test entry linked to it.
Seven roles
Atlas asks who is reading and rebuilds the whole page around that reader instead of filtering it. Nothing is hidden behind a role: what one omits, another shows, and each page says which.
| In Atlas | In English | What the page is rebuilt around |
|---|---|---|
| Leitung | Leadership | A report in plain words, with no schema terms. |
| Entwickler | Developer | Anchored files that changed without their record, and the acceptance criteria of those features that have no linked test. |
| Test & Review | Test & review | Category, then feature, then acceptance criterion, and where tests or docs are missing. |
| Record-Autor | Record author | For each record, which fields are filled and which are missing, emptiest first. |
| Eigentum | Ownership | Portfolio per team, how far dependencies reach, and the history of fixes. |
| Neu hier | New here | A way into this repository, built only from its own records: core areas, FAQ, what to do first. |
| Agent | Agent | Raw data as measured, null for anything not counted, and the endpoints. |
Acceptance criteria and evidence
Each scenario defines an acceptance criterion. Open a feature and a scenario to see every test entry linked to it. In the feature list, a row names one test and counts the others; a missing test entry is stated explicitly.
The acceptance criterion
Given an acceptance criterion referenced by exactly one test entryWhen either surface is drawnThen it names that test and adds no count
What stands behind it
1 test claims it
In Atlas, a scenario counts as proven when a test names it in proves:. Atlas does not run that test. Running tests is the job of your CI.
Atlas also keeps “not measured” apart from zero. A count nobody took is a dash, not a 0, and a share with no known total is not drawn as a percentage.
Atlas AI
Atlas AIAtlas AI answers questions and drafts summaries using your existing sign-in; subscription use needs no extra FACET token purchase, while provider limits and any explicitly configured API billing still apply.View nowRead more here answers questions whose answer is in the code, such as “where does this happen?” or “does the code still do what the record says?”. It starts on your machine, inside the repository, and names every file its answer came from.
- It needs installed and signed in on the same machine.
- All built-in AI features use your existing sign-in. With a supported subscription, you do not buy extra tokens from FACET; your provider’s plan limits still apply. A separately configured API key follows its provider’s billing.
- Its standard tools read records and code; general writing and shell tools are disabled. Separately granted plugin tools may add specific actions. Wiki editing in the browser already proposes changes on a separate branch.
- Choose Haiku, Sonnet or Opus per question, matching the model to a quick lookup or a deeper review.
- Type
/in the question box for its commands, among them/recordand/wiki. Plugins can add their own. - Conversations survive a reload and a restart; they are kept in your browser.
Account details: Claude Code with Pro or Max. A configured API key takes precedence over subscription sign-in.
Plugins
Atlas takes new kinds of content as plugins. Three come with it:
| Plugin | What it adds |
|---|---|
| Wiki | A wiki area with pages, history from git, and editing as a branch and pull request. It can import from Confluence and mirror back to it. |
| ADR | Your architecture decisions, read from the directory adr.directory names in .facetrc.yaml. Read only. |
| BPMN | BPMN 2.0 process diagrams from docs/bpmn/*.bpmn, laid out by a program the plugin brings along. |
A plugin reaches anything outside the page only through named tools, and only those its manifest declares and you granted. Install others from a package file, a ZIP, a folder, an https:// address with its checksum, or a GitHub release:
You do
facet plugin add github:owner/repo@tagYou see
The package is checked against that release's own checksums.txt, then you are asked for each right it declares. Without a terminal nothing is granted unless --grant names it. facet plugin list shows what is installed.
All options are in the CLI reference.
Themes and language
Two themes, FACET and VS Code, each in a light and a dark version. A theme sets more than colour: type size, line height, density and the shape of controls. The interface is in English or German. Both choices are settings of the machine you read on.