TheCorporation Docs

Architecture

Git-native storage, the intent/decision/receipt execution model, bounded contexts, and cryptographic signing. Overview →

CLI

The corp binary — local-first with --local mode, @last refs, and the full governance surface in one Rust binary. Overview →

REST API

Full REST API served by corp-server — same governance kernel, same git commits, accessible from any HTTP client. Overview →

MCP Server

12 tools with 64 operations for AI agent integration via Model Context Protocol. Overview →

TypeScript SDK

@thecorporation/corp — typed HTTP client, CLI wrapper, and binary manager. Browser-safe with zero runtime dependencies. Documentation →

Examples

Step-by-step walkthroughs — formation through operations — with real corp commands and API calls. C-Corp Founder Journey →

Philosophy

Why git-native corporate governance — design principles and the problem we’re solving. Read →

Key Patterns

• Git-native storage — every entity is a bare git repository containing JSON files, committed atomically, with full history
• Intent / Decision / Receipt — every side effect requires a typed intent, a policy decision, and an immutable receipt
• Cryptographic signing — optional Ed25519 SSH commit signatures with actor identity trailers
• Three interfaces, one kernel — HTTP API, Rust CLI (corp), and local oneshot (corp-server call) all go through the same governance engine, producing identical commits
• Local-first — corp --local runs entirely on your machine with no server required; all state is written to bare git repos under CORP_DATA_DIR
• Self-hostable — run corp-server on your infrastructure with all data in git repos you own

Open Source

The core is Apache-2.0 licensed in the thecorporation-public repository — five Rust crates:

Crate	Purpose
corp-core	Domain types, governance AST, execution model
corp-storage	Git-native storage backend
corp-server	Axum HTTP server + call oneshot subcommand
corp-cli	The corp binary
corp-auth	Authentication primitives