How It Works

Every action — whether initiated by a human at the terminal, an agent on a cron schedule, or an MCP tool call from an AI client — passes through the same pipeline. The policy gate enforces governance rules. The commit captures the state change. The repo stores the complete, immutable history. One path, one audit trail, one source of truth.

The CLI

The corp CLI is the primary human interface. Terminal-first, scriptable, composable. Every command validates the input, passes it through the policy gate, and commits the result to your local repo.

$ corp cap-table issue-equity \
    --entity-id ENT_ID \
    --grant-type common \
    --shares 4_000_000 \
    --recipient "Alice Chen"
  ✔ [7d8e9f0] corp: issue equity to "Alice Chen"

The Git Commit

Every mutation produces an atomic git commit. Not a log entry about the mutation — the commit is the mutation. The entity data, equity records, generated documents, and governance changes all land in a single atomic operation.

Commit messages follow a consistent format: corp: <action> <details>. Your entire corporate history is readable with standard git tools.

$ git log --oneline
  e6f7a8b corp: adopt bylaws v1.0
  b3c4d5e corp: issue SAFE ($500K)
  7d8e9f0 corp: issue equity "Alice"
  4a1b2c3 corp: form "Acme Inc" (DE)
  a0b1c2d corp: init repository

The Policy Gate

Before any action commits, it passes through the policy gate — the programmatic expression of your corporation's governance rules. The gate enforces what the bylaws describe and what board resolutions authorize.

• Does this action require board approval? Has a quorum voted?
• Are there conflicting obligations or pending prerequisites?
• Does the requesting agent have the required scopes?
• Does the action comply with the governing documents?

The gate either approves and commits, blocks the commit, or routes to human approval.

Agents

Agents are first-class participants that commit directly to your corp repo. They run autonomously — on schedules, on events, on demand — and pass through the same policy gates as human actions.

  Agent: compliance-bot
  Trigger: cron (1st of month)

  [f1a2b3c] check compliance deadlines
  [a2b3c4d] prepare DE annual report
  [b3c4d5e] file franchise tax ($400)
  [c4d5e6f] update BOI report

Each agent runs in a sandboxed container with budget controls, scope boundaries, and approval workflows.

Human Pages

Some actions require a human in the loop — signing a stock purchase agreement, acknowledging a disclosure, providing personal information. The system generates obligation pages: simple web forms with a unique URL. When completed, the result commits to the repo.

  Human page: /human/abc123
  Obligation: Sign stock purchase
  Assigned to: Alice Chen
  Status: pending

  On completion:
  [c4d5e6f] obligation completed
             "sign_rspa" (Alice Chen)

Cloud Sync

Your corp repo is a git repo. Keep it local, push to your own remote, or sync to TheCorporation's cloud for managed hosting.

$ git remote add cloud \
    https://thecorporation.ai/acme.git
$ git push cloud main
  ✔ Synced to thecorporation.ai

• Self-hosted — your repo, your server, full sovereignty.
• Cloud — managed agents, hosted pages, filing automation.
• Hybrid — git clone to keep a local copy. Always portable.

The API

CLI, MCP tools, agent ticks, human pages — every surface is a thin client over a single REST API. Every mutation creates a git commit. Reads query the repo state. One API, one policy gate, one audit trail.

POST /v1/formations
{
  "name": "Newco Inc",
  "entity_type": "corporation",
  "jurisdiction": "DE"
}
intent_id: a0b1c2d

POST /v1/execution/intents
{
  "entity_id": "ENT_ID",
  "intent_type":
    "equity.issue",
  "metadata": {
    "shares": 4000000
  }
}
intent_id: 7d8e9f0

GET /v1/entities/{id}/cap-table
{
  "holders": [
    { "name": "Alice",
      "shares": 4000000 }
  ],
  "total": 5000000
}

Whether a human types corp cap-table issue-equity, an MCP tool calls issue_equity(), or an agent runs autonomously — the same pipeline executes.