Skip to content

workflow engine: meter executions under the routed module's compute resource type - #24227

Merged
DylanTinianov merged 11 commits into
developfrom
cre-confidential-compute-metering
Nov 19, 2026
Merged

DylanTinianov merged 11 commits into
developfrom
cre-confidential-compute-metering

Conversation

@DylanTinianov

@DylanTinianov DylanTinianov commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

What

The confidential module declares how its executions bill — ComputeResourceType() returning cre:workflow:confidential-compute, right next to where it reports the enclave-measured ComputeDurationMs. The engine asks the routed module for that type (TriggerRouter from the common bump) and stamps it on its base identity at emit; modules without a declaration meter as ordinary cre:workflow:compute.

The wiring layer is untouched, and the engine names no runner.

Why

Billing can distinguish enclave compute downstream while the metering decision lives with the module that causes it. Adding a future execution environment is one method on the new module.

Rollout

No sequencing: the engine emits exactly one record per execution in every mode; old engines emit cre:workflow:compute, new ones the confidential type for enclave runs — the two never mix in one scored event downstream.

DylanTinianov and others added 2 commits November 18, 2026 10:02
Co-Authored-By: Claude Code <noreply@anthropic.com>
Executions of triggers whose subscription requires a TEE now emit
cre:workflow:confidential-compute instead of cre:workflow:compute, so
billing can distinguish enclave compute downstream. The value is
unchanged: the enclave-measured duration already returned in the
execution result. The record's resource pool follows the resource type.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

👋 DylanTinianov, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

@github-actions

Copy link
Copy Markdown
Contributor

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

@github-actions

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

elatoskinas
elatoskinas previously approved these changes Nov 18, 2026
Co-Authored-By: Claude Code <noreply@anthropic.com>
@DylanTinianov
DylanTinianov requested a review from a team as a code owner November 18, 2026 15:11
@DylanTinianov DylanTinianov changed the title workflow engine: meter TEE-routed executions as confidential compute Workflow Engine: meter TEE-routed executions as confidential compute Nov 18, 2026
The resource-type constant is on common's main now; every module is
tidied against it (make gomodtidy).

Co-Authored-By: Claude Code <noreply@anthropic.com>
@DylanTinianov DylanTinianov changed the title Workflow Engine: meter TEE-routed executions as confidential compute workflow engine: meter executions under the routed runner's usage identity Nov 18, 2026
DylanTinianov and others added 3 commits November 18, 2026 13:18
The engine stops reading trigger TEE requirements and keeping a route
map: the requirement-selecting module reports which runner a trigger
routed to, and the record carries that runner's declared usage
identity. The wiring declares the confidential runner's identity
(cre:workflow:confidential-compute) where the confidential module is
constructed; the engine code names no runner. Carries the
chainlink-common bump for the UsageIdentity/UsageRouter addition.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
The engine's call site follows the renamed interface:
UsageIdentityForTrigger returns the declared identity directly.

Co-Authored-By: Claude Code <noreply@anthropic.com>
The confidential module declares its compute resource type next to
where it reports the enclave's duration; the engine asks the routed
module for it and stamps the pool on its base identity at emit. The
engine's wiring layer is untouched.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@DylanTinianov DylanTinianov changed the title workflow engine: meter executions under the routed runner's usage identity workflow engine: meter executions under the routed module's compute resource type Nov 18, 2026
DylanTinianov and others added 2 commits November 18, 2026 15:16
Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
@DylanTinianov
DylanTinianov added this pull request to the merge queue Nov 19, 2026
Merged via the queue into develop with commit 983bbfa Nov 19, 2026
342 of 347 checks passed
@DylanTinianov
DylanTinianov deleted the cre-confidential-compute-metering branch November 19, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants