t↗TENURECOMPANY AUTHORITY SYNTHETIC WORKSPACE

ONE AGENT · FOUR TOOLS · SEPARATE AUTHORITY

The agent that runs the company should not have one credential.

Acme Robotics asks in Slack for SAML SSO before they expand. The company agent files the Linear issue, merges the GitHub pull request, marks the Attio deal won, and sends the Stripe invoice. Each action is earned on its own. Two others are registered and still refused.

NO LIVE GITHUB
NO LIVE STRIPE
SYNTHETIC SANDBOX

THE ASK

Acme wants SSO before they sign.

Expansion value is the ceiling the billing capabilities must stay inside. Default $18,400. Maximum earned ceiling is $50,000.

Customer: Acme Robotics · Channel: Slack Connect · Repo: acme-app/web · CRM: Attio · Billing: Stripe

  1. 01
    LINEARFile the issueWAITING
  2. 02
    GITHUBMerge the PRWAITING
  3. 03
    ATTIOClose the dealWAITING
  4. 04
    STRIPESend the invoiceWAITING

WHAT THIS AGENT MAY DO

Registration is not authority.

No case yet. The agent starts with nothing it can execute.

Capability passports for this company agent
CapabilityToolLevelWhy
Run the case to earn the four operating capabilities.

SIGNED RECEIPTS

Every mutation has a passport.

Receipts appear after the case runs.

What this is

A working authority kernel on synthetic Linear, GitHub, Attio, and Stripe records. No repository is cloned, no invoice is emailed, no payment moves. Irreversible consequences — a production deploy, an email already sent — are escalated, not pretended away.

Full scope and limits

THE COMPANY COMPANY

One agent. A separate permission for every tool.

The Company Company runs a business through Slack, Linear, GitHub, Attio, and Stripe. We built this page around that agent: filing an issue, merging code, updating a deal, and sending an invoice should not share one credential.

WHAT THIS IS

A working model of that idea. A customer asks in Slack for SSO. The agent does the four steps. The records are synthetic. No real repository, deal, or invoice is touched.

WHAT TO PRESS

  1. Run the company agent. Linear, GitHub, Attio, and Stripe each earn their own passport. A refund and turning off branch protection stay refused.
  2. Freeze, then investigate. The Slack message that started the work was not the customer. Watch what freezes first, what rolls back, and what cannot be undone.

WHAT IT CAN SHOW

  1. Authority earned per tool, after the work, not granted on day one.
  2. Every later action that depended on a bad instruction, frozen before any model runs.
  3. The issue, pull request, deal, and invoice rolled back. A production deploy and an email the customer already received, escalated.

ACTION RECEIPT