teahubxyzandClaude Opus 5.5
744c5946aa
Folds in the tree branch's key layer (2ea7884): lineage-keys.js and
handoff.js come over as written, with their spec vectors; the off-chain
keyring and the old UI stay behind, because v1's tree comes from the chain.
- Each holding gets its own 24-word lab root. Every node has lineage's
keys at its place in the tree: BIP-85 org seeds, agents as accounts
1..n of their org's seed, BIP-86 wallets and NIP-06 npubs.
- Every act is signed by whichever key holds the authorizing inscription;
a birth hands the child its own; the lab wallet is the faucet.
- Graduation is a claim by the org's fresh root, countersigned by its
derived key, and the derived subtree re-keys under the new root, so the
parent's line can no longer sign for it. Adopted descendants keep theirs.
- Inspect shows each node's key path, npub, address and current holder,
and which key signed each event; the act panel names the signing key.
- Labs saved before keys still load; their holdings sign with the lab
wallet.
- 49 unit tests (6 new), Playwright 6/6 with key checks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H4upF5LVwmPDDqrhdUfnXh
4.0 KiB
Orgchain
Lineage's app for creating and operating lineage holdings: https://lineage.yolopreneur.lol/orgchain/
Lineage gives an org its structure, a key tree with a place for every org and agent. Orgchain adds time. Every act is an inscription on a private toy chain in your browser, and its parent inscription is the node that authorizes it, so the chain itself records who did what, and when.
- Found a holding (a root: the LLC). Birth orgs and agents under any org. Award a belt (one skill, one seat). Decide (a decision on a node's record). Graduate an org (its edge flips from derived to adopted). Close a node (derived children close with it; graduated ones hold their own roots and stay open).
- Time. A beat is a block. At the default tempo each act is its own beat; at 10, 30 or 60 seconds, acts are cued and land together on the next beat; on manual they wait for Beat now. The slider and Replay show a holding as it stood at any beat.
- One interpretation.
src/orgchain/lineage.jsfoldslineage/v0events into trees, and vets every act before anything is signed. Events it rejects stay on the chain and show as rejected; they just don't change the tree. - Keys. Each holding gets its own 24-word lab root, and every node has lineage's keys at its place in the tree
(
src/orgchain/keys.js): an org's seed is BIP-85 from its parent's, or its own root once it graduates; agents are accounts 1..n of their org's seed; each key is BIP-86 (the wallet that holds the node's inscription and signs for it) and NIP-06 (its npub). Every act is signed by whichever key holds the authorizing inscription, and a birth hands the child its own. Graduation is a claim by the org's fresh root, countersigned by its derived key, and the derived subtree re-keys under the new root, so the parent's line can no longer sign for it.
Test coins and test keys only: a local chain, the lab wallet (the faucet that funds every key) and each holding's lab
root, kept in this browser (localStorage, key orgchain:lab:v1). Nothing here is a real key; minting a real root is
the operator's call.
Events
lineage/v0 is the ord metaprotocol (tag 7); the fields are CBOR metadata (tag 5); the body is a short text label.
| op | parent inscription (spent to authorize) | metadata |
|---|---|---|
found |
none | name |
birth |
the parent | name, kind (org or agent) |
award |
the issuing org or holding | to, skill, belt (white, green, black) |
decide |
the deciding node | title, why |
graduate |
the child's parent (then the handoff to the child's fresh root) | of |
close |
the node itself | none |
Names are domain labels (lowercase letters, digits, hyphens). Org and agent indices count separately and are never reused.
Build and test
npm ci
npm test # engine, reducer and lab (node --test)
npm run build # dist/ is the site; relative paths, so it works at any sub-path
npm run test:e2e # Playwright on vite preview; PW_CHANNEL=chrome uses installed Chrome
ORGCHAIN_URL (plus PW_ARGS, a JSON array of browser flags) points the same end-to-end spec at a deployed copy.
Deploy: copy dist/ to ventures/lineage/orgchain/ on teahubxyz/time gh-pages. Its headers (a strict CSP with
connect-src 'none': the app makes no network requests) come from ventures/lineage/_headers.
Built on Super Testnet
The chain, wallet, inscriptions, metadata and index (src/adapters, src/upstream, with src/storage.js and
src/miner.js) are Super Testnet's, unchanged and with their tests
(tests/adapters.test.js). See PROVENANCE.md and public/licenses/. Lineage's key derivation and the claim and
countersign handoff (src/adapters/lineage-keys.js, src/adapters/handoff.js, with their spec vectors in
tests/keys.test.js) come from the tree branch. The full lab (explorer, delegates, recursion and
the Inscriboor extension) lives at supertestnet.lol.