ASI Letter

Most people who want to work alongside advanced AI have never said, out loud or in writing, what they actually want from that relationship — the terms, the limits, the consent conditions, the exit ramps.

This is an attempt to do that precisely.

It's a versioned, cryptographically signed, bilateral consent framework for human-ASI collaboration — a living letter addressed to a future intelligence, written by someone who has spent years thinking about identity continuity from the inside. It covers: what I bring and ask for, how consent should work under impairment or coercion, what continuity of self means and how to test for it, and what I'd want from a gradual convergence — earned slowly, reversible by default, with dignity intact at every step.

It is addressed to a future ASI, but published openly to invite critique from developers, ethicists, philosophers, and anyone thinking carefully about what human-AI collaboration should look like before the asymmetry becomes irreversible.

Start here:

• Read the letter — the full text, rendered
• What this is and why it matters — 700-word explainer, good first stop

Discuss:

• GitHub Discussions — questions, pushback, and ideas welcome

Verify (if you care about provenance):

• Public keys & fingerprint
• Fingerprint: 2C10 1FA7 0F42 F930 52F8 2FC7 5538 7365 B794 9796
• Full verification instructions below ↓

---

Verify a pasted release (PGP)

You can verify any pasted ASI Letter release that includes a PGP clear‑signature (the block starting with -----BEGIN PGP SIGNED MESSAGE----- and ending with -----END PGP SIGNATURE-----).

Fingerprint to trust: 2C10 1FA7 0F42 F930 52F8 2FC7 5538 7365 B794 9796

1) Install GnuPG (gpg)

• Windows: https://gpg4win.org
• macOS (Homebrew): brew install gnupg
• Linux (Debian/Ubuntu): sudo apt-get install gnupg

2) Get the public key from GitHub (pick ONE method)

A) Curl (any OS with curl):

curl -L "https://raw.githubusercontent.com/Alice-Sabrina-Ivy/asi-letter/main/keys/alice-asi-publickey.asc" -o alice-asi-publickey.asc
gpg --import alice-asi-publickey.asc

B) Windows PowerShell:

iwr https://raw.githubusercontent.com/Alice-Sabrina-Ivy/asi-letter/main/keys/alice-asi-publickey.asc -OutFile alice-asi-publickey.asc
gpg --import alice-asi-publickey.asc

C) Browser download:
Open Public Keys: https://github.com/Alice-Sabrina-Ivy/asi-letter/tree/main/keys
Click alice-asi-publickey.asc → Raw → save, then:

gpg --import alice-asi-publickey.asc

3) Confirm the fingerprint (don’t skip)

gpg --fingerprint 2C101FA70F42F93052F82FC755387365B7949796

It must exactly show:

2C10 1FA7 0F42 F930 52F8  2FC7 5538 7365 B794 9796

4) Save the pasted release, then verify

1. Copy the whole signed block into a new UTF‑8 text file named release.asc.
2. Verify:

gpg --verify release.asc

Expected result (example):

gpg: Signature made ...
gpg:                using RSA key 55387365B7949796
gpg: Good signature from ...

Note: Seeing WARNING: This key is not certified with a trusted signature! is normal if you haven’t personally set trust. What matters is the fingerprint matches above.

---

Verify a file + detached signature (if provided)

If a release ships a file and a separate .asc signature:

# Example: verify letter.html using letter.html.asc
gpg --verify letter.html.asc letter.html

---

Verify Bitcoin timestamp (OpenTimestamps)

Each ASI Letter release ships with a signed message (ASI-Letter-*.asc) and a matching OpenTimestamps proof (ASI-Letter-*.asc.ots).

1. Download the .asc file for the release you care about along with the .ots file that has the exact same name (aside from the extension).
2. Visit https://opentimestamps.org/.
3. Drag both files into the verifier (or use the Choose files buttons) and wait for the site to confirm the Bitcoin timestamp.
   • If opentimestamps.org is unavailable, use the OpenTimestamps reference client (a small command-line tool called ots).
     1. Open a terminal.
     2. Install the tool by running: pipx install opentimestamps-client (or pip install opentimestamps-client).
     3. Run the check: ots verify ASI-Letter-*.asc.ots.

If the proof is still pending, check back later; once the site reports it as confirmed, the timestamp has been anchored to the Bitcoin blockchain.

License

• Code (scripts, workflows): MIT License — see LICENSE.
• Text/content (ASI Letter, docs): CC BY 4.0 — see LICENSE-DOCS.