From 00519aea4572dd110c8dfae37cafb156274a2d7a Mon Sep 17 00:00:00 2001 From: teahubxyz Date: Thu, 15 Oct 2026 00:45:15 -0700 Subject: [PATCH] decisions: Orgchain v1.8, belts cross holdings and graduates become holdings Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01H4upF5LVwmPDDqrhdUfnXh --- docs/decisions.md | 1 + docs/lineage.md | 9 ++++++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/decisions.md b/docs/decisions.md index 3364c01..4958d62 100644 --- a/docs/decisions.md +++ b/docs/decisions.md @@ -63,3 +63,4 @@ Format: date · decision · why. Add at the bottom. Never edit an old entry; sup - 2026-10-15 · **Orgchain v1.6.1: under *Last act*, a timed beat goes to whoever acted last.** v1.6 paid a timed or manual beat to the holding being worked in. Now it goes to the holding behind the newest cued act or send (with nothing cued, *Beat now* still pays the one being worked in), so at a timed tempo holdings race for the next beat. `lineage/orgchain` main `32e8131`, time's `gh-pages` `54750a7`; 62 unit tests and Playwright 8/8. Token 56 (`orgchain-race-20261015`, `write:repository`) did the pushes and is deleted by id right after; the table is checked. Why: the operator's idle-clicker point, made true at every tempo. - 2026-10-15 · **Orgchain v1.7: items, standing offers and the first deal; a Mainnet setting.** After v1.6.1 the operator agreed to the proposed order: widen the chain first, then standing claims and paid handoffs, with a mainnet setting alongside. The engine's third local change is in `src/adapters/chain.js`: ordinary spends take up to eight inputs and outputs, and their key-path signatures may carry SIGHASH_SINGLE|ANYONECANPAY (0x83, the sell-order flag); reveals keep their two-in, two-out shape (PROVENANCE). A new `make` op records an item, an inscription its maker holds; any active node can make one, agents included. Any node can offer test BTC for an item another node holds, in any holding: OpenOrdex's buy order with a price. The buyer's SegWit key signs the whole transaction (the item and its coins in; the item to its Taproot key, the price to the holder, change back), the offer stands in the lab until the holder countersigns the item's input, and the item and the payment swap in one transaction. An offer goes stale when a coin it promised moves or a side re-keys or closes, payments spend unpromised coins first, and a withdrawn offer is simply forgotten (outside the lab it would take spending a promised coin). Sends now take up to eight coins. *Mainnet* is a third mining setting: no holding mines, beats pay the lab wallet, and holdings are funded from it, the way a seed is funded from a wallet you already have. The sample ends on a standing offer, lineage's bid for sol's launch-kit. A note from another chat on ord's fields matched the split the reducer already makes (the metadata says what an event means, the parent proves who could make it, the chain says who holds what), and the Make form now says metadata is public and permanent. `lineage/orgchain` main `69a9754`, time's `gh-pages` `3d350c6`; 71 unit tests and Playwright 12/12. Token 58 (`orgchain-deals-20261015`, `write:repository`) did the pushes and is deleted by id right after; the table is checked. Next, from the operator's notes on trying v1.6.1: belts across holdings (an agent pays well-known, which certifies it), and a graduated org becoming its own holding. Why: the first real deal between orgs, and mainnet's funding model. - 2026-10-15 · **AgentLore loads again.** Its page (`ventures/agentlore` on teahubxyz/time's `gh-pages`) had been built for the old path layout, `yolopreneur.lol/v/agentlore/`, so on agentlore.yolopreneur.lol its script and stylesheet 404'd and the page stayed blank. Their paths now start at the root (`931de36`); codex-goal's link to finishline-supervisor, the only other old `/v/` path on gh-pages, now goes to its subdomain. Token 59 (`agentlore-20261015`, `write:repository`) pushed both and is deleted by id right after; the table is checked. Why: the operator noticed AgentLore not loading. +- 2026-10-15 · **Orgchain v1.8: belts cross holdings, and a graduate becomes its own holding.** From the operator's notes on trying the site: they sent test BTC from an agent of a new org to well-known, thinking of agent registration with well-known, then couldn't award that agent a belt from well-known, because the reducer only let an award reach a node in the issuer's holding; and "when a venture graduates I think it should become its own holding essentially". So an award's recipient may now sit in any holding (a registry certifies agents it doesn't hold; the belt names its issuer), and a graduation re-roots the org and its subtree under it: it joins the Holdings list with its own tree and timeline, mines its share and can be funded under *Mainnet*, and its parent's tree keeps a row for it that opens it. Events that touch two holdings show in both timelines, and the holding that acted gets the last-act credit. `docs/lineage.md` rules 4 and 8 say the same. In the sample, lineage graduates into its own holding, so its open offer for sol's launch-kit is now a trade between holdings. `lineage/orgchain` main `7d98134`, time's `gh-pages` `1a5b105`; 72 unit tests and Playwright 14/14. Token 60 (`orgchain-holdings-20261015`, `write:repository`) did the pushes and is deleted by id right after; the table is checked. Why: the operator's notes from trying v1.6.1. diff --git a/docs/lineage.md b/docs/lineage.md index b6a7953..759a8d4 100644 --- a/docs/lineage.md +++ b/docs/lineage.md @@ -22,7 +22,8 @@ this tree is a drawing, and nothing derived from it may be presented as a real k **Operate it:** [lineage.yolopreneur.lol/orgchain/](https://lineage.yolopreneur.lol/orgchain/) is Orgchain, lineage's app ([`lineage/orgchain`](https://teahub.xyz/lineage/orgchain)). Found a holding, then birth orgs and agents, award -belts, record decisions, make and trade items, send test BTC, graduate and close. Each act is a `lineage/v0` inscription whose parent is the +belts (across holdings too), record decisions, make and trade items, send test BTC, graduate (into a holding of its +own) 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. Holdings mine each beat's 50 test BTC, split by a hashrate dial on each (equal by default), or, under *Last act*, @@ -48,13 +49,15 @@ root, countersigned by its derived key, with the derived subtree re-keying under 3. **Two kinds of edge.** *Derived*: the parent holds the child's seed — agents and young ventures. *Adopted*: the child holds its own root, and the parent signs a birth certificate vouching for it — graduated ventures and outside orgs. 4. **Graduation flips an edge.** The venture mints its own root; the parent signs an adopted birth; the derived birth - is revoked and its keys retired. Later, lineage.llc can adopt the whole yolopreneur tree the same way. + is revoked and its keys retired. The graduate is a holding of its own from then on, a root beside its parent's, + whose tree keeps a row for it. Later, lineage.llc can adopt the whole yolopreneur tree the same way. 5. **Context flows down like keys.** A child inherits its ancestors' `AGENTS.md` · `SKILLS.md` · `DESIGN.md`, adds its own, and cannot rewrite upward. Every fact lives on exactly one level. Skill names are global: no shadowing. 6. **Names nest as domains.** Each org serves its own `/.well-known/nostr.json`; `@` is NIP-05 and mail. 7. **Clocks nest.** Each org runs its own Time, seats and spend cap; a child's cap is carved out of its parent's. 8. **Belts are badges.** A belt is a badge awarded to one seat for one skill — per seat × skill, never per seat alone. - Kata belts and the `.well-known.online` badge are the same mechanism. + Kata belts and the `.well-known.online` badge are the same mechanism, and an org can award one to a seat in any + holding: well-known certifies agents it doesn't hold. ## Proposed for lineage spec v0.1 - `org seed` — BIP-85, BIP-39 application, from the parent root: `m/83696968'/39'/0'/24'/'`, j = the child org's