System Atlas

Upload screenshots

Turn screenshots of your tools and boards into components your agent uploads.

Some of the company only exists on screen: a project board, a CRM pipeline, an org chart in a slide. Agents that read images can turn those into components. System Atlas stores what the agent describes, not the image itself.

  1. Collect the screenshots

    Put them in one folder on the machine the agent runs on. Crop or blur anything personal before the agent sees it.

    • Boards and pipelines: the columns are process steps, the arrows are flows.
    • Tool settings and integrations pages: the tools and what they connect to.
    • Org charts: teams and roles (not people's names).
  2. Ask the agent to read them

    Read the screenshots in ./screens (our tools, boards and org charts).
    For each real thing you can see (a team, a role, a tool, a process step,
    a dataset, a rule) make one System Atlas component: label in our words,
    one plain sentence of description, the layer, and
    source { kind: "client_document", title: "<file name>" }.
    Skip names of people, emails, amounts and anything that looks like a secret.
    Then upload_components in one batch and upload_flows for the hand-offs
    you can see (arrows, columns, "sent to").
  3. Upload what it found

    The agent calls upload_components, naming the screenshot as the source so a reviewer can trace it:

    {
      "workspace": "acme-builders",
      "items": [
        {
          "clientId": "screen/jobs-board/column-estimating",
          "label": "Estimating column on the jobs board",
          "description": "Jobs wait here until an estimator prices them in Excel.",
          "layer": "process",
          "parent": "tool/jobs-board",
          "source": { "kind": "client_document", "title": "jobs-board.png" }
        }
      ]
    }

Tips

  • Use a clientId that names the screen and the element, so a later pass over a fresh screenshot updates instead of duplicating.
  • Screenshots are evidence of how the tool is set up, not of how often it is used: leave values like frequency out unless a doc says so.
Privacy
Screenshots often hold names, emails and amounts. The agent must leave those out; upload the structure only.