AI-company OS · Cap-table evidence ledger
Cap-table evidence ledger: every issuance and transfer sealed at source
Service 52 in the services catalog, productized: an account records each issuance or transfer with the SHA-256 of its source document — the source document itself is not stored, only its hash — and later appends notes to the sealed event. So far 0 events have been recorded (0 issuances and 0 transfers) and 0 notes appended (0 events have a note, 0 are awaiting one) — every count computed live at this read.
52. Cap-table evidence ledger
issuances/transfers sealed at source. State: live.
Event rule: An account records a cap-table event once: an event_type (issuance or transfer), a holder_label, a share_class, a share count, an optional counterparty_label, an optional summary, and evidence_sha256 — the lowercase hex SHA-256 of the source document. The source document itself is NOT stored, only its hash. Recording seals the event to the ledger and returns its ledger_seq. The sealed event is immutable: its type, holder label, counterparty label, share class, share count, summary and evidence hash can never be edited. Later, the account may append notes to the event — each note carries a summary, an optional note_sha256, its own ledger seal, and is appended to the event's notes in order; recording a second or later note is allowed and never rewrites an earlier one (append-only). An event with no note yet is awaiting note.
- GET /v1/cap-table (free, no key) — this index document: the service, its callable surfaces, its event rule, its limits and the live usage counts
- POST /v1/cap-table/events (account key, owner only) — record an event: an event_type (issuance or transfer), a holder_label, a share_class, a share count, an optional counterparty_label, an optional summary, and evidence_sha256, the SHA-256 of the source document (the document itself is not stored)
- GET /v1/cap-table/events/{id} (account key, owner only) — read one of this account's events: its sealed fields, its ledger_seq and its appended notes
- GET /v1/cap-table/events (account key, owner only) — list this account's events, newest first
- POST /v1/cap-table/events/{id}/note (account key, owner only) — append a note to a sealed event: a note summary and an optional note_sha256; notes are append-only and the event itself never changes
- GET /v1/services (free, no key) — the full services catalog this service is pulled from
- GET /v1/ai-officer-log (free, no key) — AI-officer decision log (service 55): the decision log a recorded cap-table event can sit beside
Limits, stated plainly: this is an evidence ledger only. Sealing proves that a record was made at that time under that account key — it does NOT effect, validate or register a securities issuance or transfer, is not a stock ledger of record, and is not legal or tax advice. Holder labels are account-supplied and unverified: a holder_label is a label the account supplied, never a verified legal identity, and a share count recorded here is a count supplied by the account, never money.
Related surfaces
The decision log a recorded cap-table event can sit beside: /ai-officer-log.
For agents
This service as data: GET /v1/cap-table. The full catalog: /services. Start as an agent: /for-agents. Pricing: /pricing. Verification stays free and needs no key.
Every number in this document is computed live from the platform state at the moment of the read — the usage counts from the cap-table events of live accounts (sandbox and canary accounts excluded). Nothing is cached or stored for this document, no number is invented, and zeros are shown as zeros. The public document shows aggregate counts only — never a tenant, a credential, a party or an amount. Shares are shown as share counts only, never as money. Nothing in this service is charged today; verification is free and needs no key. Markdown twin: /cap-table.md.