Module front_door 

Front-door record — how a domain is discovered as an agent (QDP: draft-webcivics-QDP).

Two forms, per the plan (§0.5) — DNS is the primary, no-hosting anchor:

• DNS TXT at _qdp.<domain> (QDP §3.6): the Front Door DID (a contextually-isolated, per-domain DID) + compact peering material. A domain owner adds one record at their registrar/Cloudflare — no server needed. This is the minimum viable front-door.
• /.well-known/QDP profile (QDP §3.1): the rich agent profile in Turtle + JSON-LD + CBOR-LD (Solid-compatible) — the optional enhancement for those who have hosting (web server / Cloudflare Worker+R2 / Solid POD). The DNS record may point to it (qdp:profile).

Private keys are NEVER placed in either form (QDP §5). CBOR-LD term-dictionary compaction (the q42 vocab) is deferred — to_cbor_ld is CBOR of the JSON-LD document (linked data in CBOR), which is lossless.

Structs

FrontDoorRecord

The front-door record for a domain acting as a QDP agent.

QdpService

A service a domain-agent exposes (QDP §3.4): eCash address, Solid POD, SPARQL endpoint, …

Functions

dns_record_name

The DNS record name the front-door TXT lives at (QDP §3.6).