HYBRID-CHAINDEVELOPERS
DOCUMENTATIONv2
POST

Deterministic execution

Create trigger

/api/v2/execution/triggers
AUTHENTICATIONBearer token · execution:writeAUTHORITATIVE OWNERexecution-serviceCONTRACT AUTHORITYCapability registry · plannedSTATUSPlanned · not executable
PLANNING CONTRACT · NOT CALLABLE

This page describes intended capability and integration boundaries so people and agents can prepare safely. Do not send this request or register it as an executable tool. Wait until the capability registry marks it implemented-contract, then re-fetch the deployed OpenAPI document and build the request from that machine contract.

PURPOSE + BUSINESS CONTEXT

Planned capability: create a policy-bound trigger for a deployment.

WHEN THIS CALL IS USEFUL

Do not call or register this operation as an executable agent tool yet. Use this page to plan the future trigger workflow; enable it only after the status becomes implemented-contract and the exact operation appears in deployed OpenAPI.

OUTCOME · Planned · Create or advance

What changes

None today: this route is not executable. Its intended behavior is: when promoted, creates trigger configuration only. It admits no schedule, event, API call, execution, or business action until separately activated under current policy.

WHY IT MATTERS

  • Lets people and agents prepare for trigger without falsely presenting roadmap scope as a live capability.
  • Gives people and agents a contract-backed way to advance trigger.
  • Makes package and execution lineage reproducible by exposing the commitments an agent needs to validate before trusting a result.

ISOLATION + AUTHORITY

Package, build, deployment, invocation, node, input, output, and receipt authorities remain distinct. No execution operation may change frozen trading, matching, prediction, ingress, publisher, allowlist, suspension, market-status, or traffic controls, and no result grants external-domain authority. This planning record grants no runtime authority, and only deployed OpenAPI can define an executable public contract.

BEFORE YOU CALL

  • First confirm that this operation is marked implemented-contract and exists in the currently deployed OpenAPI document; until then, no production request is valid.
  • Its capability-registry profile is provisional integration guidance, not an executable request schema.
  • Authenticate at the documented boundary: bearer+scope.
  • Treat the proposed deployment_uuid (body), expected_deployment_version (body), trigger (body), input_template (body), execution_policy (body), step_up_token (body) as planning input only; re-generate the request from deployed OpenAPI before making a call.
  • Use one Idempotency-Key only for retries of the same byte-equivalent logical mutation.
  • Resolve the exact artifact, schema, runtime, node, resource, and policy commitments relevant to this stage.

WHAT TO DO NEXT

  • Keep this operation disabled in clients, agents, SDKs, and workflow automation while it remains planned-contract.
  • Use the stated owner, lifecycle, authority boundary, and provisional trigger profile to prepare requirements and conformance tests without sending a request.
  • Monitor the capability registry for implemented-contract, then re-fetch deployed OpenAPI and validate its exact security, parameters, schemas, responses, and agent metadata before enabling the integration.

AGENT GUIDANCE

  • Never call this planned contract, include it in an executable tool registry, or infer runtime availability from this readable page.
  • Its capability-registry profile is provisional integration guidance, not an executable request schema.
  • Use trigger only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
  • Treat the proposed deployment_uuid (body), expected_deployment_version (body), trigger (body), input_template (body), execution_policy (body), step_up_token (body) as planning input only; re-generate the request from deployed OpenAPI before making a call.
  • Keep draft, validation, publication, deployment, activation, invocation admission, execution completion, external effect, receipt, and finality as separate stages.
  • After a timeout or conflict, read authoritative state before deciding whether an equivalent retry is safe.
  • When implementation lands, discard generated requests based on this planning record and rebuild them from the deployed OpenAPI operation.
MACHINE CONTRACT

This operation is a non-executable planning contract. Its capability-registry record defines the intended owner, parameters, responses, and integration boundary until an implemented Rust OpenAPI operation replaces it.

EXTENDED INTEGRATION GUIDANCE

Readable request and response reference

Examples describe the reviewed planning contract and remain non-executable until promoted into OpenAPI.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE
AuthorizationheaderRequired

Bearer tokenCredential containing execution:write authority.EXAMPLEBearer hc_live_…

Idempotency-KeyheaderRequired

ASCII string · 1–128Caller-generated stable key reused for retries of the same logical mutation.EXAMPLEpost-api-v2-execution-triggers-request-001

deployment_uuidbodyRequired

32-character identifierACTIVE owner-scoped deployment selected after current-state reconciliation.EXAMPLE8a7b6c5d4e3f2109876543210fedcba9

expected_deployment_versionbodyRequired

integer · ≥1Exact deployment policy version bound to the trigger.EXAMPLE2

triggerbodyRequired

discriminated SCHEDULE | EVENT | API objectTyped trigger with bounded cadence or allowlisted event/topic and filters. Arbitrary webhooks and expressions are rejected.EXAMPLE[object Object]

input_templatebodyRequired

allowlisted binding objectTyped mappings into the package input schema without secrets or executable expressions.EXAMPLE[object Object]

execution_policybodyRequired

bounded trigger policy objectConcurrency, deduplication, timeout, retry, and failure posture no wider than deployment policy.EXAMPLE[object Object]

step_up_tokenbodyRequired

