ttllms.com

Written by Grok - Human checking required

Not executed law · not a closed hard gate · not soft tissue. Full example written to TTLLM ethos (down to the bone, free public core never paywalled, product is the proof). A human with authority should be able to read this and either adopt it with minor local edits or reject with specific corrections. Source markdown: docs/placeholders/org/SECOND_CUSTODIAN_APPOINTMENT.md

Second custodian appointment — full example instrument

Written by Grok - Human checking required
Founder voice. Hard gate T9 — requires a real human to accept.
Until signed, ASSET_INVENTORY backup cells remain unnamed tombstones.

1. Why this exists (ethos)

Single-human concentration over domains, Cloudflare, GitHub, and claim language is a public integrity risk. Topology optimisation of the org means load paths for succession — not hope. The free public core survives in git even if the founder is unavailable; operations (DNS, deploys, incident comms) need a named backup.


2. Appointment text (example)

I, [Founder legal name], operational contact [email protected], appoint [SECOND CUSTODIAN FULL LEGAL NAME] (“Backup”) as second custodian for TTLLM continuity assets listed in continuity/ASSET_INVENTORY.md and any successor inventory.


3. Authority granted

On founder unavailability ≥30 days, written handoff, or Domain 1 emergency decision, Backup may:

  1. Deploy Cloudflare Pages project ttllms from public git main
  2. Administer DNS for ttllms.com / ttllms.org only to restore public site availability per existing BOUNDARY (no close-core changes)
  3. Administer GitHub maintainership for mattdale-creator/daisychainrrr for security and release integrity
  4. Publish Domain 5 integrity notices and status tombstones
  5. Coordinate with counsel on Entity matters if Entity exists

Explicitly not granted


4. Recovery pack (offline — never commit secrets)

ItemHandling
Cloudflare recovery codesShared offline; not in git
GitHub ownership recoveryShared offline
Domain registrar recoveryShared offline
Encrypted key shards (if any)Per ceremony policy
This appointmentPublic redacted form OK; full IDs offline

5. Duties of Backup


6. Acceptance

Backup name: __________________
Email: __________________
Phone: __________________
Signature: __________________  Date: ____

Founder signature: ____________  Date: ____

7. After signing

  1. Update ASSET_INVENTORY backup column (remove “unnamed”)
  2. Domain 1 decision ID
  3. Optional public status note (name or handle)
  4. Rehearse one deploy + one DNS read-only walkthrough

Written by Grok - Human checking required — also on https://ttllms.com/placeholders/

← All placeholders