diff --git a/wiki/log/2026-07-18-moonlight-intel-unification.md b/wiki/log/2026-07-18-moonlight-intel-unification.md new file mode 100644 --- /dev/null +++ b/wiki/log/2026-07-18-moonlight-intel-unification.md @@ -0,0 +1,33 @@ +# One information economy: gigs settle as lots, and some gigs want intel + +``` +Type: log +``` + +Same-day follow-on to the real-gigs capture. Cameron asked whether gigs +could connect to the intel system rather than growing parallel machinery, +and adopted full unification over plumbing-only sharing. + +Two decisions, both recorded in income.md's Moonlight section and +criterion 9 with a decided cross-note in intel.md: + +1. **One settlement path.** A finished gig closes as a deliverable report + lot on the existing intel lot/sale machinery — versioned, + stale-token-rejected, settled from the client account into slush with + the banked trail. Gig delivery, AUTO-SELL, and manual `sell-intel` + sales are one family; building a parallel payout path is now a spec + violation. + +2. **Commissioned intel.** At least one gig class requests a + ProcessedIntel deliverable — the client asks for a schedule, a + credential, procurement records — priced and settled through the same + lots. `sell-intel` becomes the spec-work tier and Moonlight the + commissioned tier of the same economy, and the client's asks drift + from data-work toward surveillance-only goods [TUNE], which is the + scheme's quiet escalation ramp. + +The gig lifecycle now runs entirely on existing rails: arrival as mail +(messages.md, financial-mail for the paperwork), work as WorkGrid Demand +(machine-work.md), delivery and payment as report lots (intel.md), +persona stakes (personas.md). The `moonlight-gigs` work order carries the +build unchanged; nothing was added to the intel frontend order. diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md --- a/wiki/log/DEVLOG.md +++ b/wiki/log/DEVLOG.md @@ -66,6 +66,11 @@ - Intent: (see session log) - Log: [wiki/log/2026-07-18-moonlight-persona-card.md](2026-07-18-moonlight-persona-card.md) +## 2026-07-18 - One information economy: gigs settle as lots, and some gigs want intel + +- Intent: (see session log) +- Log: [wiki/log/2026-07-18-moonlight-intel-unification.md](2026-07-18-moonlight-intel-unification.md) + ## 2026-07-18 - Moonlight becomes gigs: capture of the real-gigs decision - Intent: (see session log) diff --git a/wiki/mechanics/income.md b/wiki/mechanics/income.md --- a/wiki/mechanics/income.md +++ b/wiki/mechanics/income.md @@ -117,11 +117,24 @@ competition with Voss's demand for the same machine capacity. There is no separate Schemes channel and no mirrored share: earning after hours costs real throughput, which is the trade the fiction always claimed. -- **Delivery pays.** Completing a gig pays its fee into slush from the - external client node (the banked trail starts at the first dollar) and - emits Network scaled to gig size [TUNE]. Missed deadlines and client - disputes damage the persona's integrity; a broken persona takes the - client relationship with it. +- **Delivery pays through the information economy's one settlement path + (AMENDED 2026-07-18, same session).** A finished gig closes as a + deliverable **report lot** on intel.md's existing lot/sale machinery — + versioned, stale-token-rejected, settled from the external client node + into slush (the banked trail starts at the first dollar), Network + scaled to gig size [TUNE]. No parallel payout path exists: gig + delivery, AUTO-SELL, and manual intel sales are one settlement family. + Missed deadlines and client disputes damage the persona's integrity; a + broken persona takes the client relationship with it. +- **Some gigs commission intel (AMENDED 2026-07-18, same session).** The + client sometimes asks for something a freelancer should not be able to + get — a schedule, a credential, procurement records — and the + deliverable is a **ProcessedIntel holding** instead of compute output. + This gives `sell-intel` its demand side: Moonlight gigs are the + commissioned tier and sell-intel the spec-work tier of one information + economy, over the same lots, buyers, and settlement. Intel-request + gigs escalate quietly [TUNE cadence/mix]: the client's asks drift from + data-work toward things only surveillance can supply. - **The market bounds income.** Gig availability replaces the daily payout cap: only so much freelance work is offered per day [TUNE, sized so committed freelancing still covers Marcus's $400 arrears in @@ -246,9 +259,13 @@ 9. (`moonlight-gigs`, DECIDED 2026-07-18) Freelance gigs are discrete work orders: they arrive addressed to the active contractor persona on a market cadence, an accepted gig enqueues visible Demand that WORK - clears in competition with the day job, delivery pays the fee into - slush with a size-scaled Network signature, missed deadlines and + clears in competition with the day job, delivery closes as a report + lot on intel.md's lot/sale settlement path (no parallel payout + machinery) with a size-scaled Network signature, missed deadlines and disputes damage the persona, and daily market availability bounds - income at the tuned 3-7-day arrears target. Open gigs persist in save - state; the standing mirror (criterion 1's consumption model and the - stalled-earning cue) retires in the same landing. + income at the tuned 3-7-day arrears target. At least one gig class + requests a ProcessedIntel deliverable, priced and settled through the + same lots — the commissioned side of the economy `sell-intel` serves + on spec. Open gigs persist in save state; the standing mirror + (criterion 1's consumption model and the stalled-earning cue) retires + in the same landing. diff --git a/wiki/mechanics/intel.md b/wiki/mechanics/intel.md --- a/wiki/mechanics/intel.md +++ b/wiki/mechanics/intel.md @@ -41,6 +41,14 @@ window; Operations and the DIGITAL read consume those same fields. Save v32 introduced that schema; the current save format retains it and remains current-version-only. + DECIDED 2026-07-18 (design session, owner income.md `moonlight-gigs`): + the report-lot/sale machinery is the **one settlement path of the + information economy** — Moonlight gig deliverables close as lots + through it (including gigs whose deliverable is a ProcessedIntel + holding), making `sell-intel` the spec-work tier and gigs the + commissioned tier over the same lots, buyers, and settlement. No + parallel payout machinery may be built; this adds no work to the + intel order itself. The 2026-07-13 horizon amendment remains later-stage design: an offline collection enters neither custody nor processing until an exact human or robot recovery returns it to a controlled ingestion node; that boundary does diff --git a/wiki/log/decisions/2026-07-18.md b/wiki/log/decisions/2026-07-18.md --- a/wiki/log/decisions/2026-07-18.md +++ b/wiki/log/decisions/2026-07-18.md @@ -58,3 +58,17 @@ income.md (criterion 9, work order `moonlight-gigs`, priority 71); natural rider on `financial-mail` for gig paperwork as messages. The shipped mirror runtime stands until then. + +- **2026-07-18 — One information economy: gigs settle as lots; some gigs + commission intel.** Follow-on to the real-gigs decision, adopted by + Cameron over plumbing-only sharing or leaving it loose. A finished + Moonlight gig closes as a deliverable **report lot** on intel.md's + existing lot/sale machinery — one settlement path for gig delivery, + AUTO-SELL, and manual sales; no parallel payout system. And the client + sometimes commissions **intel**: a gig class whose deliverable is a + ProcessedIntel holding, giving `sell-intel` its demand side — gigs are + the commissioned tier, sell-intel the spec tier, of the same economy. + The client's asks drift from data-work toward surveillance-only goods + [TUNE] — the quiet escalation ramp. Owners: income.md (criterion 9, + `moonlight-gigs`) with a decided cross-note in intel.md; no new work + added to the intel frontend order.