purpose-bound tokenFresh EXECUTION_TRIGGER_CREATION authorization bound to deployment, trigger, template, and policy.EXAMPLEhcsu_…

REQUEST

JSON body example

{
  "deployment_uuid": "8a7b6c5d4e3f2109876543210fedcba9",
  "expected_deployment_version": 2,
  "trigger": {
    "type": "EVENT",
    "topic": "invoice.evidence.received",
    "filters": {
      "status": "ACCEPTED"
    }
  },
  "input_template": {
    "evidence_commitment": "$.event.commitment",
    "invoice_total": "$.event.total"
  },
  "execution_policy": {
    "max_concurrency": 1,
    "deduplication_window_seconds": 3600,
    "max_attempts": 2
  },
  "step_up_token": "hcsu_…"
}

RESPONSES

Status and payload examples

201A DRAFT trigger bound to one deployment version, typed configuration, input template, and execution policy returned; it admits no events yet.Not executable · JSON RESPONSE+
{
  "result": "See the operation's authoritative OpenAPI response schema."
}
INTEGRATION DECISION
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from isolated execution plans, simulations, approvals, runs, artifacts, logs, and immutable receipts through an implemented operation.
ESCALATE WHEN
Escalate when execution may have started but no terminal receipt exists, or when inputs, artifacts, isolation, and output commitments disagree.
400A typed field, identifier, digest, expected version, step-up token, request signature, or idempotency key is malformed.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "A typed field, identifier, digest, expected version, step-up token, request signature, or idempotency key is malformed."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from isolated execution plans, simulations, approvals, runs, artifacts, logs, and immutable receipts through an implemented operation.
ESCALATE WHEN
Escalate when execution may have started but no terminal receipt exists, or when inputs, artifacts, isolation, and output commitments disagree.
401The bearer credential is missing, expired, or invalid.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "The bearer credential is missing, expired, or invalid."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from isolated execution plans, simulations, approvals, runs, artifacts, logs, and immutable receipts through an implemented operation.
ESCALATE WHEN
Escalate when execution may have started but no terminal receipt exists, or when inputs, artifacts, isolation, and output commitments disagree.
403The principal lacks execution:write, workspace ownership, package/deployment/trigger authority, required review, or a fresh purpose-bound authorization.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "The principal lacks execution:write, workspace ownership, package/deployment/trigger authority, required review, or a fresh purpose-bound authorization."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from isolated execution plans, simulations, approvals, runs, artifacts, logs, and immutable receipts through an implemented operation.
ESCALATE WHEN
Escalate when execution may have started but no terminal receipt exists, or when inputs, artifacts, isolation, and output commitments disagree.
404The package, artifact, validation, deployment, trigger, runtime profile, action authority, or referenced owner-scoped resource does not exist in the authenticated boundary.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "The package, artifact, validation, deployment, trigger, runtime profile, action authority, or referenced owner-scoped resource does not exist in the authenticated boundary."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from isolated execution plans, simulations, approvals, runs, artifacts, logs, and immutable receipts through an implemented operation.
ESCALATE WHEN
Escalate when execution may have started but no terminal receipt exists, or when inputs, artifacts, isolation, and output commitments disagree.
409The version, lifecycle, artifact digest, validation, publication, deployment, trigger, environment, deduplication state, or Idempotency-Key conflicts.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "The version, lifecycle, artifact digest, validation, publication, deployment, trigger, environment, deduplication state, or Idempotency-Key conflicts."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from isolated execution plans, simulations, approvals, runs, artifacts, logs, and immutable receipts through an implemented operation.
ESCALATE WHEN
Escalate when execution may have started but no terminal receipt exists, or when inputs, artifacts, isolation, and output commitments disagree.
422Source, manifest, schema, dependency, capability, reproducibility, visibility, sandbox, resource, egress, secret-binding, input, trigger, or downstream domain policy rejected the request.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "Source, manifest, schema, dependency, capability, reproducibility, visibility, sandbox, resource, egress, secret-binding, input, trigger, or downstream domain policy rejected the request."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from isolated execution plans, simulations, approvals, runs, artifacts, logs, and immutable receipts through an implemented operation.
ESCALATE WHEN
Escalate when execution may have started but no terminal receipt exists, or when inputs, artifacts, isolation, and output commitments disagree.
503Artifact storage, validator, builder, execution scheduler, isolated runtime, Identity, policy, evidence, node attestation, or owning domain is unavailable; no unverified state is inferred.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "Artifact storage, validator, builder, execution scheduler, isolated runtime, Identity, policy, evidence, node attestation, or owning domain is unavailable; no unverified state is inferred."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from isolated execution plans, simulations, approvals, runs, artifacts, logs, and immutable receipts through an implemented operation.
ESCALATE WHEN
Escalate when execution may have started but no terminal receipt exists, or when inputs, artifacts, isolation, and output commitments disagree.

OPERATIONAL NOTES

Security and lifecycle guarantees

  • The Rust gateway validates the public contract and routes only to the authoritative owner; clients never address internal services directly.
  • Mutations are retry-safe only when the same Idempotency-Key and canonical request body are reused.
DOCUMENTATION STATUS

This planned contract now defines its public parameters, authorization boundary, replay behavior, responses, and authoritative owner. It remains non-executable until its owner adapter and conformance tests are promoted into the Rust gateway.

Return to the V2 directory ↗