Aller au contenu principal

Plan Before Mutate: Dry-run & Confirmation Token

Preview workflow before any GAM write: readable plan, credit cost, irreversible risks, time validity and confirmation token.

REST endpoints

MethodPathDescriptionCredits
POST/api/campaigns/{id}/dry-runPreview a campaign deploy without a GAM write0
POST/api/jobs/{id}/deployRun a confirmed deploy5
POST/api/jobs/{id}/deployment-planBuild the plan of a staging draft0
POST/api/inventory/blueprints/{id}/pushBlueprint push with diff and token0 / 0.5 unit

MCP tools

ToolDescriptionCredits
campaign(action='create_draft')Create a staging draft before the GAM mutation0
campaign(action='deploy', dryRun=true)Return the ExecutionPlan and the confirmation token0
campaign(action='deploy', confirmationToken=...)Consume the token and execute5
campaign(action='create_display', dryRun=true)Display forecast + plan before creation0
push_inventory_blueprint(dryRun=true)Full blueprint diff before push0
push_inventory_blueprint(confirmationToken=...)Confirmed blueprint push to GAM0.5/unit

Examples

Two-step campaign deploy

{
  "tool": "campaign",
  "arguments": { "action": "deploy", "jobId": "job_8b2a", "dryRun": true }
}
// -> ExecutionPlan { mutations, estimatedCost, irreversible, planValidUntil, confirmationToken }

{
  "tool": "campaign",
  "arguments": { "action": "deploy", "jobId": "job_8b2a", "confirmationToken": "tok_9c3f", "dryRun": false }
}

Notes

  • • The token is tied to the tenant, the operation type and the canonical hash of the plan.
  • • dryRun=true produces no GAM write.
  • • Irreversible risks are shown before confirmation.
  • • An expired plan must be regenerated before execution.