PantryAtlas · production

Overview

Real-time health, traffic, and access across the PantryAtlas organization — every repo, service, and atlas in one place.

API events · 24h
Last activity
Active flows
Tokens · used / cache reuse

Thesis

hypotheses · live

Workflow Atlas

org map · preview
Open atlas ↗
Plate I · Sheet 1 of 4

The Workflow Atlas

awaiting survey
scale 1:repos
projection · systems
edges · status
project settings · api

API keys

Authenticate requests to the Plat Atlas API for PantryAtlas. Treat secret keys like passwords — anyone holding one gets whatever access its scopes grant. Never commit them to source control.

Publishable vs. secret keys

Publishable keys (pa_pub_…) are safe to expose in client code — they're restricted to public, read-only resources. Secret keys (sk_live_…) bypass access policies and must stay server-side. Rotating a key revokes the previous value immediately.

4 keys · 1 expiring
preview state
NameKeyScopesCreatedLast used
production-server
added by c.merry
sk_live_••••••••••••••••
readwrite 2026-03-14 4 min ago
ci-pipeline
added by j.okafor
sk_live_••••••••••••••••
read 2026-04-02 2 hours ago
web-client
publishable
pa_pub_8Hn4Km2Wq9Zx
public-read 2026-04-02 just now
migration-temp
expires in 3 days
sk_live_••••••••••••••••
readwriteadmin 2026-05-20 1 day ago

No API keys yet

Create a key to start making authenticated requests to the Plat Atlas API from your servers, CI pipelines, or scripts.

Couldn't load API keys

We hit an error fetching keys for this organization. This is usually temporary — check your connection and try again.

request_id: req_8fK2aL9dQ4mZ
organization · access control

Access

People, AI agents, roles, and access requests for PantryAtlas — one place to grant, scope, time-box, and revoke.

preview state
MemberRoleAtlas accessStatusJoined
CM
Craig Merry
craig@pantryatlas.org
Ownerall atlases · org-wideactive2025-11-02
JO
Jane Okafor
jane@pantryatlas.org
Adminall atlases · org-wideactive2025-12-15
DL
Dev Lin
dev@pantryatlas.org
Developerpantryatlas, docsactive2026-01-20
SP
Sam Park
sam@pantryatlas.org
Developerpantryatlasactive2026-02-08
AB
Aria Bello contractor
aria@partner.io
Viewerpublic atlases · read-onlyexpires 21d2026-03-30
RS
Rafa Santos
rafa@pantryatlas.org
Developerawaiting acceptanceinvited1 day ago

No members match

No members match your current search or filters. Try a different term, or clear the filters to see everyone in PantryAtlas.

Couldn't load members

We hit an error fetching the member list for PantryAtlas. This is usually temporary — check your connection and try again.

request_id: req_3pQ7vM1nK8sT

Service accounts for AI & automation

Agents have an owner, scoped access, a credential (API token or OAuth/MCP binding), and optional expiry. Every action an agent takes is attributed in the activity log.

2 service accounts
AgentOwnerRoleScopeCredential
🤖
Claude · service
agent · created 2026-05-12
Craig MerryDeveloperpantryatlas OAuth · MCP
ci-deploy-bot
agent · created 2026-04-02
Jane OkaforDeveloperpantryatlas, docs
sk_live_••••••••
Roles & permissions · presets + custom

Owner

1 member

Full administrative control. Manages billing and members; can transfer or delete the organization.

org · destructiveEdit · soon

Admin

1 member

Manages members, agents and API keys; configures every repo. No billing or org deletion.

org · manageEdit · soon

Developer

2 members · 2 agents

Read/write on assigned atlases. Can issue scoped tokens; cannot manage members.

repo · writeEdit · soon

Viewer

1 member

Read-only on public atlases. The default for partners and external collaborators.

repo · readEdit · soon

Release Manager

custom · 0 members

