Module identity 

Explains the identities used to submit, manage, and coordinate tasks.

Value	Meaning
TaskId	One submission in the current process
Task name	Registry uniqueness key and diagnostic label
Controller slot	Key that coordinates competing submissions

application submission
     ├── direct add ─────────► TaskId + task name ──► registry
     └── controller submit ──► TaskId + slot ───────► controller ──► registry

Taskvisor allocates the ID before the first admission decision. The same ID follows queued work, every retry, terminal cleanup, and controller rejection. Several task names may use the same controller slot.

A name can be reused after registry membership ends and Taskvisor has observed the physical exit of any force-aborted actor with that name. Reuse allocates a new TaskId. IDs come from a process-local u64 sequence, are not persisted, and cannot be reconstructed through the public API. Returned IDs are never zero and never wrap. The next allocation after exhaustion panics. Store a separate application ID when identity must survive a process restart.

Structs

TaskId

Opaque identity of one task submission within the current process.