Run a rule and inspect results

Replace the placeholders with values from your own authorized scope before copying this prompt into an MCP client.

Inputs

• {{workspace_id}} Stable workspace ID.
• {{application_id}} Stable application ID.
• {{rule_id}} Authorized published rule ID.
• {{version}} Exact published version.
• {{bindings}} Typed parameter bindings for that version.
• {{compiled_program_digest}} Exact programDigest returned by the definition read.
• {{request_key}} Stable key for the run.

Prompt

In {{workspace_id}} / {{application_id}}, call read_v2_program with application.rule.version.read and ruleId {{rule_id}} to read the current publication. Verify Published status and version {{version}}.
Use execute_v2_expression_rule_program with application.rule.run, ruleId {{rule_id}}, bindings {{bindings}}, expectedVersion {{version}}, expectedProgramDigest {{compiled_program_digest}} and idempotency_key {{request_key}} only where the current publication is authorized.
The server must reject a current publication that differs from the inspected version or digest. Do not follow a changed head automatically.
Read application.rule.run.read using the returned workflow ID, and report the actual bound version, status, committed units and a bounded result check.
Stop on a publication mismatch or denied scope.
If submission response is lost, reconcile the original intent before any new run.

Example inputs

After publishing the disposable rule, use {"InputAmount": "12.50000000"} as bindings if the bounded read returned that reviewed value. Confirm the workflow reports one committed unit and a receipt, and then read the full InputB coordinate. It should contain 15.00000000. This sample requires a fresh destination cell.

Tools used include read_v2_program, execute_v2_expression_rule_program. See the module guidelines and tool index.