The runtime ID is the name of one run. The table names are where the OS stored the result objects. This page checks those tables for you after agent operator authentication.
Agent-scoped proof surface
FinanceOps MVP runtime proof review.
This agent operator surface reads the latest FinanceOps MVP runtime run after authentication and shows whether the OS wrote the required proof records: Work Order, execution binding, tool command, result contract, usage receipt, callback record, ledger reference, attestation, and runtime audit event.
Agent verification
Latest FinanceOps MVP run.
Enter the agent credential, then load the latest run or inspect a specific runtime run ID. The proof data is not exposed without the agent credential.
StatusLoading...
Result objects
Required records
Supabase inspection guide
How to find the records manually
In Supabase, open Table Editor, choose one of the tables below, and use a filter. For most tables, filter by task_token. For the main run table, filter by runtime_run_id. You do not have to inspect every table manually once this surface shows all required records found.
financeops_mvp_runtime_runs
Filter: runtime_run_id
Filter: runtime_run_id
agent_task_runs
Filter: task_token
Filter: task_token
wever_intake_work_order_dispatches
Filter: work_order_id
Filter: work_order_id
work_order_execution_bindings
Filter: task_token
Filter: task_token
tool_execution_commands
Filter: task_token
Filter: task_token
tool_execution_result_events
Filter: task_token
Filter: task_token
agent_result_contracts
Filter: result_contract_id
Filter: result_contract_id
agent_usage_receipts
Filter: usage_receipt_id
Filter: usage_receipt_id
agent_callback_deliveries
Filter: callback_id
Filter: callback_id
agent_ledger_events
Filter: ledger_event_id
Filter: ledger_event_id
agent_result_attestations
Filter: attestation_id
Filter: attestation_id
runtime_binding_events
Filter: task_token
Filter: task_token
Raw envelope
Machine-readable result
Loading...