Add trusted attachment staging and signed native worker binding - #63
Merged
Conversation
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.
Summary
This stage completes the next planned Phase 2 slice: trusted attachment staging and per-job signed/native worker-attempt composition.
What changed
ArtifactBoundary.stage_bytesso already-bounded attachment bytes use the same owner, size, MIME, digest, retention, and atomic-publication controls as trusted path copy-in.attachment.stage.v1staging with:POST /api/v1/execution/attachmentsand generated OpenAPI/TypeScript contracts.NativeRecipeWorkerAttemptFactoryandbuild_native_recipe_coordinator_factory:Safety and rollout
The normal Cortex application remains default-off. Both routes require a ready explicit
qualificationlifecycle. Configuration creates no process; an absent signed package, broker binding, or reviewed native process factory remains blocked.Verification
compileall, contract generation, andgit diff --check: passedNext gate
The next planned stage is an end-to-end durable-coordinator qualification run through the packaged signed worker, covering staged transform, in-flight cancellation, retention, atomic publication, owner isolation, and complete native cleanup. Production signing/trust and external review remain optional official-release hardening.