# K1341 — waitset object registration

`Waitset` belongs to one process generation and stores up to `N` object
registrations. A registration binds a kernel-validated typed object name to a
nonempty subset of READ, WRITE and CLOSED interests. The adapter must verify
the caller's live source handle before registration; raw user input cannot
mint an object name. A typed object may appear at most once in a waitset.

Registration checks owner, object name, interest bits, duplicate entry,
capacity, slot conversion and generation overflow before publishing. It
returns a generation-tagged ID. `query` and `unregister` require the current
ID and the waitset owner. Unregistering frees the slot while retaining its
generation; the next registration there gets a new ID, and the old ID returns
`BadFd`. Failed calls leave the full snapshot unchanged. An exact same numeric
name with a different object kind is a distinct typed object.

K1341–K1344 require host positive and boundary tests, a duplicate-bypass
mutant rejected by a negative test, and an AArch64 `no_std` metadata build.
K1345 requires native EL0 registration over six direct/UEFI QEMU profiles on
one experimental Image. Readiness signaling, timeout races and waitset close
lifetime are later gates; this registration gate does not claim them or
product release acceptance.