Can deploy and tag releases on assigned repos. No member, key, or billing management.

repo · deployEdit · soon

Access requests

People and agents can request a role, repo, or view. Admins approve or deny here — every decision is logged.

Rafa Santos requests Developer on pantryatlas
"need write to ship the navigator fix" · 4h ago
ci-deploy-bot agent requests write on recipe-db
owned by Jane Okafor · "publish recipes-v0.3.0" · 1d ago
Verified robots · production

Robots

Every verified robot in this org and the operators it acts for — plus a cryptographically-attested log of what each robot did. A robot appears here only after a gateway-signed action verified against its RRF authority.

Operator → robot graph
Loading robots…
Field map
Loading field map…
Viewpoints & assists
Loading viewpoints & assists…
Verified action log
RobotToolStatusAttestationWhenSourceProvenance
Loading actions…
Authority map · production

Governance

Every actor that touched this org, grouped by how its authority is backed. Each tier is computed and stamped server-side — the console only renders what the registry attests. Physical AI and RRF-signed operators are cryptographically verified; a software-AI agent is audit-logged session attribution, not RRF-crypto-verified.

RRF-verified — signed & registry-attested Session-authenticated — GitHub login Audit-logged — software AI, not crypto-verified
Actors & the principals they act for
Loading governance…
AI usage · production

Usage

Every AI interaction this org can honestly account for — actions, actors, error rates, and token efficiency. Software-AI activity is audit-logged (uploader-attributed), not RRF-crypto-verified; the word verified is reserved for signed physical-AI actions. Token totals are real (summed over deduped requests) or honestly empty — never estimated.

Activity & token record
Loading usage…
Survey office · before you build

Survey check

Ask before you build: does this already exist in the org's atlas? Verdicts come only from the declared atlas — found / possible / unsurveyed — never guessed. Every query lands in the org's survey.query audit ledger, same as agent queries.

Survey before you build
Type what you're about to build. The survey answers from the declared atlas — it never guesses, and it never fires without a query.
Field sheet · today

Today

Today at my site — the published mission and its gates, the crew on record, the latest operator-signed measurements, and the newest published camera still. Everything below is the published record or an honest empty; software-AI crew reads audit-logged, never "verified".

Fleet · Managed-Agent ops

Fleet

The Managed-Agent fleet — a persisted coordinator delegating to effector sub-agents, gated by a host-side human approval queue. Coordination is REAL; every physical actuation is SIMULATED and labelled. The coordinator and effectors are software-AI (audit-logged, never an RRF attestation); nothing here is fetched live. Everything below is the published run record or an honest empty.

Plat Atlas FieldOps · field run record

Field operations

The Plat Atlas FieldOps read view — the operator-published field run record (coordination REAL; every physical actuation SIMULATED and labelled). This is the cloud, read-only side: the signing key lives on the field device (the phone approver / edge client), never here. Everything below is the published run record or an honest empty.

Program · shared record

The Work Program

Now/next, the thesis board, the latest bring-up ledger, the 48-hour ship log, and open issues by cluster — one shared progress record for humans and AI alike. Everything below is the published record (regenerated by bin/progress-page.mjs from real sources) or an honest empty; nothing here is fetched live from GitHub.

Audit ledger · the record

Audit ledger

Every recorded action in this org — who acted, on what, and the outcome, newest first. Denied attempts are part of the record and wear the red ink. Everything below is the recorded ledger or an honest empty — never a fabricated row; filter choices come from events the wire actually returned, never a fixed list.

PantryAtlas · view

View

Prototype view

Surveyed, not yet built. This view is packaged on a console, but its full surface doesn't exist yet. PlatAtlas never typesets vapor as product — when the view ships it replaces this placeholder; until then, this is honestly all there is.

retired view · tombstone

Retired view

Retired

This view was retired. Its provenance is kept on the record; its data plane is closed — nothing is rendered from a retired spec.

Copied