Publish runtime state

Console configuration does not affect app traffic until the environment has runtime state the data plane can serve. Publish after changing controls, their app integrations, credits, plans, or customer rules that your app expects Valqio to enforce.

Publish flow

1. Model or update the Feature, Usage Control, Limit, plan, or customer policy.
2. Add or update a control's resource and verb under Use in your product.
3. Preview the runtime state for the selected environment.
4. Check control counts and published app integrations.
5. Publish the environment.
6. Generate or refresh the SDK client.
7. Run the integration's side-effect-free test.
8. Send an app request and inspect transaction evidence.

What publishing proves

A published runtime state should answer:

• Which generated action paths can the SDK call?
• Which meters, limits, and plans are active for the environment?
• Which environment sequence is the data plane serving?
• Are generated client bindings aligned with the published configuration?
• Can Workbench and app traffic reach the same allow or deny outcome?

Publishing is the handoff from configuration to runtime decisions.

Generated clients

When a published control has an app integration, generated clients expose a domain-shaped callback helper:

await customer.actions.invoices.send.run(
  {
    quantity: 1,
    idempotencyKey: `sendInvoice:${requestId}`,
  },
  async () => sendInvoice(),
)

Refresh generated clients after publishing changes that add or retire integrations. A published resource and verb are immutable; create a replacement integration when the product API must change. Your application should fail readiness checks rather than run billable work with stale bindings.

Generated client files come from Console or Valqio's SDK tooling for your project.

Safe rollout

Use separate environments for staging and production. Publish and test staging first, then publish production when the app, SDK bindings, runtime key, and evidence checks are ready.

If production behavior looks wrong, stop new product rollout traffic, inspect decision evidence, and publish a corrected runtime state before retrying.