This atlas covers the 18 identified noncrypto builders in this investigation. Connected projects share a factory overview. Individual components remain listed with their roles and sources.
A map is an explanation of the reviewed sources. It is not proof that a workflow runs unattended. A repository documents a design; a creator’s operating update is a report. Each dossier names the gaps.
- Documented architecture
- Public source or documentation explains the mechanism. We did not install or benchmark it.
- Reported operation
- The builder describes using the workflow. Throughput and reliability remain attributed claims.
- Partial evidence
- Projects are visible, but parts of the production process or orchestration are not established.
The miniature workplaces use the Two Point workflow grammar: rooms show actions, characters show owners, work items preserve identity, and a review desk or exception tray shows what happens when a machine cannot finish. Example work items are illustrative. Dashed or unknown routes are not confirmed implementation.
Some component links point to the builder’s public inventory when a standalone implementation was not inspected. Project/component counts refer to listed entries, not distinct repositories or independently tested products.
Tokens are not a productivity score. All-time submitted usage, monthly totals, actual spend, API-equivalent value, subscriptions and concurrent agents are different measures. Cache reads may dominate. The token sort only compares explicitly identified all-time totals.
Timeline entries require dated evidence. An empty month means this research has no dated event, not that a builder was inactive. The local tweet archive covers July–September; earlier events depend on public sources.
Research priority is editorial relevance to understanding factories. It is not a benchmark or a universal frontier ranking. Artwork is AI-generated from saved scene contracts and reviewed for source fidelity.
Tokscale discovery source ↗