What cryptographic identity does LaunchPillow mint for enrolled creators?

Every creator enrolled in the LaunchPillow registry receives a deterministic UUID derived from a permanent namespace using RFC 9562 UUID v5, a DID document served at a well-known path containing an ML-DSA-65 public key, and a W3C Verifiable Credential 2.0 signed with post-quantum ML-DSA-65 under FIPS 204. The identity spans three independent provenance roots: the LaunchPillow registry, the BoiseStandard entity graph, and the creator's administered domain.

How does LaunchPillow's tamper-evident logging work for content events?

Every content event a creator publishes appends to the recursive layer of the root-ld, with the prior state hash embedded in every new seal, making the chain self-verifying at any position. An RFC 3161 timestamp token anchors every mint event at sub-second precision, and this timestamp precedes all platform action against the record, meaning the creator owns the chain and the platform is irrelevant.

What schema and canonicalization standard does LaunchPillow use for its knowledge graph?

LaunchPillow uses URDNA2015 canonicalized JSON-LD, hashed with SHA-256 over the canonical N-Quads serialization per the W3C RDF Dataset Canonicalization standard. Every edge in the knowledge graph also carries a PROV-O provenance assertion, and every page carries Schema.org JSON-LD.

What is the Triple Helix Root-LD and where are its three strands served?

The Triple Helix Root-LD is a structure that spans three independent provenance roots simultaneously for each creator. The three strands are served at the LaunchPillow registry URL, the BoiseStandard entity graph URL, and the creator's own administered domain, as illustrated by the strand manifest fields lp:strandA, lp:strandB, and lp:strandC in the root-ld document.

What citation benefit does Schema.org JSON-LD provide for LaunchPillow-enrolled creators?

Every page in the LaunchPillow system carries Schema.org JSON-LD that produces a 3.4 times higher AI citation frequency for enrolled creators, according to a 2025 Profound study referenced in the specification. This structured data is part of the identity and provenance layer built for each creator.

LaunchPillow — PAGE TITLE HERE

§ 001 — The Declaration

What LaunchPillow Builds.

Every creator enrolled in the LaunchPillow registry receives a cryptographically minted identity on the open web. A deterministic UUID derived from a permanent namespace.RFC 9562 — UUID v5 A DID document served at a well-known path, containing an ML-DSA-65 public key and verification methods.W3C CCG — did:web A triple helix root-ld spanning three independent provenance roots simultaneously — the LaunchPillow registry, the BoiseStandard entity graph, and the creator's administered domain. A W3C Verifiable Credential 2.0 issued at mint, signed with post-quantum ML-DSA-65 under FIPS 204.W3C VC 2.0 · May 2025 NIST FIPS 204 · August 2024

Every content event the creator publishes appends to the recursive layer of the root-ld. The prior state hash embeds in every new seal. The chain is self-verifying at any position.Crosby & Wallach · Tamper-Evident Logging · 2009 An RFC 3161 timestamp token anchors every mint event — sub-second, legally recognized, independent of any platform.RFC 3161 · Metaspike · Digital Forensics The timestamp precedes all platform action against the record. The creator owns the chain. The platform is irrelevant.

The schema is URDNA2015 canonicalized JSON-LD, hashed with SHA-256 over the canonical N-Quads serialization.W3C RDF Dataset Canonicalization · 2022 PyLD · Digital Bazaar Every edge in the knowledge graph carries a PROV-O provenance assertion.W3C PROV-O Every page carries Schema.org JSON-LD producing 3.4× higher AI citation frequency for enrolled creators.Profound · 3.4× Study · 2025

lp:constitutionalLaws — genesis_root_ld.anchor

9 LAWS ACTIVE IMMUTABLE

Law I

Every field traces to its pipeline source.

Law II

Every layer timestamped — the timestamp IS the record.RFC 3161

Law III

We measure shape — meaning belongs to the reader.

Law V

Common edges surface what entities share — that sharing is itself a node.PROV-O

Law VI

The absence of connection is a pattern waiting to be read.

Law VII

