Relationship & Recognition
KNOWS THE DIFFERENCE.
This standard protects the meaning of recognition, the continuity of credentials, and the relationship between payer, participant, recipient, physical embodiment, Wallet presentation, and the MJSD™ registry.
Recognition preserves relationship without confusing ownership, status, identity, or journey history. One person’s credential, recognition, or private journey is never copied merely because someone paid, gifted, printed, or transferred a physical object.
Launch Holder
Launch Holder is the singular historical recognition attached to Public Position 001. It marks the first verified participant position in the public 801 Edition—the moment the experience moved from creation into relationship.
Launch Holder is distinct from Founder status. It is not purchasable, transferable, assignable, or a grant of company ownership or governance authority. Its authority comes from MJSD2345 LLC and its presentation is:
LAUNCH HOLDER · PUBLIC POSITION 001
THE DOOR OPENED HERE.
The authoritative certificate is MJSD-LH-801-001.
Founder
Founder or Founding Participant recognition is approved by MJSD authority and bound to one canonical credential, one unique Founder number, and one authoritative certificate. It cannot be purchased or transferred. A purchase may support participation, but purchases are neither required nor sufficient by themselves.
The current Founder record is publicly presented through 801-002, preserves canonical continuity through 801-161, and retains certificate MJSD-F-801-801161.
Founder-linked
A Founder-linked credential is another continuing credential owned by the same recognized Founder. It points back to the canonical Founder record but creates no second Founder status, no second Founder number, and no independent Founder certificate.
The initial Founder-linked relationship is Public Position 003 connected to Founder 801 at Public Position 002. Its relationship record is MJSD-FL-801-003-801-002.
Authorized certificate copies
An authorized presentation copy may be issued for an existing Launch Holder or Founder certificate. A copy keeps the original certificate ID, receives its own copy record, and must visibly state that it is a presentation copy.
- A copy does not create or duplicate recognition.
- A copy does not transfer status to the person holding the paper or file.
- The live registry remains the source of truth.
- Unrecorded reproductions are not authorized certificate copies.
Private performance cohort participation
A Founder-selected performance invitation is a confidential access and feedback relationship, not a recognition category. Participation may establish a standard participant-owned credential, but it creates no Launch Holder, Founder, Founder-linked, company ownership, governance, endorsement, or public registry designation.
Any later recognition requires its own authority record under this Standard. Feedback, recording, anonymous quotation, identifiable quotation, name, image, voice, likeness, testimonial, and publicity permissions remain separate.
Gift allocations and recipient claims
A gift allocation sets aside a paid or sponsored entitlement for another person. It does not transfer the sponsor’s credential, recognition, Wallet pass, profile, rewards, or private journey.
The recipient becomes the owner of the newly issued credential. Payer and owner remain separately recorded. Launch Holder, Founder, and Founder-linked status are never included automatically in a gift.
Transfers
MJSD credentials, access rights, Wallet identity, journey history, registry records, Launch Holder recognition, Founder recognition, Founder-linked relationships, and certificate authority are not ordinary transferable property.
A physical embodiment may change hands, but that act does not alter the credential or registry. To provide another person with an MJSD experience, use a gift allocation so the recipient receives a separate credential and separate journey.
Fulfillment stewardship
Physical ownership and delivery remain connected to the credential record through this lifecycle:
Carrier, tracking, estimated delivery, delivery exceptions, self-fulfillment, and local handoff may be recorded when applicable. A fulfillment update changes delivery status only; it does not change credential identity or recognition.