adk_run_registry (erlang_adk v0.7.0)
View SourceProcess registry and bounded terminal-run retention for adk_run.
Active invocations are retained for as long as they execute. Completed invocations are retained for replay, subject to both their own retention timer and this registry's global count limit. The registry monitors every invocation so stale process identifiers are never returned deliberately.
Summary
Functions
Resolve only when the caller presents the exact immutable owner scope. Unknown and cross-owner runs intentionally have the same result.
Register a run with immutable boundary metadata.
Functions
-spec child_spec(map()) -> supervisor:child_spec().
Resolve only when the caller presents the exact immutable owner scope. Unknown and cross-owner runs intentionally have the same result.
Register a run with immutable boundary metadata.
owner_scope is an opaque SHA-256 digest minted by a trusted boundary. It is intentionally not exposed through lookup/1 or status responses. Runs started through local Erlang APIs may omit it; production network/UI boundaries should always set it and use lookup_authorized/2.
-spec start_link() -> gen_server:start_ret().
-spec start_link(map()) -> gen_server:start_ret().
-spec stats() -> map().