Build and inspect a sealed plan

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.
• {{program_id}} Active Python source ID.
• {{version}} Exact active source version.
• {{parameters}} Typed parameter values.
• {{delegation_id}} Active execution delegation for this caller and application.
• {{delegation_version}} Exact active delegation version.
• {{request_key}} Stable build-admission key.

Prompt

In {{workspace_id}} / {{application_id}}, use python.program.read to confirm {{program_id}} version {{version}} is Published. Verify that {{delegation_id}} version {{delegation_version}} permits python.program.build for the current subject.
Read application.state.read and pass metadataRevision, policyRevision, and schemaEpoch as expectedMetadataRevision, expectedPolicyRevision, and expectedSchemaEpoch.
Call execute_v2_python_program_build with python.program.build, programId {{program_id}}, programVersion {{version}}, parameters {{parameters}}, delegationId {{delegation_id}}, delegationVersion {{delegation_version}}, and idempotency_key {{request_key}}.
Include scheduleId and scheduleVersion. Pass null for both for a direct build.
Read the returned build ID with read_v2_python_program_build.
When sealed, inspect section Plan using read_v2_python_program_build_artifact. Start with cursor null and pass nextCursor back to read subsequent pages within a bounded review. Decode chunkBase64 and compare the complete section to sectionDigest.
Report the digest, effect scope and any diagnostics.
Stop before execution or if the build fails or includes unexpected effects.

Validate, Test and activate first

Use the Python source example. Save automatically starts Validation; poll its task and resolve diagnostics until validation seals successfully. Use python.program.test with the exact source, parameters and current pins, then inspect the complete Impact artifact. Test uses private state and does not activate or run the source. Activate the exact version using python.program.publish, then refresh application pins before admitting the Plan build above.

A Test artifact cannot become a runnable plan. Run uses a separately built Plan under current execution authority. Its inputs may differ from the earlier Test baseline; inspect those revisions and test again when that matters to the decision. For a multiunit plan, inspect its actual checkpoint boundaries. A later failure does not undo earlier published units.

Tools used include read_v2_program, execute_v2_python_program_build, read_v2_python_program_build, read_v2_python_program_build_artifact. See the module guidelines and tool index.