Prism
A developer preview for bounded local agent execution, with an inspectable event trace, a contract-derived terminal run record, and fixed limits clearly separated from measured usage.
- Contribution
- I build the trace workflow and the interface for inspecting its result.
- Maturity
- Developer preview
Contract-derived simulation
Primary demonstration
Portfolio simulation screenshot derived from Prism v0.1.0 public source: run.completed, the result 3 words, and a v1 inspect-record excerpt with fixed limits. No Prism execution was captured; measured usage and cleanup receipts are absent from this CLI record.
Deterministic simulation
Contract-derived simulation from Prism v0.1.0 public source.
Public example checked 2026-09-12. Portfolio simulation screenshot derived from Prism v0.1.0 public source: run.completed, the result 3 words, and a v1 inspect-record excerpt with fixed limits. No Prism execution was captured; measured usage and cleanup receipts are absent from this CLI record.
Playback in this browser does not execute Prism, start a subprocess, call a provider, or read a local run.
Initial example · Ready to start
Count the words in: one two three
The result and receipt remain hidden until the sixth event.
- 01Goal accepted
- 02Tool requested
- 03Policy allowed
- 04Tool completed
- 05Provider finalized
- 06Run completed
This server-rendered reference stays available if the interactive controls cannot load.
Interactive controls load when this example comes into view.
If the interactive example stops responding, Reload this example.
Problem and workflow
The problem
A local agent run can end with a short answer while leaving the important sequence hidden. A developer still needs to see which goal was accepted, which tool the provider requested, whether policy allowed that request, and how the run reached completion. Those stages must stay in order, and the record shown afterward must keep its evidence layers straight. A fixed limit is different from measured usage. A lower-level lifecycle assertion is different from a field persisted by the CLI. This example makes those boundaries readable without executing Prism in the browser.
The workflow
The example follows the successful deterministic bounded-coordinator sequence documented in Prism v0.1.0. Start with the fixed word-count prompt, move through the six public event identifiers, and inspect the result only after run.completed. At completion, the receipt panel shows an explicitly labeled v1 inspect-record excerpt. A separate disclosure describes lifecycle facts asserted by pinned source tests; it is not a captured receipt and does not prove a sandbox or container execution.
01Walk the contract-derived trace
- 01The unstarted frame shows the fixed prompt. Start example presents goal.accepted; no result or receipt is available.
- 02Next event advances through provider.tool-requested, policy.allowed, tool.completed, and provider.finalized. Previous event moves back one stage and clears anything that belongs to a later state.
- 03The sixth stage is run.completed. Only now does the result 3 words appear and Inspect receipt become available.
- 04The v1 inspect-record excerpt contains fixed limits of two provider turns and one tool call, plus terminal status completed and answer 3 words. It contains no persisted measured usage or cleanup field.
- 05Close receipt hides the excerpt. Reset returns to the unstarted prompt, with the terminal result and receipt removed.
Engineering and evidence
Decision 01
A trace is meaningful only in its authentic order.
- Choice
- Store the six public event identifiers in a strict server-side fixture and let a bounded Prism-specific reducer move one position at a time.
- Consequence
- The interaction cannot skip ahead, present a result early, or turn a source sequence into a generic workflow.
Decision 02
Prism exposes evidence at different layers.
- Choice
- Keep the v1 CLI inspect-record excerpt separate from the lower-level lifecycle contract asserted by source tests.
- Consequence
- Fixed limits are not mislabeled as measured usage, and lifecycle assertions are not presented as fields captured in the persisted run.
Decision 03
The browser must not become an execution surface.
- Choice
- Project one validated fixture into a local state machine and render the complete walkthrough on the server.
- Consequence
- The page can explain the bounded run without starting a process, contacting a provider, reading local run data, or claiming runtime assurance.
Contribution and credits
I build the trace workflow and the interface for inspecting its result.
- My contribution is the trace workflow and the interface for inspecting its result.
- The pinned NOTICE credits Vora Technologies, LLC. The public metadata does not establish a sole personal authorship claim.
Current limits
- This is a contract-derived simulation from public source, not a recording or a live Prism run. No run ID, workspace, timestamp, process, host, container, or native execution was captured.
- The v1 record persists fixed limits but no measured usage or cleanup receipts. The lower-level lifecycle assertions are documented separately and do not prove sandboxing.
- Linux, KVM, QEMU, Firecracker, physical-X1 assurance, plugin digest approval, and ambient-authority experiments remain outside this example.
About this example
Contract-derived simulation from Prism v0.1.0 public source, checked September 12, 2026. GitHub marks release v0.1.0 immutable; its annotated tag resolves to pinned commit fcad9afece7a7c12395946f9dd3305de0250bc1c. The overview image shows this portfolio simulation. No Prism command was run and no runtime identifiers were captured or substituted. Fixed limits and terminal fields follow the public v1 record contract; lower-level lifecycle assertions are separate source-test facts, not captured inspect output.
Checked September 12, 2026
Evidence details
Portfolio simulation screenshot derived from Prism v0.1.0 public source: run.completed, the result 3 words, and a v1 inspect-record excerpt with fixed limits. No Prism execution was captured; measured usage and cleanup receipts are absent from this CLI record.
contract-derived · version 0.1.0 · revision fcad9afece7a7c12395946f9dd3305de0250bc1c