teahubxyzandClaude Opus 5.5
4ad75f0970
A new lineage/v0 op, charter, records a node's legal form: sole proprietor, LLC, series LLC, series or corporation, with a jurisdiction (ISO 3166), a legal name, who formed it and a SHA-256 of the filings. Legal form is an attribute, so a node keeps its inscription, keys and history whatever form it takes, and the newest charter counts. A node charters itself; a series is chartered by its master, an ancestor chartered as a series LLC. Whether a charter stands is derived from the tree, never stored: a series lapses if it graduates or its master closes or stops holding series, so charters commute with graduations and closes in any block order. Agents can graduate: a seat goes independent as a holding of its own, with its own root and keys and its money along, and can then birth, award and incorporate. Charter is the tenth verb, and the tree tags each node with its form. Charter hashes a filing from a file in the tab. The sample charters yolopreneur as a Wyoming series LLC with its ventures as series, and lineage graduates into Lineage LLC. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H4upF5LVwmPDDqrhdUfnXh
3.7 KiB
3.7 KiB
AGENTS.md
Orgchain is lineage's app for creating and operating lineage holdings on Super Testnet's toy chain.
- Test-only, always: no mainnet funds, no hidden signing, no custody, and nothing presented as a real key.
- Lineage semantics live in one place,
src/orgchain/lineage.js, andSPEC.mdsays the same in words. The UI never interprets events itself, and every act is vetted by that reducer before it is signed. A new op or rule means a reducer change, its tests, the README's table andSPEC.md. - Whatever signs must stay valid on real Bitcoin. After changing how transactions or envelopes are built, rerun the
regtest rehearsal and its comparison (
tools/regtest/README.md) and refresh the fixture it records. - The engine (
src/adapters,src/upstream,src/storage.js,src/miner.js) is Super Testnet's. Compose with it rather than rewriting it, and keep its tests passing. Preserve upstream licenses and provenance. Its local changes are P2WPKH payments, a coinbase split across up to 64 outputs, ordinary spends of up to eight inputs and outputs whose key-path signatures may carry 0x83, coins imported from a real chain, and BIP-341/342 checks of reveals' script paths, all insrc/adapters/chain.js(PROVENANCE.md); keep them small and tested. - Money lives in
src/orgchain/money.js: beats pay the holdings (split by hashrate, or all to the last act; under Mainnet none mine, and the lab wallet funds them), sends spend SegWit coins only, so an inscription can never leave as change, and balances are read off the chain, never stored. Gas (src/orgchain/actions.js): every act is paid by the actor's own keys and checked before anything is signed; the lab wallet pays only for foundings and for holdings that predate lab keys. - Deals live in
src/orgchain/offers.js: the buyer pre-signs the whole transaction and the holder countersigns. An offer is signatures kept in the lab, never chain state, and who holds an item is read off the chain, never from metadata. Inscription metadata is public and permanent, so never put a secret in it (item notes included), and a charter carries a hash of the filings, never the filings. - Charters (
src/orgchain/lineage.js): legal form is an attribute of a node, and whether a charter stands is derived from the tree (standing), never stored, so charters commute with graduations and closes. - Keys follow the tree (
src/orgchain/keys.js): store roots only (one per holding, one per graduated org) and derive every other key from its position. Every act is signed by whichever key holds the authorizing inscription. - A node's chain key is its account's BIP-86 Taproot key (
m/86'/1'/account'/0/0); SegWit is BIP-84 at the same account and holds its money; its Ethereum key is BIP-44 atm/44'/60'/account'/0/0(an org's, at account 0, is the key tree page's legal-control key, andtests/keyring.test.jspins that page's vector). Leaves are HKDF-SHA256 (saltlineage/v0) and must stay byte for byte with lineage's key tree page;tests/keys.test.jsholds values read off that page. - Keyrings (
src/orgchain/keyring.js): every key signs the statement with its own chain's message standard (BIP-322, EIP-191, a NIP-01 event), so real wallets can make and check the proofs. Keep those formats exact and their pinned vectors passing; a new chain's key joins only with its own standard and a vector to pin. - Secrets show only behind Reveal, reset on every selection, and match the key tree page byte for byte (the tests pin hashes of the page's own output).
- The page makes no network requests; keep it that way (the deployed CSP sets
connect-src 'none'). - Before shipping:
npm test,npm run build,npm run test:e2e.