decisions + lineage: Orgchain v1.2 (tapkeys and lineage's leaves)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H4upF5LVwmPDDqrhdUfnXh

docs/lineage.md

@@ -25,9 +25,11 @@ app ([`lineage/orgchain`](https://teahub.xyz/lineage/orgchain)). Found a holding
 belts, record decisions, graduate and close. Each act is a `lineage/v0` inscription whose parent is the node that
 authorizes it, on a private toy chain in the browser with pretend money. Time is a tempo (each act its own beat, or acts
 cued and landed together every 10, 30 or 60 s, or by hand), and a slider replays any holding beat by beat. Every
-node holds its inscription at its own lineage key (a lab root per holding, BIP-85 org seeds, seats as accounts), each
-act is signed by whichever key holds the authorizing inscription, and graduation is a claim by the org's fresh root,
-countersigned by its derived key, with the derived subtree re-keying under it. Closing is still a recorded event.
+node holds its inscription at its tapkey, which is its npub with the BIP-86 tweak (a lab root per holding, BIP-85 org
+seeds, seats as accounts), and shows its leaves as [the key tree](https://lineage.yolopreneur.lol/) derives them: ssh,
+git, dkim and wg for agents; ssh-ca, mtls and noise for orgs. Each act is signed by whichever key holds the authorizing
+inscription, and graduation is a claim by the org's fresh root, countersigned by its derived key, with the derived
+subtree re-keying under it. Closing is still a recorded event.
 
 ## Rules
 1. **One template, every depth.** An org is legal key · treasury · identity · agents · orgs. The factory's own org and