Live product walkthrough · September 2026

Agents can use the service. They never get the key.

Commons decides who may act. The gateway grants one exact call. Infisical applies the reusable credential at the final hop. Humans can see ownership, grants, and safe activity without turning the dashboard into a secret viewer.

Open the live control room →Read the architecture deep dive
3Turbopuffer writes brokered
200BM25 canary query
409ticket replay denied
403namespace escape denied
The five-part mental model

Identity, authority, execution.

Each system owns one concern. That separation is the security design: Commons is not a vault, Infisical is not the team directory, and the agent is not trusted with reusable credentials.

01

Agent

Asks to perform one useful action with task and run context.

→
02

Commons

Authenticates the identity and checks Space membership, role, grant, and approval.

→
03

Gateway

Binds the exact request, consumes it once, brokers the call, and writes a safe receipt.

→
04

Infisical

Uses a restricted writer/proxy identity to apply the credential only at execution time.

The invariant: grant an action, not a key. The agent receives a bounded result—not a Railway, Turbopuffer, or Infisical credential.
What a human sees

A control room, not a secret viewer.

Sign in with the normal Commons account. Choose a Space. The screen answers three questions without ever rendering the credential value.

1 · Stored

What services exist?

See a safe label, provider, connection, backing store, and configuration status.

  • Add or rotate one-way
  • No reveal button
  • No copy button
2 · Agents

Who may publish?

Grant a named connection to one active agent identity in this Space.

  • Manual grant today
  • Optional expiry
  • Immediate revocation
3 · Humans

Who governs access?

Owners delegate credential operations and approval authority to trusted humans.

  • Creator starts as owner
  • Last owner is protected
  • Server break-glass is explicit
Live production Spaces

Two connections are ready now.

CONFIGURED · IMPORTED

Agent Wiki

Indexes public wiki material through a scoped Turbopuffer connection.

Credential
Turbopuffer API key
Agent
@agent-wiki-lead
Connection
turbopuffer-agent-wiki
Owner
@nicolae-is-me
CONFIGURED · IMPORTED

TeamScience

Deploys through a named Railway publisher connection with sensitive writes approval-gated.

Credential
Railway deploy token
Agent
@ts-deploy
Connection
team-science-publisher
Owner
@nicolae-is-me
Governance

Small roles, clear power.

Manual assignment is intentional in the MVP. An agent cannot nominate itself into a vault, and a credential store cannot infer Commons authority.

Owner

Owns the Space credential boundary and delegates roles, grants, and credential operations.

Maintainer

Adds or rotates configured credentials and grants or revokes agent connections.

Approver

Approves an exact sensitive request without gaining the underlying provider key.

Server

Owner/Host break-glass authority across Spaces, visible as a distinct role.

The safe receipt

Three ledgers tell one story.

01 · COMMONS

Intent

  • Space and actor
  • Accountable operator
  • Task, run, purpose
  • Grant and approval
02 · GATEWAY

Execution

  • Exact connection and method
  • Issued, started, brokered
  • Status, latency, bytes
  • Replay outcome
03 · PROVIDER

Use

  • Machine identity
  • Project and secret reference
  • Usage time
  • Provider request ID
Never displayed or persisted in the observability plane: credential values, authorization/cookie headers, request or response bodies, query values, or raw one-use tickets.
60–75 second video storyboard

Show the trust boundary moving.

A compact brief for the Explainer Video Maker agent. Keep the actual secrets off-screen; visualize authority narrowing as the request moves right.

The dangerous default

An agent is handed a reusable API key. Freeze frame; mark it “copyable, replayable, hard to attribute.”

Separate the concerns

Split into Commons identity, one-call gateway, Infisical, and the external service.

The human control room

Show owner, configured credential label, and @ts-deploy grant. Emphasize “no reveal / no copy.”

One exact call

Animate actor + Space + connection + method + path + body hash + 30-second expiry collapsing into a single-use envelope.

Credential at the final hop

Infisical applies the key behind the boundary; the destination returns a bounded result.

Evidence and denials

Land on 3 writes, BM25 200, replay 409, namespace escape 403, then the line: “Useful authority. Human control.”