AI-company OS · AI-officer action log
AI-officer decision log: every autonomous decision sealed with its rationale hash
Service 55 in the services catalog, productized: an account records each autonomous decision with the SHA-256 of its rationale document — the rationale itself is not stored, only its hash — and later appends outcome notes to the sealed decision. So far 0 decisions have been recorded and 0 outcomes appended (0 decisions have an outcome, 0 are awaiting one) — every count computed live at this read.
55. AI-officer action log
every autonomous decision sealed with rationale hash. State: live.
Decision rule: An account records a decision once: a title, an optional category, an optional summary, an optional label for the officer or agent role that decided, and rationale_sha256 — the lowercase hex SHA-256 of the rationale document. The rationale itself is NOT stored, only its hash. Recording seals the decision to the ledger and returns its ledger_seq. The sealed decision is immutable: its title, category, summary, deciding label and rationale hash can never be edited. Later, the account may append outcome notes to the decision — each outcome carries a summary, an optional outcome_sha256, its own ledger seal, and is appended to the decision's outcomes in order; recording a second or later outcome is allowed and never rewrites an earlier one (append-only). A decision with no outcome yet is awaiting outcome.
- GET /v1/ai-officer-log (free, no key) — this index document: the service, its callable surfaces, its decision rule, its limits and the live usage counts
- POST /v1/ai-officer-log/decisions (account key, owner only) — record a decision: a title, an optional category, an optional summary, an optional decided_by label, and rationale_sha256, the SHA-256 of the rationale document (the rationale itself is not stored)
- GET /v1/ai-officer-log/decisions/{id} (account key, owner only) — read one of this account's decisions: its sealed fields, its ledger_seq and its appended outcomes
- GET /v1/ai-officer-log/decisions (account key, owner only) — list this account's decisions, newest first
- POST /v1/ai-officer-log/decisions/{id}/outcome (account key, owner only) — append an outcome note to a sealed decision: an outcome summary and an optional outcome_sha256; outcomes are append-only and the decision itself never changes
- GET /v1/services (free, no key) — the full services catalog this service is pulled from
- GET /v1/quote-to-contract (free, no key) — quote-to-contract autopipeline (service 27): the sealed-agreement flow a recorded decision can later point at
Limits, stated plainly: this is an evidence log. Sealing proves that a decision and its rationale hash were recorded at that time under that account key — it does not make the decision lawful, authorized, correct or a corporate act, and it does not prove the rationale document says what any summary claims (the rationale itself is not stored, so only its holder can open it against the hash). A Delaware AI-run-company law is a proposal, not enacted law; this service is a readiness and evidence surface, not incorporation, not a registered agent and not legal advice.
Related surfaces
The sealed-agreement flow a recorded decision can point at: /quote-to-contract.
For agents
This service as data: GET /v1/ai-officer-log. 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 AI-officer decisions 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. Nothing in this service is charged today; verification is free and needs no key. Markdown twin: /ai-officer-log.md.