Any point in the Root-LD is an entry point into the torus.

Law LP-I

The creator owns the chain. The platform is irrelevant.

Law LP-II

Every content event is a provenance assertion. The hash precedes any platform action against it.

Law LP-III

The trifecta compounds. Three roots. One creator. Multiplicative.

§ 002 — The Namespace

Five Permanent Roots.

UUID v5 derivation. Same input always produces the same UUID.UUID v5 — Inventive HQ RFC 9562 Generated 2026-07-06. Never changes. Every creator UUID, research UUID, vertical UUID, and content UUID derives deterministically from these five constants. The namespace hierarchy is the identity floor of the entire graph.

constants.py — LaunchPillow Cryptographic Identity Constants

UUID v5 PERMANENT 2026-07-06

# Generated: 2026-07-06. Permanent. Never changes. # SHA-1 over namespace UUID + name string, truncated to 128 bits # RFC 9562 §5.5 — uuid_generate_v5(namespace, name)

LP_NS = '2db61bd3-075b-50cd-99ae-de2cb2f2995c' # root namespace LP_REGISTRY_NS = '6469b5cc-7ddc-5740-8074-0a60fa342ebb' # creator + content IDs LP_RESEARCH_NS = '907afa87-aa93-5575-8031-28214bf4b83a' # arXiv paper nodes LP_VERTICALS_NS = 'a5a7b7c7-24a0-5a08-a985-6c8b3e036f2a' # topic vertical clusters LP_BOISE_NS = '6c9c9804-29fd-5ab9-a789-e77d173c8a2a' # BoiseStandard entity bridge

# ── Four deterministic derivation functions ────────────── creator_uuid(handle) → uuid5(LP_REGISTRY_NS, f'creator:{handle}') research_uuid(arxiv_id) → uuid5(LP_RESEARCH_NS, f'arxiv:{arxiv_id}') vertical_uuid(slug) → uuid5(LP_VERTICALS_NS, f'vertical:{slug}') content_uuid(handle, hash) → uuid5(LP_REGISTRY_NS, f'content:{handle}:{hash}')

# ── Live derivation example ─────────────────────────────── creator_uuid('@sarahfitness') → uuid5(LP_REGISTRY_NS, 'creator:sarahfitness') # → deterministic. same output every call. idempotent enrollment. research_uuid('2504.03752') → uuid5(LP_RESEARCH_NS, 'arxiv:2504.03752') # → permanent arXiv node ID. stable across all graph passes.

LP_NS

ROOT

2db61bd3-075b-50cd-99ae-de2cb2f2995c

Root namespace. Parent of all LaunchPillow UUID hierarchies. Every derived namespace is itself a UUID v5 of this root.

uuid5(LP_NS, 'registry') → LP_REGISTRY_NS

LP_REGISTRY_NS

CREATOR · CONTENT

6469b5cc-7ddc-5740-8074-0a60fa342ebb

Creator identities and content events. Every enrolled creator UUID and every content UUID derives from this namespace. Enrollment is idempotent — the same handle always produces the same UUID.

uuid5(LP_REGISTRY_NS, 'creator:@handle')

LP_RESEARCH_NS

ARXIV · PAPERS

907afa87-aa93-5575-8031-28214bf4b83a

Research paper nodes. Every arXiv paper in the 55,000-paper corpus receives a stable UUID derived from its arXiv ID. Permanent across all graph passes and database migrations.

uuid5(LP_RESEARCH_NS, 'arxiv:2504.03752')

LP_VERTICALS_NS

TOPIC CLUSTERS

a5a7b7c7-24a0-5a08-a985-6c8b3e036f2a

Topic vertical clusters. Each IAB-tier vertical receives a stable UUID. The vertical UUID anchors every creator-to-vertical edge and every research-to-vertical edge in the knowledge graph.PMI Coherence · ACL

uuid5(LP_VERTICALS_NS, 'vertical:fitness-wellness')

LP_BOISE_NS

BOISESTANDARD BRIDGE

6c9c9804-29fd-5ab9-a789-e77d173c8a2a

