Library · Workflows & capabilities
Bounded Execution Ledger
Keep a task request, handler result and execution evidence together, including failures and refusals.
Repository: CinvanaAI/bounded-execution-ledger
Recorded synthetic example. Source with a complete offline example.
See the idea in action.
complete: hello ledger; failed invalid input; denied request never invokes handler; three durable runs.
A registered text-normalizing handler and an explicit permission decision.
{
"kind": "captured synthetic execution projection",
"command": "npm run demo",
"input_example": "examples/first-handler.mjs",
"observed_output": {
"success": "complete",
"output": "hello ledger",
"failed": "failed",
"denied": "denied",
"handlerCalls": 2,
"durableRuns": 3
},
"projection_note": "Selected fields from a successful local run. Machine paths, temporary identifiers and execution timestamps are omitted. Re-run the linked example for fresh evidence."
}Try the example.
From the repository root, follow the dependency requirements in the README. This example uses supplied synthetic material.
npm ci npm run demo
complete: hello ledger; failed invalid input; denied request never invokes handler; three durable runs.
Complete setup and instructions ↗The interesting part.
Evidence of what was requested and returned belongs to the execution boundary itself.
Where it came from.
Executor and owner-scoped record substrate from Skeleton Execution Environment.
Provides a standalone package around preserved success, denial and failure semantics.
The lineage link describes the source; it does not require installing the full desktop.
Follow the family: Skeleton and the ownership rebuild