alkdev/alknet
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

tasks: mark call/registry/handler-registration completed

Browse Source
This commit is contained in:
glm-5.2
2026-06-23 14:42:01 +00:00
parent 3aae9d1323
commit 31fd8a73ac
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
tasks/call/registry/handler-registration.md
View File

@@ -1,7 +1,7 @@
--- ---
id: call/registry/handler-registration id: call/registry/handler-registration
name: Implement Handler, HandlerRegistration, OperationProvenance, OperationRegistry, and OperationRegistryBuilder name: Implement Handler, HandlerRegistration, OperationProvenance, OperationRegistry, and OperationRegistryBuilder
status: pending status: completed
depends_on: [call/registry/operation-context] depends_on: [call/registry/operation-context]
scope: broad scope: broad
risk: medium risk: medium
@@ -199,4 +199,10 @@ imported overlays are dynamic at their respective scopes (ADR-024). The
## Summary ## Summary
> To be filled on completion Implemented `Handler`, `HandlerRegistration`, `OperationProvenance`,
`OperationRegistry` (register/registration/invoke/list_operations), and
`OperationRegistryBuilder` (new/with_local/with_leaf/with_leaf_provenance/with/build)
in `registry/registration.rs`. `invoke` enforces visibility (Internal from wire →
NOT_FOUND), ACL with authority switch (internal: true → handler_identity.as_identity(),
internal: false → caller identity), and handler dispatch. 21 unit tests pass; clippy
clean. Merged to develop.