Repository navigation
workflow engine: meter executions under the routed module's compute resource type - #24227
Merged
Merged
Conversation
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>
product-security-plaid-production
Bot
requested review from
cedric-cordenier and
george-dorin
November 18, 2026 15:02
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! |
Contributor
|
I see you updated files related to
|
Contributor
|
✅ No conflicts with other open PRs targeting |
elatoskinas
previously approved these changes
Nov 18, 2026
Co-Authored-By: Claude Code <noreply@anthropic.com>
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>
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>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
cedric-cordenier
previously approved these changes
Nov 18, 2026
Co-Authored-By: Claude Code <noreply@anthropic.com>
cedric-cordenier
approved these changes
Nov 19, 2026
nolag
approved these changes
Nov 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The confidential module declares how its executions bill —
ComputeResourceType()returningcre:workflow:confidential-compute, right next to where it reports the enclave-measuredComputeDurationMs. The engine asks the routed module for that type (TriggerRouterfrom the common bump) and stamps it on its base identity at emit; modules without a declaration meter as ordinarycre: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.