A worked mechanism
Use conservation to expose a lost owner.
This descriptor-level example counts accepted completion handshakes as terminal outcomes. Intermediate issue and response events do not close a descriptor.
Accept eight descriptors
accepted = 8
The channel fronts allocate eight distinct live identities.
Complete three
completed = 3
Three completion handshakes retire their identities exactly once.
Account for the remainder
active = 5
Five identities must still belong to active state, including any error recovery.
Quiesce to zero
8 = 8 + 0
Close all remaining work through declared completion/cancellation semantics before reuse.
Work it through
A response vanished from the ledger
If counters report accepted=8, completed=3, active=4, one descriptor has no accounted-for owner. Counting eight issued fabric requests would not repair the gap.
The invariant fails by one identity: 8 ≠ 3 + 4.
Watch for this
If cancellation is a distinct terminal category, add it explicitly to the equation rather than silently deleting active work.
Check your reasoning
Cross-check allocation, terminal handshakes, live identity sets, first-error state, and reset policy at the same abstraction level.
Put it into practice
Explain the decision behind the design.
- Control a credited linkDefine ownership, return credits, and bounded outstanding work.→
- Schedule credited clients fairlyBalance arbitration policy, throughput, and starvation bounds.→
Continue the learning path