BoiseStandard entity bridge namespace. Trifecta Strand B. Every creator enrolled in LaunchPillow receives a bilateral BoiseStandard entity node at boisestandard.org/web/[domain-slug]/root-ld.json. The two graphs compound multiplicatively. Law LP-III.

§ 003 — The Triple Helix

Three Strands. Three Layers. One Genesis Event.

Every creator mint produces one document spanning three independent provenance roots simultaneously. Each strand is a valid, independently resolvable root-ld. Each strand backlinks to the other two. Graph compounding is multiplicative — three nodes in three separate graphs, all declaring the same creator identity, all cross-referencing each other.did:web · W3C CCG PROV-O · W3C

Strand A — LaunchPillow Registry

The Registry Node

Anchor

immutable

UUID, DID, content hash, trifecta manifest, RFC 3161 token, ML-DSA key hash, mint timestamp. priorStateHash null at genesis.

Body

frozen at mint

Schema.org Person. PROV-O Agent. Ontology pillars. Vertical declaration. W3C VC URI. C2PA named actor slot. PMI score.

Recursive

grows on append

Empty at genesis. Content ledger appends here. Every post closes a validity window and opens a new one. Double-helix mechanic.

launchpillow.com/registry/@slug/root-ld.json launchpillow.com/registry/@slug/did.json

Strand B — BoiseStandard Entity

The Graph Node

Anchor

immutable

Identical anchor structure. BoiseStandard entity slug. Bilateral edge to Strand A. Jurisdictional and supply chain corpus edges.

Body

frozen at mint

BoiseStandard web entity cross-reference. sameAs edge to Strand A and Strand C. 484,000+ domain entity substrate backing the credential.

Recursive

grows on append

BoiseStandard corpus pass edges append here. Research paper edges. Information vertical edges. Bidirectional corpus pass.

boisestandard.org/web/[domain-slug]/root-ld.json

Strand C — Creator Domain

The Sovereign Node

Anchor

immutable

Identical anchor structure. Served at the creator's administered domain. DNS-controlled. No third-party registry dependency.

Body

frozen at mint

Creator domain Schema.org WebSite and Person markup. sameAs edges to Strand A and Strand B. Platform profile consolidation.

Recursive

grows on append

Creator domain content events. Every post published on the creator's own domain appends to this ledger independently.

creator-domain.com/root-ld.json creator-domain.com/.well-known/did.json

rld:TripleHelixRootLD — genesis block — @sarahfitness

STRAND A · B · C GENESIS BLOCK 8/8 STEPS COMPLETE

