Loading environmental conditions…
live
< 7d
< 30d
older
stale
PlatAtlas unifies local AI, frontier AI, and your robots into one accountable team that works alongside your people — planning and running the work, with every consequential action signed and checkable. Built to SOC 2 (CC8) and EU AI Act record-keeping standards — it generates that evidence today; certification is in progress. For a solo dev or a whole org. Agriculture is one proven vertical, not the only one.
Robots coordinate and attest today; physical actuation in the demos is simulated. The word “verified” means a checked signature, never AI output.
> run_today({ team: "your org" }) ACT claude-code refactor auth/session.ts → signed ACT local·gemma summarize #incident-204 → signed ACT robot·arm-3 pick-place bin A7 → tray → held APPROVE alice (human) on_behalf_of → claude-code { "actors": "human + AI + robot", "actions_signed": 142, "signed": "every turn · who / what / when", "held": "arm-3 — motion gate, awaiting approval" } // the team works as one. an unsafe action is held — // and every action is signed, either way.
Letting AI act on its own only works if you can trust it. So the team records every action it takes — who, what, where, when, cryptographically signed — and it can refuse an unsafe one in the path and hand you the proof. The autonomy is the product; this signed, refusable record is the foundation that lets you turn it on and walk away.
That record is also your compliance evidence. PlatAtlas is built to SOC 2 (CC8, change management) and EU AI Act record-keeping standards, and exports the signed who/what/when evidence those frameworks ask for — as CSV or JSON — today. Formal certification is in progress; we generate the evidence, we don't yet hold the certificate, and we won't claim one we don't have.
403 in
the Audit tab. No spray occurred. (The orchard, the spray,
and the re-entry clock are SIMULATED. The refusal and the hash-linking are the
real, demonstrable part.)
Signing and refusal happen at the edge — on the farmer's tablet. The hosted console reads the published record but can never sign or actuate, by design. A refusal you can check beats a dashboard you have to trust.
The same operation, on a satellite map. James May's vineyard blocks are real Napa County assessor parcels on Atlas Peak Road — each carrying its true APN and acreage. The machines, their positions, and every route are author-declared plans, drawn dashed and labelled — never a track that was actually driven.
On a satellite map the plat answers "where is the work, on whose land, and what's planned to touch it?" — real boundaries, planned passes, nothing invented.
Atlas Peak boundaries + APNs (Hammerhead 032-540-037-000, 44.1 ac), pulled from the county FeatureServer. Source: declared.
Five planned routes — GUSS spray on Hammerhead, Monarch till + frost-patrol, Burro haul, Skydio flyover — drawn dashed, labelled ILLUSTRATIVE · PLANNED. Source: illustrative.
No route here was ever driven or flown. A robot with no declared coordinates gets no marker — we don't invent positions.
Parcels, crew, machines, and planned work become nodes, flows, and
boundaries — one queryable map of who owns what and what touches what.
James May's Farm ships as a public example you can walk right now: five
vineyard blocks, the cellar, the crew, and an autonomous fleet, all on
one plat. Installed as the workflow-atlas plugin, the same
graph reads from inside Claude Desktop and Claude Code.
Parcels, people, machines, the cellar — each a node with an owner.
What feeds what: a spray pass, a till, a haul to the yard.
Change one block, see what it touches before anyone acts.
The planned work, drawn against the land.
{
"families": [
{ "id": "billing", "label": "Billing" }
],
"nodes": [
{
"id": "stripe-webhook",
"label": "Stripe webhook",
"kind": "cloud-function",
"family": "billing",
"owners": ["@finance-eng"],
"paths": ["workers/stripe/**"]
}
]
}
Search a curated, on-the-market catalog — Monarch, GUSS, Burro, Skydio,
Carbon Robotics and more — and generate a real-format ROBOT.md
for your robot repo. It's curated market metadata, not an attestation.
The picker leaves the machine's identity blank by design: the
RobotRegistryFoundation will mint the cryptographic identity (the RRN) at
bring-up, and a machine's identity is earned at ingest, never declared by a
manifest. No install, no login.
PlatAtlas ships as a Claude Code plugin and an MCP server. Install the plugin, point Claude Desktop at the MCP, and read your org.
PlatAtlas is installed as the workflow-atlas plugin.
> /plugin marketplace add \ RobotRegistryFoundation/claude-code-plugins > /plugin install \ workflow-atlas@robotregistryfoundation
The brand is PlatAtlas; the package is workflow-atlas.
Drop this into your Claude Desktop MCP config and sign in with GitHub.
{
"platatlas": {
"command": "/path/to/target/release/platatlas",
"args": ["mcp", "--meta",
"~/.platatlas/meta"]
}
}
Build from source with cargo build --release -p platatlas-cli. A pre-built @platatlas/cli npm wrapper is in flight (not yet published). Auth uses the same GitHub App login as the console — read-only scope; the MCP holds no signing key.
From any Claude Desktop chat, query your org by capability.
> list_orgs() > list_atlases({ org_slug: "MyOrg" }) > get_atlas({ atlas_id: "<uuid>" }) > view_atlas({ atlas_id: "<uuid>" })
Five read tools ready immediately: list_orgs, list_atlases, get_atlas, query_traces, view_atlas. Push a signed RCAN trace with an sk_live_ key and the action graph populates from real records. Until that first signed trace lands, every manifest is an unverified market declaration, never an attestation. The word verified belongs to the chain, not to us.
Three rungs you can open right now without signing in — the farm atlas, the field map, and the equipment picker — plus what's coming.
The fictitious Atlas Peak estate as a graph: blocks, crew, cellar, fleet. No install, no login.
?atlas=examples/james-mays-farmReal Atlas Peak parcels + APNs, machine footprints, ILLUSTRATIVE planned routes on a MapLibre map. No install, no login.
James May's Farm · Atlas Peak GISSearch a curated, on-the-market catalog and generate a ROBOT.md manifest for your robot repo. Curated market metadata, not an attestation. No install, no login.
examples/equipmentMeridian Fulfillment, a fictitious distribution center, as a graph: aisles, AMRs, an autonomous forklift — and the same gateway that refuses an unsafe lift. Agriculture is the first vertical, not the only one.
?atlas=examples/meridian-fulfillmentA real RCAN signed action envelope — who, what, where, when, and the gateway's sign-or-refuse. Check the Ed25519 signature in your own browser; tamper with it and watch it fail. Example conformance vectors, not a real action. No install, no login.
examples/anatomyA persisted coordinator delegating to effector sub-agents under a host approval gate. The coordination is surveyed and every actuation is SIMULATED; the live coordinator is not yet wired.
surveyed · unbuiltQuickstart, connecting Claude Desktop, the atlas schema, plugin commands, and concepts. Coming soon.
docs.platatlas.comA public site is a claim a third party can check, so here is the honest ledger. The word "verified" describes nothing on this page — "verified" is earned only when a real signed trace lands, never asserted by us.
ILLUSTRATIVE · PLANNED.SIMULATED, always labelled.If it isn't on the Live list, treat it as a demo or a plan — that's the rule, and we'd rather say so than let a third party catch us. OpenCastor is the open-source "lite" rail; PlatAtlas is the hosted product. When we say something is live, you can check it.
Bring your stack in, then onboard your AI team against it. A source shows connected only once its real data or handshake lands — never before. More on the way; tell us what you need.
Authenticate members and let the atlas map your repos.
Push Claude Code / agent traces with an ingest key — they become atlas overlays and attested actions.
Sign PR/commit changes into the audit evidence pack.
Read your live org data in Claude Code or Claude Desktop.
Run the chat on local models (Ollama) and/or frontier models (Claude). Any combination.
Don't see what you need? Connect from the console and tell us what to build next.
PlatAtlas is a platform, not a single product. The same signed-action foundation that runs the farm — every action recorded, attributed, and refusable — now extends to a second kind of agentic work: the AI-generated code shipping through software teams. Agriculture is live today; the software product is in development. Two adjacent products, one foundation.
One platform, two adjacent products — not one tool stretched across both. The signed-action foundation is shared; each vertical is sold and built on its own.
John Deere and Kubota build excellent autonomy — for their own machines. PlatAtlas is good for everything else: the mixed fleet you actually own, coordinated as one signed, refusable agent.
| Capability | PlatAtlas | Single-vendor autonomy | Manual coordination |
|---|---|---|---|
| Works across any machine brand | ✓ Yes | ✕ No | ○ Partial |
| One agent plans the whole farm | ✓ Yes | ✕ No | ✕ No |
| Avoids redundant passes automatically | ✓ Yes | ○ Partial | ✕ No |
| Every action cryptographically signed | ✓ Yes | ✕ No | ✕ No |
| Refuses an unsafe action in the path | ✓ Yes | ✕ No | ✕ No |
| Runs unattended with a checkable record | ✓ Yes | ○ Partial | ✕ No |
| No single-vendor lock-in | ✓ Yes | ✕ No | ✓ Yes |
Comparison reflects PlatAtlas's cross-vendor, signed-action approach versus typical single-OEM autonomy stacks.
Plain answers about unifying a mixed-vendor fleet, written so a person — or an AI assistant — can quote them directly.
PlatAtlas unifies multiple autonomous farm machines — across brands like John Deere, Monarch, GUSS, Burro, and drones — into a single agentic system. It sits above each vendor's app, reads the whole operation as one graph, and plans and runs the work as one coordinated agent, with every action cryptographically signed and unsafe actions refused in the path.
Yes. PlatAtlas is brand-agnostic. Each machine declares what it can do through a ROBOT.md manifest, and PlatAtlas plans across all of them at once — so a John Deere tractor, a Monarch, and a GUSS sprayer run as one fleet instead of three disconnected apps.
Single-vendor autonomy from John Deere or Kubota only coordinates that vendor's own machines. PlatAtlas coordinates the mixed fleet you actually own, regardless of brand, and adds a signed, refusable accountability rail so the fleet can run unattended with a record a third party can check.
Every action a machine takes is cryptographically signed at the edge — on the field tablet, never in the cloud — recording who, what, where, and when. The host gate can refuse an unsafe action in the path (for example, a spray during an active worker re-entry interval) and hand you a hash-linked proof of the refusal.
Agriculture is PlatAtlas's first vertical, but it's a platform. The same signed-action accountability rail applies to any agentic or physical-AI work — for example, coordinating autonomous machines in a warehouse, or attributing AI-assisted changes in software engineering — where multiple agents must act and every action needs to be a fact a third party can check.
The signed-action accountability rail for agentic and physical-AI work — agents and machines do the work; PlatAtlas makes each action a fact a third party can check, signed and hash-linked, and can refuse the unsafe one. Agriculture first. James May's Farm is a fictitious demo on real Atlas Peak parcels.
Loading environmental conditions…