Queued work should look the same no matter where it came from.

Runtime, browser and MCP lanes can differ in execution surface, but the queue packet should stay constant: what was proposed, why it queued, who owns it, what happens next and what export survives if released.

Bundle schema

Review should read like one case file, not a reconstruction project.

That is what makes the queue product-grade for ops and risk.

Intent

What was proposed

Action, counterparty, amount, purpose and business context should all sit in the same bundle without needing a second system.

Reason

Why it queued

Threshold, counterparty posture, anomaly context and policy version should explain the queueing reason in one read.

Owner

Who decides next

One reviewer, team or finance owner should be named directly in the bundle so the path does not diffuse into side threads.

Resolution

Approve, reject or step up

The bundle should carry the exact next move, not just surface a risk score and hope a human figures out the rest.

Continuity

Proof and finance should still inherit the same record

If released, the action should become proof packet and finance close packet without changing identifiers or explanation shape.

Reuse

Linkable, exportable and reusable later

Review packets should survive beyond the queue itself as artifacts for ops, risk, audit and buyer proof.