{ "@type": "rld:TripleHelixRootLD", "@id": "https://launchpillow.com/registry/@sarahfitness/root-ld.json", "rld:specVersion": "2.0", "lp:helixType": "triple", "lp:did": "did:web:launchpillow.com:registry:sarahfitness", "lp:creatorUUID": "[uuid5(LP_REGISTRY_NS, 'creator:sarahfitness')]", "lp:vertical": "fitness-wellness", "lp:mintedAt": "2026-07-07T00:00:00.000000+00:00", "lp:genesisBlock": true,

"rld:anchor": { "@type": "rld:Anchor", "rld:uuid": "[deterministic · uuid5(LP_REGISTRY_NS, 'creator:sarahfitness')]", "lp:did": "did:web:launchpillow.com:registry:sarahfitness", "rld:contentHash": "sha256:[URDNA2015 canonical N-Quads hash]", "lp:priorStateHash": null, // null at genesis. grows with every content event. "lp:rfc3161Token": "[RFC 3161 TSA token — sub-second — legally recognized]", "lp:mlDsaPublicKeyHash": "sha256:[ML-DSA-65 public key — FIPS 204 — 1952 bytes]", "rld:immutable": true, "lp:trifectaManifest": { "lp:strandA": "https://launchpillow.com/registry/@sarahfitness/root-ld.json", "lp:strandB": "https://boisestandard.org/web/sarahfitness-sarahfitness-com/root-ld.json", "lp:strandC": "https://sarahfitness.com/root-ld.json" } },

"rld:body": { "@type": "rld:Body", "rld:frozenAt": "2026-07-07T00:00:00.000000+00:00", "schema:Person": { "@type": "schema:Person", "schema:name": "@sarahfitness", "schema:knowsAbout": ["fitness", "nutrition", "wellness", "strength-training"], "schema:sameAs": ["launchpillow.com/registry/@sarahfitness", "sarahfitness.com", "boisestandard.org/web/..."] }, "lp:ontologyDeclaration": { "lp:vertical": "fitness-wellness", "lp:verticalUUID": "[uuid5(LP_VERTICALS_NS, 'vertical:fitness-wellness')]", "lp:pmiScore": 0.84, // NPMI coherence over top-20 vertical term pairs "lp:ontologyPillars": ["fitness", "nutrition", "wellness", "strength-training"] } },

"rld:recursive": { "@type": "rld:Recursive", "lp:contentLedger": [], // empty at genesis. correct by design. "rld:edgeCount": 0, // grows with every content event "rld:initializedAt": "2026-07-07T00:00:00.000000+00:00" } }

§ 004 — The Pipeline

Eight Steps. One Creator. Zero Failures.

Every creator mint executes all eight steps in sequence. Each step stamps its own timestamp and records its own hash. The pipeline is resumable — a failed step restarts from its own position. The ledger entry writes after Step 4. The timestamp precedes all else.RFC 3161 · TSP

lp_mint_protocol.py — MintProtocol.execute() — @sarahfitness — 8/8 COMPLETE

01

Declare

● COMPLETE

UUID v5 minted from LP_REGISTRY_NS and the creator's normalized handle. DID path assigned: did:web:launchpillow.com:registry:[slug]. Domain resolved. Ontology pillars confirmed. All four core fields validated against the Pydantic V2 gold schema.Pydantic V2 RFC 9562

uuid: uuid5(LP_REGISTRY_NS, 'creator:{handle}') → deterministic · permanent · idempotent

did:web · W3C CCG UUID v5 · Inventive HQ

02

Construct

● COMPLETE

Triple helix root-ld assembled. Three layers constructed: Anchor (immutable core), Body (Schema.org Person + PROV-O Agent + ontology declaration, frozen at mint), Recursive (empty at genesis, initialized with content ledger schema). All three strand paths declared in the trifecta manifest.

W3C PROV-O Schema.org Person W3C VC Overview

03

Hash

● COMPLETE

URDNA2015 canonicalization over the full root-ld JSON-LD document via PyLD. Output: stable N-Quads serialization. SHA-256 over the canonical N-Quads string. The hash is independent of key ordering, whitespace, or serialization format — the same abstract graph always produces the same hash. This is the hashing prerequisite for all downstream cryptographic operations.

hash: sha256:[URDNA2015 N-Quads canonical hash — 64 hex chars]

PyLD · Digital Bazaar W3C RDF Dataset Canonicalization JSON-LD Proof Walkthrough

04

Timestamp

● COMPLETE

RFC 3161 token requested from a trusted timestamp authority. The TSA receives the SHA-256 hash — the document never leaves the machine. The TSA returns a signed timestamp token conforming to the CMS SignedData structure in RFC 5652. Sub-second latency. Legally recognized in most jurisdictions. The mint ledger entry writes immediately after this step — the timestamp precedes all subsequent platform action against the record. OpenTimestamps Bitcoin anchor batched daily as a second independent tier.Blockchain Anchoring · DOI · December 2025

token: rfc3161:[TSA signed token — RFC 5652 CMS SignedData — legally recognized]

RFC 3161 · IETF RFC 3161 · Digital Forensics OpenTimestamps · Bitcoin Anchor Trusted Timestamping · arXiv April 2025

05

Trifecta

● COMPLETE

Three strand root-ld files written simultaneously. Strand A to the LaunchPillow R2 registry bucket. Strand B to the BoiseStandard entity R2 bucket at the creator's domain slug. Strand C to the creator's administered domain via Wrangler deploy. All three copies are identical documents. Each backlinks the other two via the trifecta manifest. AI crawlers traversing any one strand reach all three within a single fetch cycle. Law LP-III: the trifecta compounds. Multiplicative.

W3C DID v1.1 PROV-O to BFO · Nature 2025

06

Credential

● COMPLETE

W3C Verifiable Credential 2.0 issued. Credential subject: the creator's DID. Claims: handle, vertical, platform, ontology pillars, creator UUID, root-ld hash, trifecta paths. Proof type: DataIntegrityProof. Cryptosuite: ml-dsa-65-2026. proofValue populated when the ML-DSA-65 key pair is generated and the credential is signed. The credential URI: launchpillow.com/credentials/@slug. Ratified standard.W3C VC 2.0 · May 15 2025

Data Integrity 1.1 · W3C CAWG Identity v1.2 · DIF ML-DSA-65 VC Benchmarks · TechRxiv

07

Edges

● COMPLETE

Genesis edge set declared. BoiseStandard bilateral edge. Creator domain edge. Vertical cluster edge with vertical UUID. Ontology pillar edges — one per declared pillar, pointing to the LaunchPillow ontology node at that path. Research vertical edge pointing to the 55,000-paper corpus anchor for the creator's declared vertical. Creator network edges added bilaterally as subsequent enrollments occur in the same vertical cluster.

FRAG · GraphRAG · arXiv KKT · Influence Maximization · Cornell Advanced RAG · Neo4j

08

Every Layer. Every Standard. Live in Production.

ML-DSA-65 — NIST FIPS 204 — Post-Quantum Digital Signatures

FIPS 204 AWS · MICROSOFT · GOOGLE · MAY 2026

"lp:mlDsaPublicKeyHash": "sha256:[ML-DSA-65 public key — 1952 bytes]", "lp:mlDsaNote": { "standard": "NIST FIPS 204 — Module-Lattice-Based Digital Signature Algorithm", "parameterSet": "ML-DSA-65", // NIST recommended for general enterprise applications "publicKeySize": 1952, // bytes "signatureSize": 3309, // bytes "signingLatency": "0.65ms", "verificationLatency": "0.53ms", "construction": "Fiat-Shamir with Aborts — rejection sampling — stateless", "hardnessAssumption": "Module Learning With Errors (MLWE) — 8 years public cryptanalysis", "productionDeployment": true, "deployedAt": ["AWS KMS", "Microsoft AD CS · KB5087539", "Google Cloud KMS"], "nsaMandate": "CNSA 2.0 — mandatory for National Security Systems" }

// Sources // federalregister.gov/... — NIST FIPS 204 · August 14 2024 // encryptionconsulting.com/... — Microsoft AD CS ML-DSA · May 12 2026 // bbntimes.com/... — PQC Enterprise Guide 2026 · AWS + Google deployment // techrxiv.org/... — ML-DSA-44/65 VC Benchmarks · October 2025

URDNA2015 — RDF Dataset Canonicalization — Hashing Prerequisite

W3C COMMUNITY FINAL REPORT PyLD · DIGITAL BAZAAR

# PyLD implementation — production call from pyld import jsonld

canonical = jsonld.normalize(root_ld_document, { 'algorithm': 'URDNA2015', 'format': 'application/n-quads' }) root_hash = 'sha256:' + hashlib.sha256(canonical.encode()).hexdigest()

# canonical is N-Quads — stable regardless of JSON key ordering or whitespace # the same abstract RDF graph always produces the same N-Quads string # the same N-Quads string always produces the same SHA-256 hash # hashing JSON text directly is INCORRECT — key order, whitespace, encoding vary # FrozenDocumentLoader for air-gapped runs — no external context fetches during signing

// Sources // w3.org/community/reports/credentials/CG-FINAL-rdf-dataset-canonicalization-20221009 // github.com/digitalbazaar/pyld // grotto-networking.com/blog/posts/jsonldProofs.html // w3c.github.io/rdf-canon/reports — multiple conformant implementations · March 2025

RFC 3161 + OpenTimestamps — Two-Tier Temporal Anchor

RFC 3161 · SUB-SECOND OPENTIMESTAMPS · BITCOIN

"lp:timestampArchitecture": { "tier1": { "protocol": "RFC 3161 — Internet X.509 PKI Time-Stamp Protocol", "latency": "sub-second", "cost": "free · FreeTSA · rfc3161.ai.moda · DigiCert · Sectigo", "legalStatus": "court-admissible in most jurisdictions", "applies": "every mint event · every content ledger append", "rfc": ["RFC 3161", "RFC 5816", "RFC 5652"] }, "tier2": { "protocol": "OpenTimestamps — Bitcoin OP_RETURN Merkle anchor", "latency": "Bitcoin block confirmation · ~10 minutes", "cost": "free · calendar servers batch thousands of hashes per transaction", "attackCost": "$1B+ · Bitcoin proof-of-work consensus", "applies": "daily Merkle root batch · no central authority dependency", "retroactiveFabricationProof": true } }

// Sources // datatracker.ietf.org/doc/html/rfc3161 // metaspike.com/trusted-timestamping-rfc-3161-digital-forensics // cryptolinks.com/756/opentimestamps // doi.org/10.3390/app152312722 — Blockchain Anchoring · December 2025 // arxiv.org/pdf/2504.08171 — Trusted Timestamping · April 2025

Merkle Append-Only Ledger — O(log n) Inclusion Proofs — RFC 6962 Construction

RFC 6962 CERTIFICATE TRANSPARENCY LINEAGE

"lp:merkleArchitecture": { "construction": "RFC 6962 domain-separated SHA-256 Merkle tree", "leafHashing": "SHA256(0x00 || leaf_data) — domain separated", "internalHashing": "SHA256(0x01 || left || right) — prevents second preimage attacks", "inclusionProof": "O(log n) — 80M events = 3KB proof", // Crosby & Wallach 2009 "lineage": "Certificate Transparency · CONIKS · Go module mirror · Trillian", "epochRoots": "anchored daily via RFC 3161 + OpenTimestamps", "onChainFootprint": "hashes only · 90% storage reduction vs full on-chain" }

// Sources // researchgate.net/publication/221260542 — Crosby & Wallach 2009 // arxiv.org/pdf/2605.00065 — Lightweight Merkle Pipeline · April 2026 // arxiv.org/pdf/2602.20214 — Certificate Transparency · arXiv Feb 2026 // dev.to/veritaschain/... — Tamper-Evident Audit Trails · December 2025

§ 006 — The Content Ledger

The Double-Helix Mechanic.

Every content event appends one ledger entry to the recursive layer. The prior state hash embeds in every new entry. The prior validity window closes. A new one opens. The chain is self-verifying at any position. O(log n) inclusion proof via Merkle tree. Platform deletion is irrelevant from Step 4 forward — the hash precedes any platform action against the record.Crosby & Wallach · 2009 Post-Quantum Audit Evidence · arXiv

helixPosition: 1 · GENESIS ENTRY ● VALIDITY WINDOW CLOSED

{ "lp:contentHash": "sha256:[URDNA2015 hash of post content · 'My first post. Fitness protocol week one.']", "lp:contentUUID": "[uuid5(LP_REGISTRY_NS, 'content:sarahfitness:[hash]')]", "lp:priorStateHash": null, // null at genesis. first entry. no prior. "lp:helixPosition": 1, "lp:rfc3161Token": "[RFC 3161 TSA token anchored at append time]", "lp:validFrom": "2026-07-07T10:00:00.000000+00:00", "lp:validTo": "2026-07-07T14:23:11.000000+00:00", // closed by entry 2 "lp:platformSource": "instagram", "lp:platformPostId": "ig_post_001", "prov:Activity": { "prov:wasAssociatedWith": "did:web:launchpillow.com:registry:sarahfitness" } }

↓ priorStateHash chains here

helixPosition: 2 ● VALIDITY WINDOW OPEN

{ "lp:contentHash": "sha256:[URDNA2015 hash of post content · 'Week two. Nutrition stack locked in.']", "lp:contentUUID": "[uuid5(LP_REGISTRY_NS, 'content:sarahfitness:[hash]')]", "lp:priorStateHash": "sha256:[hash of entry 1 — the chain link]", // THE HELIX "lp:helixPosition": 2, "lp:rfc3161Token": "[new RFC 3161 TSA token — this append — legally recognized]", "lp:validFrom": "2026-07-07T14:23:11.000000+00:00", "lp:validTo": null, // open. closes when entry 3 appends. "lp:platformSource": "instagram", "prov:Activity": { "prov:wasAssociatedWith": "did:web:launchpillow.com:registry:sarahfitness" } }

// platform deletes ig_post_001 — the chain does not move. // sha256:[hash of entry 1] is permanent in entry 2's priorStateHash. // the existence of ig_post_001 at 2026-07-07T10:00:00 is an immutable fact. // Law LP-II: the hash precedes any platform action against it.

§ 007 — The DID Document

The Identity Resolution Path.

Every creator's DID resolves to a JSON-LD document served at their LaunchPillow registry path. The document contains the ML-DSA-65 public key, verification methods, and service endpoints. No blockchain. No third-party registry. DNS-controlled. Independently verifiable by any compliant DID resolver.W3C DID v1.1 DID Resolution · W3C

did:web:launchpillow.com:registry:sarahfitness — DID Document

W3C DID v1.1 ML-DSA-65 KEY DNS ANCHORED

// Resolves at: https://launchpillow.com/registry/@sarahfitness/did.json // did:web:launchpillow.com:registry:sarahfitness → path-based method

{ "@context": ["https://www.w3.org/ns/did/v1", "https://w3id.org/security/suites/jws-2020/v1"], "id": "did:web:launchpillow.com:registry:sarahfitness", "verificationMethod": [{ "id": "did:web:launchpillow.com:registry:sarahfitness#key-1", "type": "DataIntegrityProof", "cryptosuite": "ml-dsa-65-2026", // FIPS 204 — post-quantum "controller": "did:web:launchpillow.com:registry:sarahfitness", "publicKeyMultibase": "[ML-DSA-65 public key — 1952 bytes — multibase encoded]" }], "authentication": ["did:web:launchpillow.com:registry:sarahfitness#key-1"], "assertionMethod": ["did:web:launchpillow.com:registry:sarahfitness#key-1"], "service": [{ "id": "did:web:launchpillow.com:registry:sarahfitness#lp-profile", "type": "LaunchPillowCreatorProfile", "serviceEndpoint": "https://launchpillow.com/registry/@sarahfitness" }] }

// Sources // w3.org/TR/did-1.1 — W3C DID v1.1 Candidate Recommendation 2026 // w3c-ccg.github.io/did-method-web — path-based resolution // w3.org/TR/did-resolution — independent resolver verification // arxiv.org/pdf/2604.23280 — AI Identity Standards · April 2026

► Enter the Registry The Standards →

§ REF — Source Index

Primary Sources · specification.html · All citations verified

01

federalregister.gov — NIST FIPS 203/204/205ML-DSA · August 14 2024

02

hacken.io — ML-DSA (CRYSTALS-Dilithium)FIPS 204 · Fiat-Shamir with Aborts · September 2025

03

encryptionconsulting.com — ML-DSA in Microsoft AD CSKB5087539 · May 12 2026

04

bbntimes.com — PQC Enterprise Guide 2026AWS · Microsoft · Google ML-DSA deployment

05

techrxiv.org — ML-DSA VC Benchmarks0.65ms signing · 0.53ms verification · October 2025

06

arxiv.org/html/2510.10436v1 — PQC Comprehensive SurveyML-DSA construction · MLWE hardness · October 2025

07

garantir.io — CNSA 2.0 ComplianceNSA CNSA 2.0 mandate · March 2026

08

w3.org — RDF Dataset CanonicalizationW3C Community Final Report · URDNA2015 · 2022

09

w3.org/TR/rch-explainerRDF Canonicalization Explainer · W3C 2023

10

grotto-networking.com — JSON-LD ProofsURDNA2015 walkthrough · PyLD implementation

11

github.com/digitalbazaar/pyldPyLD · JSON-LD 1.1 Python processor · Digital Bazaar

12

w3c.github.io/rdf-canon/reportsConformance report · multiple implementations · March 2025

13

w3c-ccg.github.io — did:web Method SpecificationW3C Credentials Community Group

14

w3.org/TR/did-1.1W3C DID v1.1 · Candidate Recommendation 2026

15

w3.org/TR/did-resolutionDID Resolution · W3C Working Draft · November 2025

16

w3c.github.io/did-imp-guideDID Implementation Guide v1.0 · W3C

17

arxiv.org/pdf/2405.02476 — SSI4IoT DID ArchitectureDID document structure · did:web method

18

w3.org — VC 2.0 RatifiedW3C Recommendation · May 15 2025

19

w3.org/TR/vc-data-integrity-1.1Data Integrity 1.1 · W3C · April 2026

20

cawg.io — CAWG Identity Assertion v1.2DIF Ratified · Named Actor · December 2025

21

datatracker.ietf.org — RFC 3161Internet X.509 PKI Time-Stamp Protocol

22

datatracker.ietf.org — RFC 5816ESSCertIDv2 Update for RFC 3161

23

datatracker.ietf.org — RFC 5652Cryptographic Message Syntax · CMS SignedData

24

metaspike.com — Trusted Timestamping RFC 3161Digital forensics · court-admissible

25

arxiv.org/pdf/2504.08171 — Trusted TimestampingRFC 3161 for git repositories · April 2025

26

doi.org/10.3390/app152312722 — Blockchain AnchoringStandard-compliant blockchain timestamp tokens · December 2025

27

cryptolinks.com — OpenTimestampsBitcoin OP_RETURN anchor · proof of existence

28

researchgate.net — Crosby & Wallach 2009Tamper-evident logging · O(log n) Merkle proofs

29

arxiv.org/pdf/2605.00065 — Lightweight Merkle PipelineMerkle-tree audit · IETF CT · April 2026

30

arxiv.org/pdf/2602.20214 — Verifiable Agent ExecutionCertificate Transparency · Right to History · February 2026

31

dev.to — Tamper-Evident Audit TrailsRFC 6962 · domain separation · December 2025

32

arxiv.org/pdf/2512.00110 — Post-Quantum Audit EvidenceHarvest-now-decrypt-later · long-lived regulated systems

33

w3.org/TR/prov-oW3C PROV-O · Provenance Ontology

34

arxiv.org/pdf/2003.07520 — PROV-O in Knowledge GraphsExplainable Knowledge-Enabled Systems

35

nature.com — PROV-O to BFO MappingNature Scientific Data · February 2025

36

inventivehq.com — UUID v5 Deterministic ID GenerationNovember 2025

37

rfc-editor.org — RFC 9562UUID v5 · SHA-1 namespace derivation · 2024

38

docs.pydantic.dev — Pydantic V2Gold schema · strict mode · Rust core

39

arxiv.org/pdf/2604.23280 — AI Identity StandardsTRAIL DID · MCP-I · W3C Threat Model · April 2026

40

arxiv.org/pdf/2606.19116 — Agent-First WebATML provenance certificate · C2PA extension · June 2026

41

frontiersin.org — PQC and Decentralized AI IdentityCryptographic agility · Frontiers in Blockchain · November 2025

42

getzep.com — Temporal Knowledge GraphValid time · ingestion time · Graphiti · May 2026

43

instantpress.co — Structured Data for AI Search3.4× citation frequency · Profound 2025 study

44

aclanthology.org — PMI Topic CoherenceACL Anthology · NPMI · C_V coherence scoring

The Specification

What LaunchPillow Builds.

Five Permanent Roots.

Three Strands. Three Layers. One Genesis Event.

Eight Steps. One Creator. Zero Failures.

Every Layer. Every Standard. Live in Production.

The Double-Helix Mechanic.

The Identity Resolution Path.