Re: First Draft of did:nostr method

Hi Melvin,
Fantastic to see the did:nostr  FPWD published – this aligns with something I've been exploring for using Nostr as an identity layer for people, AI agents, and persistent objects within linked metaverse/immersive environments.
Considering the spec currently defines a DID document primarily derived statically from the public key (without update/revoke operations), I'm particularly interested in how this model might represent moredynamic entities like AI agents (whose capabilities or associated service endpoints might evolve) or global objects (which might change state or context). Does this lean towards did:nostr acting as the stable, cryptographic root identifier, with dynamic aspects perhaps best reflected through associated, queryable Nostr events (like Kind 0 or potentially new kinds) rather than within the resolved DID document itself? I might redo my layers documents and see if i can get it to make sense to me in the next week or two in this context.
Congratulations again on reaching this stage! Looking forward to digging into the details.
Best regards,
DR JOHN O'HARE

Chief Hallucination Officer | Spatial AI Lead

DREAMLAB<https://thedreamlab.uk/>

MediaCity Immersive Technologies Innovation Hub
HOST, Blue, MediaCity UK, Salford
Contact me:  LinkedIn<https://www.linkedin.com/in/jjohare/> | Email<mailto:j.ohare5@salford.ac.uk>

Narrative Goldmine Research Pages<https://narrativegoldmine.com/#/graph>