- Home
- Product
- Decision record
Decision record
Every decision, replayable years later.
The systems that run your projects record what was spent and when. Capibud records why: what the committee knew, what it chose, who disagreed and what would reopen it, stored with the run it relied on. The log is append-only and hash-chained, and every engine run replays to an identical result.
- #1515waiting pack.pin 9c0e5b81d2a4
- #1516waiting mapping.confirm 73d57bf787d6
- #1517waiting run.committee d18d148da9bd
- #1518waiting pack.issue b62043186fb7
- #1519waiting decision.approve 5d7e3b3a34e2
Replay · run 7f3a…c21e
- Recorded
- 14 Sep 2026
- Seed · engine
- 4417 · 3.2
- Value after hurdles
- $1,180M
- Output digest
- e8b0…41d7
- Replayed
- 14 Sep 2028
- Value after hurdles
- $1,180M
- Output digest
- e8b0…41d7
Available today. Each engine run stores digests of its inputs, parameters and output, its seed and its engine version, and can be replayed to an identical result. Signed checkpoints can be verified with a public key.
One decision, five beats
From what it knew to a replay two years on
The Audit trail screen for an illustrative sanction decision. Open the record, see what the committee saw and chose, re-run it two years later, then try to change it.
Select a record to see what it holds.
Illustrative decision. The figures are not taken from a client project.
What a record holds
One page that answers “why did we do this?”
Minutes say what was decided. The record also keeps what the committee was looking at when it decided, so the decision can be re-examined on its own terms rather than with hindsight. Your project systems keep the transactions; the record keeps the reasoning behind the money. When an LP or a regulator asks a fund, years later, why it backed an asset, the answer is the record, not a reconstruction.
- 1The question
What was asked, the options on the table, and the envelope and bad-year floor the committee set. The options not chosen stay.
- 2What it knew
Every input as it stood on the day, traced to its cell, slide or page line. The industry pack is the version in force then, not whatever is current later.
- 3The run
Run id, seed, engine version and digests of inputs, parameters and output, so the run replays to an identical result.
- 4Votes and dissent
Each vote with its rationale. Dissent with its reasoning, beside the alternative it argued for, for as long as the decision stands.
- 5What reopens it
Tripwires: thresholds that reopen the decision if live data crosses them, checked by the brain on every scan.
- 6Its place in the chain
Nothing is overwritten. A later change is a new entry, hash-chained to the one before it.
Append-only, hash-chained
Try to change the past
Each entry in the audit log carries a hash of its own contents and of the entry before it. Change one figure and the hashes stop agreeing. Re-hash that entry and the next one stops agreeing. Rewrite everything up to the head and the head no longer matches the signed checkpoint.
What the chain does not do. It detects edits, deletions and truncation. Someone with privileged access to both the database and the local anchors could still replace the whole history. Signed checkpoints held somewhere independent close that gap; independent custody of checkpoints and RFC 3161 timestamping are on the roadmap.
- #1515The interactive chain needs JavaScript.
Illustrative. A short toy hash stands in for the SHA-256 digests Capibud stores.
Votes, dissent and tripwires
A record of judgement, not only of numbers
The engine produces the ranges. People make the decision. The record keeps both, so that a good decision with a bad outcome can be told apart from a bad decision.
Independent votesBefore discussion
Each member votes with a rationale: approve, approve with conditions, disagree and commit, reject or abstain. Collecting votes before discussion keeps the loudest voice from setting the answer.
Who supported this, and on what grounds?
DissentKept, not minuted out
A dissenting view is stored with its reasoning, beside the alternative it argued for, and stays attached to the decision for as long as the decision stands.
Did anyone see this coming?
TripwiresWatched by the brain
Thresholds that reopen the decision if live data crosses them. The brain checks them on every scan; a breach, or a close approach, becomes a proposal to revisit the decision.
When should we look at this again?
Outcome scoringWhen the result is known
When the outcome is recorded, the forecast frozen at decision time is scored against it, and the score feeds the calibration scorecard that later committee packs draw on.
Were our ranges honest?
Every change, the same way
Preview, approve, apply, undo
Committee decisions are one kind of change. Re-phasing a project, adding contingency or adopting a brain proposal go through the same path and land in the same record.
Preview
- Every change is previewed before it is applied.
- The apply is bound to the exact preview a person saw.
- If the plan has moved underneath it, a fresh preview is required.
Approve
- Routed by your delegation-of-authority matrix.
- Maker-checker, escalation and cumulative-change rules.
- Approvals re-validated against what the approver reviewed.
Apply and undo
- The final approval applies the change.
- The change is written to the append-only record.
- It can be undone, and the undo is recorded too.
Today and next
What is available now, and what is on the roadmap
Capibud is available to design partners as a deployment inside your own environment. We separate what runs today from what is planned.
| Area | Available today | Roadmap |
|---|---|---|
| Audit | Append-only, hash-chained log with verification; signed checkpoints that can be verified with a public key; run replay to an identical result; backup and restore drill | Independent custody of checkpoints, for example a write-once bucket in a separate account; RFC 3161 timestamping |
| Approvals | Preview before every change; maker-checker; approvals re-validated against what the approver reviewed | No change planned |
| Deployment | Runs on hardware or cloud you control, as a single node or container | Managed regional hosting; sovereign and air-gapped pods with customer-held keys |
| Certifications | None yet | SOC 2 Type II and ISO 27001 programme |
Capibud does not move funds or place orders. "Apply" changes a plan inside Capibud and nothing else. More on security and deployment.
Questions auditors ask
Before the first review
How decisions are made is on the capital committee page; how tripwires are watched is on the brain.
Can a past decision be replayed?
Yes. Each engine run stores digests of its inputs, parameters and output, its seed and its engine version, and replays to an identical result. The industry pack and parameters are the versions in force on the day, not whatever is current later.
What does a decision record hold?
The question and the options on the table, the run the committee relied on, votes with their rationale, dissent with its reasoning, the alternatives not chosen, and the tripwires that would reopen the decision.
Can a fund show an LP or a regulator why it backed an asset?
Yes. The investment committee paper, the run it rested on, the votes and dissent, and the limits and stresses as they stood on the day are kept together. Years later the run replays to an identical result, so the answer is what the committee saw, not a reconstruction with hindsight.
Can the record be edited after the fact?
No. The audit log is append-only and hash-chained, so a later change is a new entry, never an edit, and edits, deletions and truncation are detected. Signed checkpoints can be verified with a public key; independent custody and RFC 3161 timestamping are on the roadmap.
Does Capibud move funds or place orders?
No. “Apply” changes a plan inside Capibud and nothing else. Every change is previewed, routed through your delegation of authority, written to the record and can be undone.
Make your next decision replayable.
A Decision Sprint runs one real decision on your own files in six weeks and leaves you with its full record.