Identity and authority
DIDs identify the signer; lineage and policy explain what that signer is allowed to do.
Registration is one part of a lifecycle
The node has a concrete identity-registration handler. Generic update, revoke, and delegate variants do not all share that implementation. Direct root registration, agent issuance, and key/permission lifecycle paths are separately gated in the inspected executor.
Use precise standards language
OAS uses DID-compatible identity conventions and cryptographic documents. Compatibility with W3C DID formats should not be described as OAS being a W3C-issued or endorsed standard.
A username or .sigil name is a human-readable resolution layer. Resolve it to the underlying identity and use the correct authority checks.
Recovery uses a dedicated ceremony
The dedicated recovery path combines guardians, thresholds, timelocks, and a panic-abort mechanism. Legacy IdentityRecover is not a substitute for the current ceremony.