For readers already familiar with existing object-security and credential formats, here is how Lumions relate to prior art.

Object and message security formats:

• COSE -- CBOR Object Signing and Encryption. A signed and encrypted binary object, an Internet Standard, widely deployed in passkeys and mobile credentials. It is in the same area as Lumions, but much larger.
• JOSE (JWS/JWE/JWK) -- the JSON predecessor of COSE, carrying known design hazards around in-band algorithm choice. Weaker than COSE for a binary, deterministic object.
• CMS -- Cryptographic Message Syntax. The long-established ASN.1 signed and encrypted object. Heavy toolchain, poor fit for constrained producers.

Serialisation and determinism:

• CBOR -- the binary serialisation under COSE. Too heavy for Lumions.
• CDDL -- a grammar language for CBOR and JSON structures. Too heavy for Lumions.
• Deterministic encoding (CDE, and the competing dCBOR profile). The Lumion RFC states abstractly that we may require something like this in future.

Structured data and selective disclosure:

• Gordian Envelope -- a deterministic binary Merkle structure with holder-side redaction, the closest existing design to the Lumion's structural core. Experimental, single-origin, and chained to a contested determinism profile, so a reference rather than a dependency.
• ISO mdoc (18013-5) and SD-JWT VC -- credential formats with per-element selective disclosure by salted digests. Prior art for partial disclosure; we differ in binding disclosure to the row's name.

Content addressing:

• Multihash / CID (multiformats) -- a content hash encoding that identifies the hash algorithm used. The natural realisation of the Lumion's content-derived name.

Access control models and credentials:

• NIST RBAC and the cryptographic-RBAC / RBE literature -- the access-control model and its cryptographic enforcement, discussed above.
• W3C Verifiable Credentials, Bitstring Status List, Controlled Identifiers -- portable signed claims, published revocation status, and key-to-identifier binding. Status List and Controlled Identifiers are candidates for the authority layer, not the self-contained Lumion.
• EAT (Entity Attestation Token) -- an issuer, holder, and verifier appraisal model. A candidate shape for the authority layer's interaction, not for the self-contained Lumion.

Anonymity and credential systems:

• Nym mixnet and zk-nym anonymous credentials -- metadata-hiding transport and anonymous "right to act" credentials. The mixnet is orthogonal to a Lumion: a Lumion is traceable by name by design. A generic zk-nym is a possible authority-layer mechanism for access control and key issuance, but is chain-anchored and research-stage.