Specify native invocation custody #31
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/docs!31
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/docs-owned-native-invocations"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe authenticated submission, exact reply framing and retained caller identity. Tie cancellation and retirement obligations to the actual delivered invocation and its endpoint context.
Depends on #30 (
feature/docs-owned-private-vspaces).Separate this feature from the preceding changes.
Document this contract and include its manual text in the published source-bound manual.
Runtime implementation and release-image acceptance remain tracked by the relevant component PRs and the phase acceptance issue.
This branch also includes the completed downstream features from #32, #33, #34.
WIP: Specify native invocation custodyto Specify native invocation custodyThe specification and its published manual content are complete for review. Native implementation and release-image acceptance remain with the component work; they do not prevent review of this documentation change.
Merged the approved downstream work from #32, #33, #34. The upstream PR retains its own remaining scope and completion requirements.
The prepared history keeps #32–#34 and the merged parent’s manual layout fixes. It also replaces two broken section references with links to the owning component contracts. The original branches are unchanged. This prepared commit needs renewed review before merging.