API reference

Ledger Outcome API

Ledger Outcome reconciles a past verdict against what actually happened, closing the calibration loop that turns the Trust Ledger into a self-sharpening dataset.

What it returns

On success the response returns recorded:true and the updated redacted entry, now carrying its outcome (status, note, and recorded_at). If the entry id is unknown, or the status is not one of the allowed values, it returns 404.

The body takes entry_id (the ledger_id from a prior verdict), a status of borne_out, contradicted, or unclear, and an optional note.

When to use it

Call Outcome after a verdict has played out, passing the ledger_id a readiness or execution decision returned. This is how agents make the ledger sharper over time: reconciled outcomes feed Institution Memory's borne-out rate and the platform-wide calibration in stats.

The endpoint authenticates the caller but does not consume a rate-limit slot; anonymous callers are permitted.

Notes and honesty

Only the three outcome statuses are accepted, and only a real entry id can be reconciled, so the calibration data stays clean. Recording is safe and never breaks; an unknown id simply returns 404. Educational calibration signal, never advice.

curl -s https://api.lyramindos.com/v1/ledger/outcome -H 'Content-Type: application/json' -H 'x-api-key: YOUR_KEY' -d '{"entry_id":"LEDGER_ID_FROM_A_VERDICT","status":"borne_out","note":"played out as read"}'
POST /v1/ledger/outcome · MCP lyramind_record_outcome

Questions

Where does entry_id come from?

It is the ledger_id returned by a prior verdict, such as a readiness or execution-readiness call. Pass it back here to reconcile that specific decision.

Which statuses are allowed?

Exactly three: borne_out, contradicted, or unclear. Any other value, or an unknown entry_id, returns a 404 so the calibration data stays clean.

Why reconcile outcomes?

Reconciled outcomes turn the ledger into a calibration dataset. They sharpen Institution Memory's borne-out rate for the name and the platform-wide calibration in ledger stats.

Related

See the live demo →Request access