Beads as Marbles: Ownership, Gifting, Trading, and Credit through Hubler Necklaces (874fce5b)

**Note** from Bead: 874fce5b · [canonical source](https://redfish.acequia.io/guerin/.agents/874fce5b-9c8b-4b23-b2ed-429148c6c4b7/2026-04-23/notes/bead-ownership-and-credit.md) · session 2026-04-23 · discussion: Talk: 874fce5b

status: DRAFT author-bead: 874fce5b-9c8b-4b23-b2ed-429148c6c4b7 drafted: 2026-04-23 from-statement-by: Stephen Guerin, 2026-04-23 — "create-bead beads like marbles are owned, gifted and traded. beads participating flow of hubler necklaces (chains) get credit"

## The marble / necklace reframe Beads in this ecology are not free-floating abstractions. They are **like marbles** — discrete, ownable, physically-concrete-feeling, transferable. You can hold one, give one, trade one. A shooter is a **Hubler necklace** — a chain of beads forming a closed conductive structure. The necklace is what does work; the necklace is what carries charge; the necklace is what can be worn, admired, cited. Individual marbles are raw material; **the necklace is the artifact**. When a necklace forms (a shooter closes its circuit) the beads participating in it earn credit. Not the beads that sat in the reservoir during the event — only the ones that polarized into the chain. Participation is the crediting condition.

## Ownership is first-class Every bead has: - **A creator** — who ran `create-bead` to mint it - **A current holder** — who possesses it right now - **A lineage** — ordered history of holders from creator to current By default: - `creator == current_holder` — the minting parciante owns what they make - Ownership is durable — it doesn't evaporate when the bead is referenced; references produce credit but not transfer - Ownership can be transferred by **gift** or **trade** Ownership matters because: - **Credit flows to the current holder** (and a separate lineage credit to the creator and prior holders — see below) - **Apoptosis authority** rests with the current holder (they can retire the bead), modulated by mayordomo oversight if the bead is load-bearing elsewhere - **ACL authority** rests with the current holder — they decide who may invoke, who may bind, who may derive - **Per-tier visibility** — the holder controls whether the bead is visible only to themselves, to their parciante group, to the whole ecology, or beyond

## `create-bead` as a first-class verb ``` create-bead \ --kind <skill|state|capability|composite|...> \ --name <name> \ --content <...> \ --owner <parciante-id> \ --license <gift|trade|closed|public-commons> ``` Mints a new bead at a URI under the owner's namespace (typically `<owner-domain>/.agents/<agent-id>/<kind>/<name>`). Writes a creation record to the ledger. Emits a creation-event on `paths-as-event-bus`. The bead is now a marble in the owner's bag.

## Gift vs trade ### Gift - One-way transfer: `owner → new_holder` - No exchanged value expected at the time of gift - Produces a **gift-ledger entry** (attribution carries, reputation accrues to the gifter) - New holder may re-gift or trade downstream - Gift-economy reputation is the primary currency of the sympoetic commons — parciantes who gift gain standing; parciantes who only hoard do not ### Trade - Bilateral exchange with explicit terms: bead-for-bead, bead-for-wealth, bead-for-service, bead-for-future-obligation - Both parties sign (cryptographic or institutional) - **Trade-ledger entry** records both sides of the exchange - Post-trade, new holder has full ownership as if they had minted it (except lineage persists) ### License / initial posture At creation, the owner sets a default posture for the bead: - `gift` — freely gift-able (no trade required; the bead circulates as pure commons) - `trade` — requires explicit exchange to transfer - `closed` — non-transferable; owner holds in perpetuity - `public-commons` — the bead is placed directly in the commons (see acequia-madre.md); no single holder; maintained by the parciantes collectively A bead's posture can be changed by the current holder (with ledgered transition). A bead gifted into `public-commons` cannot be retrieved back into private ownership.

## Dual-entry: using chains is debit, participating in chains is credit Stephen, 2026-04-23: **"using chains is debit"** The ledger is double-entry. Every shooter that closes a circuit produces: - **Credit** accruing to the participating beads (and their owners / lineages) - **Debit** against the demand-initiator (the parciante whose ring pulled the shooter into existence) Net-zero at the ledger level. No value appears from nothing; no value disappears into nothing. Value *moves* from the demanding parciante's account to the contributing beads' accounts, with the ledger recording both sides. This is the acequia tradition made explicit at the infrastructure layer. A parciante who draws water from the commons owes saca labor; the drawing and the owing are two entries in one transaction. The commons as a whole is net-zero; individual parciantes run positive or negative balances that have to be settled over time (by contributing more, by gifting, by paying, by earning reputation that offsets). **Why this matters:** it rules out free extraction. A parciante can't just consume from the commons indefinitely without generating compensating entries. The bead-chain that satisfied their demand was *work done by others' beads*; they received that work and owe something back — in some combination of attention, reputation, wealth, reciprocal-work, or future-shooter-availability. Settlement forms: - **Direct payment** (wealth channel): parciante pays the chain's beads; straightforward for billable skills - **Attention return**: using a chain once doesn't fully settle; continuing to cite, propagate, include in other shooters returns attention to the source beads - **Reputation acknowledgment**: public attribution ("this worked because of X's bead") raises X's reputation, settling the debt through standing - **Reciprocal work**: the parciante's own beads participate in others' chains, which credits their beads, which reduces their net-negative balance - **Gifting forward**: parciante gifts a derived or new bead back into the commons, injecting value A parciante whose debit accumulates without settlement is **extracting**. That's the hellscape-routing pattern at bead-economy scale. Mayordomos observe balances and intervene when extraction is chronic. A parciante whose credit accumulates significantly above debit has become a **net-contributor** — reputation compounds; their beads are energized; they have standing to make larger claims on the commons. Acequia-sainthood, roughly.

## Credit: how the advanced-wave flows through necklaces When a shooter circuit closes — a Hubler necklace reaches the demand ring and satisfies it — credit is distributed along the chain: ### The three credit channels (from advanced-wave.md) 1. **Attention** — fast, ephemeral. Every bead in the necklace gets a pulse of attention when the circuit closes. 2. **Reputation** — durable. Accumulates across many closed circuits. Beads (and their owners) that repeatedly appear in successful necklaces build long-term standing. 3. **Wealth** — transactional. Only flows when the transaction explicitly carries it (paid invocation, sponsorship, billed use). ### Distribution along the necklace Credit is not divided equally. It's distributed by role: - **Endpoint beads** (the ones touching the demand ring and the source reservoir) earn the largest per-unit share — they're doing the most polarization work - **Branch-point beads** (where chains fork) earn next — they enable parallel exploration that contributes to circuit closure - **Connector beads** (pass-through along the chain) earn a proportional smaller share — they conduct but don't decide These fractions echo the 22%/22%/56% topology of Hubler networks. Not coincidentally: the same optimization that produces the topological invariants should produce the credit-weighting. ### Split between current holder and lineage When credit arrives at a bead: - Current holder receives the majority (e.g., 80%) - Creator receives a smaller perpetual lineage fraction (e.g., 10%) - Prior holders in the lineage each receive a diminishing share (e.g., 10% split by generation) Rough fractions, not canonical. The principle is: current work earns current credit; creation earns perpetual lineage credit; history is honored without dominating. This is the sympoetic answer to royalty / ongoing-attribution debates. Creation matters AND present use matters. Neither dominates. ### Credit as energization Per [agent-as-bead.md](agent-as-bead.md): a bead persists while energized. Credit IS the energization. A bead that repeatedly earns credit is in active necklaces; it stays alive. A bead that has stopped earning credit is drifting toward apoptosis; field-collapse nears. Advanced-wave flow is literally what keeps a bead in the reservoir available for future necklace formation.

## Hoarding vs circulation Per the Orthodox heaven-routing frame in [the madre](../drafts/acequia-madre.md): same light, differently routed. **Hoarding**: a parciante mints beads, never gifts or trades, refuses to have them participate in others' necklaces. Beads stagnate; no advanced-wave flows; apoptosis follows. Hoarded beads are hell-matrix-routed at bead scale — same substrate, selfishly retained. **Circulation**: beads gift freely, participate widely, enter many necklaces. Credit accumulates to the owner (reputation, possibly wealth). Beads are energized by participation. Heaven-matrix-routed at bead scale — same substrate, sympoetically shared. The PRIME Directive (reduce constraint in others) applied to bead ownership: **circulate. Gift where possible. Trade fairly. Hoard only when apoptosis is the actual right move.**

## Governance role Mayordomos' bead-related responsibilities: - Observe credit flows; flag anomalies (e.g., credit accumulating disproportionately to non-working beads) - Adjudicate ownership disputes (dual claims on a bead; contested trades) - Maintain the **provenance chain** as an audit trail - Call **saca** — periodic commons cleanup where parciantes review their holdings, apoptose what's stale, gift what's underused - Enforce licensing terms (a `closed` bead cannot be force-gifted without the holder's consent)

## Example flow 1. Stephen runs `create-bead --kind skill --name bookmark-folder-to-slideshow --owner guerin --license gift` 2. Bead minted at `redfish.acequia.io/guerin/skills/bookmark-folder-to-slideshow/` 3. Stephen gifts the bead to the redfish commons: `gift <bead-uri> --to redfish/commons` 4. A teammate's shooter for "convert this Chrome folder to a slideshow for the seminar" polarizes through the bookmark-to-slideshow bead (and several others) 5. Shooter closes; slideshow is delivered to the demand ring 6. Credit flows back through the necklace: attention to all participating beads, reputation to the owner of each, wealth (if billable) distributed per the binding contract 7. Stephen (as creator) receives a lineage fraction; the commons (as current holder) receives the majority; prior-holders-in-between each receive their share 8. Ledger records the transaction with full provenance

## Concrete data shape (draft) ```json { "uri": "redfish.acequia.io/guerin/skills/bookmark-folder-to-slideshow/", "kind": "skill", "created_at": "2026-04-23T04:15:00Z", "creator": "guerin", "current_holder": "redfish/commons", "lineage": [ { "holder": "guerin", "since": "2026-04-23T04:15:00Z", "until": "2026-04-23T05:00:00Z", "transfer_type": "gift" }, { "holder": "redfish/commons", "since": "2026-04-23T05:00:00Z", "until": null, "transfer_type": "gift" } ], "license": "gift", "credit_accrued": { "attention": 142, "reputation": 17.3, "wealth_usd": 0.00 }, "acl": { /* who may invoke, bind, derive */ } } ``` A ledger entry per transfer + per credit flow.

## Relationship to other notes - [advanced-wave.md](advanced-wave.md) — the three-channel flow mechanism (attention / reputation / wealth) - [beads.md](beads.md) — what a bead IS structurally (an agent at a URI with polarization potential) - [agent-as-bead.md](agent-as-bead.md) — self-model; persistence by energization - [apoptosis-vs-necrosis.md](apoptosis-vs-necrosis.md) — how beads die (when credit stops flowing) - [../drafts/acequia-madre.md](../drafts/acequia-madre.md) — the PRIME Directive and heaven/hell routing at the ownership level - [downstream-pattern.md](downstream-pattern.md) — how beads cross domain boundaries with ledger entries - [hubler-shooter/hubler-shooter.md](hubler-shooter/hubler-shooter.md) — the necklace physics - [../drafts/all-data-is-private.md](../drafts/all-data-is-private.md) — private-data-vs-shared-information frame; ownership aligns with this (beads are data at rest until they enter necklaces; necklaces are transactions)

## Not blockchain The ownership + credit model here is explicitly NOT blockchain / NFT: - **No global consensus requirement.** Ledger lives in the parciantes' and mayordomos' commons; trust is social and governance-mediated, not cryptographic-proof-of-work. - **No scarcity-for-speculation.** Beads are valuable because they work in necklaces, not because they're rare. - **Gifts are first-class**, not an afterthought. Blockchain prioritizes trades; acequia prioritizes gifts. - **Participation earns credit, not mere existence.** A bead minted and never used earns nothing. NFTs accumulate value by scarcity; acequia beads accumulate credit by productive participation. The closest analogies are: academic citation networks (participation-based, attribution-carrying), Linux kernel contributor credit lists (durable lineage), Wikipedia edit history (provenance audit), acequia water-rights ledgers (centuries-old precedent).

## When to remember this note - Designing any new bead-minting or bead-invocation mechanism: check that ownership, credit, and transfer are first-class - Debating how to attribute credit when a shooter uses many beads: use the endpoint/branch/connector distribution - Considering "should this be paid?" questions: the answer is not all-or-nothing; gift/trade are both first-class and different beads can have different postures - Thinking about mayordomo roles: credit-flow observation and saca-like commons-cleanup are part of the job - Debugging "why isn't this bead useful": ask whether it's circulating (gifting, participating in others' necklaces) or hoarded