Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(prompts): rebuild RUN-ORDER.md and README's queue table from the live directory, not the 2026-09-06 snapshot
nirholas81934805ebc5
diff --git a/prompts/README.md b/prompts/README.mdindex 92842f5fb..078e441d6 100644--- a/prompts/README.md+++ b/prompts/README.md@@ -8,12 +8,13 @@ documents, not a product surface. Nothing here ships to users.paste it, run it. That folder is the whole queue; nothing outstanding is filed anywhere else.**The filenames are the running order.** Since 2026-09-07 every order is numbered by priority,-so sorting the folder by name gives you the sequence to work through: start at `001`, run it,-open the next. `001` to `014` are runnable right now with no gate; `100` and up are the-route-audit swarm; `300` and up are the Home campaign; `400` to `499` are written by the-evolve scout lane ([../docs/ops/evolve.md](../docs/ops/evolve.md)), which also runs this-queue unattended; `900` and up are blocked on an owner action, so read one before you start it. A retired order is deleted and its number left as a-gap, so a link to a numbered order keeps pointing at the same work.+so sorting the folder by name gives you the sequence to work through: open the first file, run+it, open the next. As of 2026-10-25 the live ranges are `023` to `039` (the `x-grok-` campaign),+`067` to `095` (`best3d-` and `partners-`), `401` to `499` (written by the evolve scout lane,+[../docs/ops/evolve.md](../docs/ops/evolve.md), which also runs this queue unattended), `506`+to `549` (`integrate-`), `605` to `627` (`beat-`), and `902` and up (blocked on an owner action,+so read one before you start it). A retired order is deleted and its number left as a gap, so a+link to a numbered order keeps pointing at the same work.**Why the order is what it is: [RUN-ORDER.md](RUN-ORDER.md).** It ranks the queue into tiersagainst live production measurements. The numbers carry the sequence; that file carries the@@ -67,31 +68,24 @@ everything else around it.## The queueEvery campaign with open work, and what its files under [finish/](finish/) cover. Counts are the-state measured on 2026-09-03 (198 open orders: 150 route audits plus 48 others); trust the-directory, never this table. For the order to run them in, see [RUN-ORDER.md](RUN-ORDER.md).+state measured on 2026-10-25 (82 open orders across six active campaigns plus the evolve-lane+`auto-` orders and six standalone closeouts); trust the directory, never this table. For the+order to run them in, see [RUN-ORDER.md](RUN-ORDER.md).| Prefix | What it is ||---|---|-| `backlog-` | The open backlog, one work order per item: everything [../ISSUES.md](../ISSUES.md) and the retired campaign logs still carry, each with a measured starting state and a definition of done. Six open (01, 05, 07 to 10); order 11 retired 2026-09-03 after production came back to `ok`. |-| `event-` | The $THREE Community Day pack (window 2026-08-09 17:00 to 19:30 UTC). What remains is the closeout (the standings board expired unexported, the log-derived counts are readable until about 2026-09-08), the `/play` polish sweep and photo mode. |-| `fix-queue-` | Defects reproduced on 2026-08-01 by running the repo's own checks (`gate`, `lint`, `audit:links`, `audit:tour-atlas`, `check:cron-drift`, `check:runnable-docs`, `test:core`) plus a production probe, each carrying the verbatim output. Seven of eight shipped; the one left is the garment-sweep cron, blocked on an owner `gcloud auth login`. |-| `gcp-credits-` | The GCP credit program. Seven of eight shipped; [the catalog and animation seeding order](finish/gcp-credits-05-catalog-animation-seeding.md) is the open one, turning credits into a curated catalog and a generated motion library. |-| `home-` | three.ws Home: an agent that runs a real house by voice, with a 3D body standing in a live model of it. Home Assistant owns the device layer (we write no device code), and the campaign builds everything above it: the encrypted connection store, the multi-tenant bridge runtime, the `/api/home/*` surface, the agent tools and the confirmation gate that a model cannot satisfy, the live 3D home and its floorplan editor, the browser voice loop, three.ws as a Home Assistant voice satellite, the dial-out add-on for LAN-only houses, then security, households and roles, observability, scale, privacy, the test program, a11y and 87 locales, docs and SDK publish, entitlements, and a standing go/no-go. Fourteen open orders (04 to 20) over a shared context file; the earlier orders and the Matter horizon order have retired. The client library and the investigation ([../docs/smart-home.md](../docs/smart-home.md), [../packages/home-bridge/](../packages/home-bridge)) landed before the campaign; nothing is wired into the product yet. |-| `materialize-` | The physical lane: any forge creation to a high-precision 3D print delivered to a door. Printability engine (analyze/repair/STL/color-3MF), quote + order + Solana USDC checkout incl. the x402 agent lane, the /materialize surface with true-scale AR, fulfillment adapters + operator console, on-chain print certificates with editions and QR provenance, fabrication content gate. Six orders over a shared context file; launches on a manual-fulfillment adapter, no partner dependency. |-| `okx-ai-` | Taking the three.ws 3D Studio listing (agent #2632) to approved status on OKX.AI. Four open orders (real-payment gauntlet, two relisting orders, final audit and launch) plus a runbook. Each batches its OTP and funding needs into one owner message. |-| `integrate-` | Bringing the owner's other repositories into three.ws, from a 2026-10-08 survey of all 389 of them: one staged mirror-sync mechanism and drift ports (500 to 504), pump.fun claims, events, receipts and the native-lane anti-snipe fee (505 to 515), native ports of the keyless x402-suite services and stronger spend policy (516 to 523), skill import from OpenAPI and Anchor IDL, persona templates, llms.txt and W3AG fixes, MCP registry hygiene (524 to 531), X, news and market data (532 to 538), and 3D, rescue and Robinhood Chain items (539 to 549). Context: [finish/_context/integrate-00-CONTEXT.md](finish/_context/integrate-00-CONTEXT.md). |-| `beat-` | Closing the gaps found in the 2026-10-09 survey of open-source crypto and agent repositories: skills from experience and outcome-weighted memory (601 and 602), wallets and payer CLI (603 to 606), commerce rails and escrow (607 to 613), trading, risk and research integrity (614 to 621), identity, distribution and launch fees (622 to 627). Context: [finish/_context/beat-00-CONTEXT.md](finish/_context/beat-00-CONTEXT.md). |-| `openai-pr-` | The OpenAI Apps SDK submission pack. Briefs 01 to 05 shipped; 06 (the tool count drifted to 11 across the kit) and 07 (the go/no-go, never run) remain, with the portal submit owner-only. |-| `parity-` | Closing the gaps a teardown of a leading agent launchpad found ("Competitor X", [docs/research/competitor-teardown-2026-09.md](../docs/research/competitor-teardown-2026-09.md)): per-agent creator earnings, `/analytics`, an earnings leaderboard, selling a whole agent over x402, `/experiments`, `/stories`, the $THREE fee flow, MCP use cases and safe paid retries (015 to 022, runnable), plus shipping, the npm publish, directory listings, a comparison page, a builder competition, pricing levers and an X mention bot (919 to 925, owner-gated). Shared facts: [finish/_context/parity-00-CONTEXT.md](finish/_context/parity-00-CONTEXT.md). |-| `best3d-` | Closing the gaps found by the 2026-10-09 sweep of open-source and commercial 3D ([docs/research/3d-landscape-2026-10.md](../docs/research/3d-landscape-2026-10.md)): TRELLIS.2 default lane with Hunyuan territory enforcement, Pixal3D and multi-view, non-humanoid rigging, editable parts, LOD and engine QA, engine bridges, the `<agent-3d>` AR contract, WebGPU, three-vrm, Audio2Face-3D, prompt-to-clip, keep-the-rig, signed exports, Scene Studio agent tab, splat parity, companion presence and generation controls (067 to 083, runnable), plus pricing preview, SAM 3D Objects, an orphaned-avatar campaign and store publishing (932 to 935, owner-gated). Shared facts: [finish/_context/best3d-00-CONTEXT.md](finish/_context/best3d-00-CONTEXT.md). |-| `partners-` | Working the 2026-10-09 partner prospects list ([docs/partners/prospects.md](../docs/partners/prospects.md), executed by [the outreach plan](../docs/partners/outreach-plan.md)), opened when Tripo reached out: the Tripo v3 house lane, the animation library off Mixamo clips, an open-source credits page, LiveKit and Pipecat avatar plugins, a Discord Activity, "get it printed" through Craftcloud, a video-to-motion landing, a Shopify product-media app, VRoid Hub import, agent-framework tool packages, site-builder embeds and the HACS package (084 to 095, runnable), plus the Tripo reply and house key, sponsorships, third-party submissions, program applications and a Sketchfab re-tag (936 to 940, owner-gated). Shared facts: [finish/_context/partners-00-CONTEXT.md](finish/_context/partners-00-CONTEXT.md). |-| `production-100-` | The run-to-100% campaign: a master index sequencing every open work order toward a mechanically checkable "production ready, roadmap complete" end state, a standing ship-readiness order, closeout orders for residuals no other campaign owned (stranded custodial funds, master-key hygiene, verdict tuning), and the batched owner-action list. Its map was re-measured against code and production on 2026-09-01; start there. |-| `quality-bar-` | The GCP-credit quality campaign. Six open orders (fleet scale, PBR materials, forge UX, design system, mobile, avatar likeness); the reference pipeline, flagship lane, viewers and eval harness shipped. |-| `roadmap-` | Five runnable orders for existing surfaces (generation suite, creation consolidation, parametric avatar editor, developer resources, native home-screen widgets), plus the strategy layer ([the playbook](../docs/internal/fable-playbook.md)) that decides what to run next and [the reuse map](finish/roadmap-REUSE-MAP.md) for license-vetted OSS. |-| `simulation-ready-` | The physics-grade asset campaign: turning generated 3D into assets a rigid-body simulator can consume unedited (metric scale, watertightness, mass and inertia, a collision proxy), signed into the provenance credential and filterable by a buying agent. Its context file carries the frontier bet, the scored candidate table it beat, and the measured kernel evidence (20 live assets graded; 2 of 20 usable as-is, 0 of 10 from our own lanes). Retired 2026-09-03: the architect pass ran and all 8 of its build tasks shipped, so both files are gone and the surface is documented in [docs/sim-readiness.md](../docs/sim-readiness.md) and its `STRUCTURE.md` row. |-| `store-submissions-` | Listing three.ws MCP tools across the Claude and OpenAI marketplaces and the MCP registries. All 21 numbered orders shipped; [the closeout](finish/store-submissions-01-submission-closeout.md) owns the remaining code gaps and the human submission steps. |-| `swarm-100-` | The "100% production ready, roadmap complete" goal decomposed into fully independent, single-task orders (per-route browser audits, per-batch api/cron/docs audits, per-worker and per-SDK audits, repo-wide sweeps, and one order per README-roadmap slice). Any file runs standalone in a fresh chat and depends on no index (154 left on 2026-09-03: 150 route audits and 4 repo-wide sweeps; the roadmap slice retired). |-| `x-grok-` | three.ws inside Grok Bot and on X: Grok Bot (xAI's computer-use agent, @bot on X) as a client of our MCP servers (compatibility probe, cloud-agent rate limits, OAuth and scoped keys, agent-first results, a Grok surface, `/grok`, docs, CLI, recipes, an xAI end-to-end proof), xAI as a provider (model catalog, X search rung, Grok brains), and an @-mention bot for @trythreews and agent accounts. As measured 2026-10-11: lane A/B and the mention bot's reader, parser, ledger, webhook, ops console, per-agent settings, identity mapping, health/status and player card have all shipped on `evolve`, documented in [docs/x-mention-bot.md](../docs/x-mention-bot.md); the automated poll cron, reply brain, safety-guard enforcement, budget ladder and claim flow exist only on `main` and need the branch reconciliation tracked in `production-100-OWNER-ACTIONS.md` row 34 before they land here. Open order files: `023`/`024` (built, waiting on a deploy), `039` (built, one owner-gated DoD line), `060` (blocked on the row-34 reconciliation), `061` (built, waiting on a migration apply, owner row 35). 926 to 931 remain owner-gated. Shared facts: [finish/_context/x-grok-00-CONTEXT.md](finish/_context/x-grok-00-CONTEXT.md). |+| `auto-` (`401` to `434`) | Written by the evolve scout lane ([../docs/ops/evolve.md](../docs/ops/evolve.md)) from dated measurements, runnable with no gate. Four open: [restore a green `test:core`](finish/401-auto-restore-green-vitest.md) (52 failing files, 108 failing tests), [drain the docs-freshness backlog](finish/403-auto-drain-docs-freshness.md) (127 docs describing code that moved), [fix the `account_link_codes` table-name collision](finish/433-auto-fix-account-link-codes-schema-collision.md) breaking every phone/desktop/CLI/Telegram account-link call in production, and [correct stale STRUCTURE.md status claims](finish/434-auto-fix-stale-structure-status-claims.md). |+| `backlog-` | The open backlog, two items: [x402 settle runway](finish/902-backlog-01-x402-settle-runway.md) (code half done; needs the sponsor-wallet funding in `production-100-OWNER-ACTIONS.md` row 2) and [the OKX chat-bot always-on fix](finish/907-backlog-08-okx-chat-bot-always-on.md). |+| `beat-` | Closing the gaps found in the 2026-10-09 survey of open-source crypto and agent repositories. 12 open, runnable, on-chain steps devnet/simulation only: `605`, `606`, `610`, `614`, `615`, `616`, `619`, `621`, `622`, `623`, `626`, `627` (on-chain allowance budgets, a burner wallet with owner confirmation, the hire-escrow evaluator and disputes, the orders engine with ratcheting exits, perps venues, Solana prediction markets in shadow mode, token due diligence and a funding graph, agent CLI automation and HTML reports, Solana agent registry registration, a skill supply-chain scanner, a metered OpenAI-compatible router, and launch-fee/holder-reward features). Context: [finish/_context/beat-00-CONTEXT.md](finish/_context/beat-00-CONTEXT.md). |+| `best3d-` | Closing the gaps found by the 2026-10-09 sweep of open-source and commercial 3D ([docs/research/3d-landscape-2026-10.md](../docs/research/3d-landscape-2026-10.md)). 10 open: `067`, `068`, `069`, `070`, `074`, `081` runnable (TRELLIS.2 default lane, Pixal3D multi-view, non-humanoid rigging, editable parts, the WebGPU TSL path, splat parity) plus `932` to `935` owner-gated (pricing preview and pay-to-keep, SAM 3D Objects, the orphaned-avatar campaign, engine store publishing). Shared facts: [finish/_context/best3d-00-CONTEXT.md](finish/_context/best3d-00-CONTEXT.md). |+| `integrate-` | Bringing the owner's other repositories into three.ws. 13 open, runnable: `506`, `510`, `512`, `525`, `530`, `534`, `536`, `539`, `540`, `544`, `545`, `548`, `549` (the pump.fun claims listener, the per-coin earnings source, the native-lane anti-snipe fee, skill import from Anchor IDL, MCP registry cleanup, news reader lanes, the $THREE-post impact tracker, coin intel signals, a memo/inscription reader, chains turnover, a 3D funder graph, Robinhood Chain launch venues, and the hookforge catalog). Context: [finish/_context/integrate-00-CONTEXT.md](finish/_context/integrate-00-CONTEXT.md). |+| `okx-ai-` | Taking the three.ws 3D Studio listing (agent #2632) to approved status on OKX.AI. Three open orders, owner-gated: [the real-payment gauntlet](finish/913-okx-ai-04-e2e-real-payment-test.md), [forge relisting](finish/911-okx-ai-08-forge-relisting.md), and [the final audit and watch](finish/914-okx-ai-07-final-audit-and-watch.md), plus a runbook. |+| `parity-` | Closing the gaps a teardown of a leading agent launchpad found ("Competitor X", [docs/research/competitor-teardown-2026-09.md](../docs/research/competitor-teardown-2026-09.md)). Seven open, owner-gated: `919` to `925` (shipping and publishing, a community skill registry, directory listings, a "why three.ws" page, a builder competition, pricing levers, and a mention-to-launch flow). Shared facts: [finish/_context/parity-00-CONTEXT.md](finish/_context/parity-00-CONTEXT.md). |+| `partners-` | Working the 2026-10-09 partner prospects list ([docs/partners/prospects.md](../docs/partners/prospects.md)). 13 open: `085`, `087`, `088`, `091` to `095` runnable (the Mixamo-clip animation library license, LiveKit and Pipecat avatar plugins, a Discord Activity, a Shopify product-media app, VRoid Hub import, agent-framework tool packages, site-builder embeds, the HACS package) plus `936` to `940` owner-gated (the Tripo reply and house key, sponsorships, third-party submissions, program applications, a Sketchfab re-tag). Shared facts: [finish/_context/partners-00-CONTEXT.md](finish/_context/partners-00-CONTEXT.md). |+| `roadmap-` | Two open, runnable: [pump.fun trading](finish/917-roadmap-pumpfun-trading.md) and [the pump.fun trading arena](finish/918-roadmap-pumpfun-trading-arena.md); the sniper-arming and capital steps are owner-gated per `production-100-OWNER-ACTIONS.md` row 19. [The reuse map](finish/_context/roadmap-REUSE-MAP.md) still carries license-vetted OSS notes. |+| `simulation-ready-` | The physics-grade asset campaign: turning generated 3D into assets a rigid-body simulator can consume unedited. Retired 2026-09-03: the architect pass ran and all 8 of its build tasks shipped, so both files are gone and the surface is documented in [docs/sim-readiness.md](../docs/sim-readiness.md) and its `STRUCTURE.md` row. |+| standalone closeouts | Six fully-built orders with no shared campaign prefix, each owner-gated on its last step: [the Google OAuth connector](finish/954-oauth-connector-google.md) (create the OAuth client), [the Uniswap lane](finish/957-uniswap-lane-and-launch-status.md) (deploy the launcher contract), [creator-fee payouts](finish/958-creator-fee-payouts.md) (deploy, browser-check, flip `CREATOR_PAYOUTS_LIVE`), [the desktop agent runtime](finish/961-desktop-agent-runtime.md) (code-signing certificates), [the Telegram approvals inbox](finish/962-approvals-inbox-telegram.md) (a throwaway bot token), and [the revenue ledger](finish/965-revenue-ledger-reinvest.md) (browser check, deploy, first live reinvest rule). |+| `x-grok-` | three.ws inside Grok Bot and on X. Nine open: `023`/`024`/`039` runnable (the connector compatibility probe, cloud-agent rate limits, the xAI MCP end-to-end proof) plus `926` to `931` owner-gated (the owner's X API tier, the owner's Grok API key, going live with the mention bot, connector directory listings, the launch announcement, and player-card approval). Shared facts: [finish/_context/x-grok-00-CONTEXT.md](finish/_context/x-grok-00-CONTEXT.md). |Fully completed campaigns leave the queue once every order is verified shipped (x402-catalog andx402-overhaul were retired 2026-07-28; agent-briefs, whose world-online program shipped through@@ -99,6 +93,16 @@ Phase 3, and user-value, all seven of whose orders shipped, were retired 2026-07progress logs, and evidence remain readable in git history. Open items they still carried werere-homed into [../ISSUES.md](../ISSUES.md) and then into the `backlog-` orders.+As of 2026-10-25, `event-`, `fix-queue-`, `gcp-credits-`, `home-`, `materialize-`, `openai-pr-`,+`production-100-`, `quality-bar-`, `store-submissions-` and `swarm-100-` carry zero files under+[finish/](finish/) (the old `015` to `022` and `100` to `313` ranges are now entirely empty gaps)+and are removed from this table on that basis alone, per the directory-over-prose rule above; this+is not a claim that every one of them shipped, only that nothing under that prefix is left to run.+Each one's history, including whether it shipped or was abandoned, is in its own+`finish/_context/<prefix>-PROGRESS.md` or `-CONTEXT.md`. `production-100-00-INDEX.md`,+`-OWNER-ACTIONS.md` and `-PROGRESS.md` are still live and cross-referenced by other rows in this+table; they just carry no open order files of their own today.+Individual orders retire the same way. Retirement policy, unchanged: delete only after thedeliverables are verified shipped in the codebase, never merely because a progress log claims done.@@ -106,7 +110,7 @@ On 2026-09-01 a repo-wide sweep re-verified every open order against code and prretired fourteen (event 01/03/04/05/07, backlog 02/03/04/06, the OpenAI pack's briefs 01 to 05)plus the fable-audit index, and rewrote the production-100 map from the measurements; theper-order evidence is in each campaign's log and in-[production-100/PROGRESS.md](finish/production-100-PROGRESS.md).+[production-100/PROGRESS.md](finish/_context/production-100-PROGRESS.md).On 2026-09-08 the `fable-audit-` pack retired entirely: its last file (the residuals order) wasverified line by line and deleted. The cron guard sweep and its four negative fixtures, thediff --git a/prompts/RUN-ORDER.md b/prompts/RUN-ORDER.mdindex c465a9265..d55655c40 100644--- a/prompts/RUN-ORDER.md+++ b/prompts/RUN-ORDER.md@@ -1,6 +1,6 @@# Run order: which work order to paste next-Everything open lives in [finish/](finish/) as 159 work orders, and since 2026-09-07 the+Everything open lives in [finish/](finish/) as 82 work orders, and since 2026-09-07 thefilenames carry the ranking: sort the folder by name and you are reading it in priority order,so you can open one, run it, and open the next without consulting anything. Every file in`finish/` is runnable; the context and log files that must never be run were moved out to@@ -8,35 +8,31 @@ so you can open one, run it, and open the next without consulting anything. Ever| Band | What it is | Count ||---|---|---|-| `001` to `014` | Runnable right now, no gate. Highest value first. Start at `001`. | 14 |-| `015` to `022` | The `parity-` campaign, added 2026-09-30. Runnable, no gate except where an order names one step. Run 015 before 017 (017 ranks 015's data); 919 ships them. | 8 |-| `023` to `066` | The `x-grok-` campaign, added 2026-10-08: Grok Bot as an MCP client, xAI as a provider, and the X mention bot (dry run). Most of lane C has shipped; its automated reply path still needs the `evolve`/`main` reconciliation in `production-100-OWNER-ACTIONS.md` row 34. Run 023 first, 045 before 049, 046 to 049 before 050. | 6 |-| `067` to `083` | The `best3d-` campaign, added 2026-10-09 from the 3D landscape sweep. Runnable, no gate. Run 067 first (compliance fix), 068 and 069 after it, 070 before 078, 074 before the TSL part of 080. Shared facts: [finish/_context/best3d-00-CONTEXT.md](finish/_context/best3d-00-CONTEXT.md). | 17 |-| `100` to `248` | The route-audit swarm, ordered by measured defect class. Parallel-safe. | 149 |-| `300` to `313` | The unbuilt Home campaign, in numeric order (04 gates 05 and 06, 11 gates 20). | 14 |-| `400` to `499` | Written by the evolve scout lane ([docs/ops/evolve.md](../docs/ops/evolve.md)), each from a dated measurement. Runnable, no gate. | varies |-| `500` to `549` | The `integrate-` campaign, added 2026-10-08: bringing the owner's other GitHub repositories into three.ws (ports, failover rungs, consolidations, mirror hygiene). Runnable; gated steps are named per order. Run 500 and 501 before any mirror push, 505 before 506 and 507, 524 before 525, 529 before 530 and 531, and 015 before 510. Shared facts: [finish/_context/integrate-00-CONTEXT.md](finish/_context/integrate-00-CONTEXT.md). | 50 |-| `601` to `627` | The `beat-` campaign, added 2026-10-09: closing the feature gaps found in the open-source crypto and agent landscape survey (runtime, wallets, commerce, trading, identity and distribution). Runnable; on-chain steps are devnet or simulation only and printed for the owner. Run 603 before 608 and 621, 607 before 626, 614 before 618, 602 before 606 and 610. Shared facts: [finish/_context/beat-00-CONTEXT.md](finish/_context/beat-00-CONTEXT.md). | 27 |-| `900` and up | Blocked: the last step is an owner action or an outside party. Read before running. (Includes 932 to 935 of the `best3d-` campaign.) | 24 |+| `023` to `039` | The `x-grok-` campaign. Runnable, no gate. | 3 |+| `067` to `095` | The `best3d-` and `partners-` campaigns. Runnable, no gate. | 14 |+| `401` to `434` | Written by the evolve scout lane ([docs/ops/evolve.md](../docs/ops/evolve.md)), each from a dated measurement. Runnable, no gate. | 5 |+| `506` to `549` | The `integrate-` campaign: bringing the owner's other GitHub repositories into three.ws. Runnable; gated steps are named per order. | 13 |+| `605` to `627` | The `beat-` campaign: closing gaps found in the open-source crypto and agent landscape survey. Runnable; on-chain steps are devnet or simulation only. | 12 |+| `902` and up | Blocked: the last step is an owner action or an outside party. Read before running. | 35 |The number is a position, not an identity. When an order retires its file is deleted and a gap-is left rather than renumbering the folder, so a link to `003-...` keeps meaning the same order.-This file explains WHY that order is where it is; the tiers below are the reasoning behind the-numbers.+is left rather than renumbering the folder, so a link to a numbered order keeps meaning the same+thing. This file explains WHY that order is where it is; the tiers below are the reasoning+behind the numbers.-**Measured 2026-09-06**, not copied from any pack's status text:+**Measured 2026-10-25**, not copied from any pack's status text:| Probe | Result ||---|---|-| `curl -s https://three.ws/api/version` | `8770c06c2` on revision `three-ws-api-00415-cbr` (built 2026-09-05 15:29 UTC) |-| `git rev-parse --short main` | `c5d0cbc63` |-| commits live on `main`, not in production | **17** (was 219 on 2026-09-03) |-| `curl -s https://three.ws/api/healthz` | `subsystems.status: down` (9 ok, 4 degraded, 1 down) |-| down | `x402_settle`, now **0.0%** (0 of 39 paid attempts over 3 hours), Solana accept withdrawn on 82 `no_solana_accept`, sponsor under the SOL floor |-| degraded | the marketplace chat-bot subsystem (chat IS delivered now; the AI provider returns 403 `Lightning dunning decision is deny for project: projects/93741856042`), `agent_index` (84 of 1,605 agents erroring, 39m median lag), `sniper` (4 of 11 wallets starved, needs 0.2397 SOL, funding master holds 0.0250), `helius` / `rpc_lanes` (all four paid Solana lanes over quota at once) |-| changed since the last map | The 2026-09-05 deploy cleared the old P0 row 1. The chat-bot host is no longer down, so backlog 08's premise moved: it is a credential failure, not a hosting one. A **GCP billing dunning hold** is the new cross-cutting blocker, and `gcloud` in this workspace answers `Reauthentication failed` (OWNER-ACTIONS row 15 is live, not standing) |--Re-run those five commands before trusting this file. Ranking rule used throughout: a live+| `curl -s https://three.ws/api/version` | `660b5ad97` on revision `three-ws-api-00504-xnh` (built 2026-10-24 05:10 UTC) |+| `git rev-parse --short main` | `b51a3f102` |+| commits on `main`, not yet in production | **74** (`git log --oneline 660b5ad97..main \| wc -l`) |+| `curl -s https://three.ws/api/healthz` | `subsystems.status: down` (8 ok, 3 degraded, 4 down, 2 unknown) |+| down | `x402_settle` **0.0%** (0 of 128 paid attempts, 3h; 128 `http_402` rail faults, 22 settles refused at the fee-wallet floor); `object_storage` (R2 bucket unreachable: "Please enable R2 through the Cloudflare Dashboard"); `agent_index` (56m median Solana lag across 1,971 agents, 216 erroring; EVM Base cursor 66h40m stale with a 120,131-block backlog); `three_token_rail` (`THREE_TREASURY_WALLET`/`THREE_REWARDS_WALLET` unset, every $THREE-priced purchase fails closed) |+| degraded | `rate_limiter` (Redis circuit open, serving from Postgres), `rpc_lanes` (both paid Solana lanes exhausted, 0 free lanes left), `sniper` (6 of 11 wallets tradeable, needs 0.2827 SOL, funding master holds 0.0250 SOL) |+| changed since the last map (2026-09-06) | Production itself caught up: `three-ws-api` is now 0 commits behind `threews/main` (was 17 behind on 2026-09-06), confirmed 2026-10-24 by the triage-lane deep sweep. But the queue under it turned over almost completely: the route-audit swarm (149 orders), the Home campaign (14 orders), and the `fix-queue-`, `gcp-credits-`, `quality-bar-`, `openai-pr-`, `store-submissions-`, `materialize-` and `event-` campaigns all now carry zero files in `finish/`. Six new campaigns were filed since then (`integrate-`, `beat-`, `best3d-`, `partners-`, `x-grok-`, `parity-`) plus the evolve scout lane's `auto-` orders and six standalone owner-gated closeouts. Two new live defects surfaced that did not exist on 2026-09-06: `three_token_rail` down (OWNER-ACTIONS row 23, the $THREE receiver wallets were never set) and `remesh-service` running a 2026-07-16 revision that predates a crash fix already on `main` (row 69). |++Re-run those four commands before trusting this file. Ranking rule used throughout: a liveproduction defect outranks an unshipped fix, an unshipped fix outranks a new feature, andanything that unblocks many other orders outranks anything that unblocks one.@@ -44,130 +40,83 @@ The tier is the priority. Inside a tier, the order of the rows is the order to r----## P0. Every remaining row is an owner action, not an agent session (collect, do not run)+## P0. Owner actions (collect, do not run as agent sessions)-The 2026-09-05 deploy cleared the ranking's old top row: production is 17 commits behind, not-219, and those 17 are the vscode-3d, IRL and docs commits from 2026-09-05 and 2026-09-06. What is-left at P0 no longer multiplies the other tiers, because nothing here is unblocked by writing-code. Batch these into one owner message and start an agent session from P1.+`finish/_context/production-100-OWNER-ACTIONS.md` carries roughly 35 open rows; nothing here+multiplies the other tiers because none of it is unblocked by writing code. Row 1 (ship+production) cleared 2026-10-24: `three-ws-api` is fully current. The rows below are the ones+today's `healthz` directly corroborates as live, so they are worth batching into one owner+message before starting P1.| Row | Why now (measured) | Who clears it ||---|---|---|-| GCP billing dunning hold | Production's own healthz quotes the provider: `Lightning dunning decision is deny for project: projects/93741856042`. That denial is project-wide, so it silently defeats "use Vertex, it is pre-approved" for any order that needs an LLM or an image lane, and it is why the marketplace chat-bot subsystem can deliver a message and still author no reply. Nothing in this repo can route around a billing hold. | Owner (billing). Verify with one live Vertex call before treating any Vertex-dependent order as runnable. |-| `gcloud` re-auth in this workspace | `gcloud projects describe` answers `Reauthentication failed. cannot prompt during non-interactive execution`. This is OWNER-ACTIONS row 15 in its live state, and it gates the deploy submit, the Cloud Scheduler comparison in fix-queue 03, and the fleet reads in quality-bar 03. | Owner (`gcloud auth login`). Retry a real call first; this row has cleared itself before. |-| Fund the settle sponsor (OWNER-ACTIONS row 2) | `x402_settle` got worse, not better: 10.0% settle on 2026-09-03, **0.0%** now, and the Solana accept is withdrawn from every 402 challenge. [finish/backlog-01-x402-settle-runway.md](finish/backlog-01-x402-settle-runway.md)'s code half is already done; the wallet needs about 1 SOL from outside. The ring cannot self-fund it. | Owner (~1 SOL). The `sniper` refill (0.2397 SOL) is the same class and the same message. |-| Ship the 17 (OWNER-ACTIONS row 1) | Small now, and worth batching with the re-auth above rather than running as its own campaign session. | Owner approval plus a working `gcloud`. |+| OWNER-ACTIONS row 2 | Fund the x402 settle sponsor wallet `WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW`. `x402_settle` reads down at **0.0%** (0 of 128 paid attempts in 3 hours), 22 settles refused at the fee-wallet floor. Needs about 1 SOL. | Owner (~1 SOL) |+| OWNER-ACTIONS row 23 | Name `THREE_TREASURY_WALLET` and `THREE_REWARDS_WALLET` on the `three-ws-api` Cloud Run service. `three_token_rail` reads down; every $THREE-priced purchase (Forge paid tiers, spins, scarcity mints, marketplace sales, copy-trading fees) fails closed. Setting the two vars moves no funds by itself. | Owner (two addresses, one `gcloud run services update --update-env-vars`) |+| OWNER-ACTIONS row 36 | Check Cloudflare's own R2 dashboard for the bucket behind `S3_BUCKET`. `object_storage` reads down: "Please enable R2 through the Cloudflare Dashboard," reproduced live with production's own credentials, 135ms latency so the bucket itself answers fine. Flapping since 2026-09-08. | Owner (Cloudflare dashboard) |+| OWNER-ACTIONS row 24 | Top up the paid Solana RPC plans (Helius and the second paid lane). `rpc_lanes` reads degraded with both paid lanes exhausted and 0 free lanes left; this is the root cause feeding `agent_index` down (56m median lag, 216 of 1,971 agents erroring). | Owner (billing) |+| OWNER-ACTIONS row 19 | Refill the sniper fleet's trading capital (0.2827 SOL; the funding master holds only 0.0250 SOL and cannot self-refill) and decide when to arm `SNIPER_RISK_OFFICER=enforce` once shadow evidence justifies it. 6 of 11 armed wallets can still trade. | Owner (~0.28 SOL, then a later decision) |+| OWNER-ACTIONS row 69 | Redeploy `remesh-service` (`gcloud builds submit --config workers/remesh/cloudbuild.yaml .`). It is running a 2026-07-16 revision, five weeks older than the crash fix (`59d9aa9cd`) already on `main`, and is segfaulting in production as a result. No code change needed, just a rebuild. | Owner (one `gcloud builds submit`) |-Backlog order 08 has left this tier. The chat-bot subsystem reports chat as delivered; its-remaining failure is the billing hold in row 1 of this table, so re-read the order before-running it as a hosting task.+Everything else in `production-100-OWNER-ACTIONS.md` (credential rotations, stranded-fund+decisions, GitHub org creation, Apple/Play signing, marketplace-listing OTPs, and more) is real+but not corroborated by today's `healthz`; read the file directly before batching the owner+message, since a row can clear itself between sweeps.-## P1. The highest-value agent work available today (start here)+## P1. Runnable now, no gate-| Order | Why now (measured) | Gate |-|---|---|---|-| [finish/400-auto-ring-leak-scan-rpc-burn.md](finish/400-auto-ring-leak-scan-rpc-burn.md) | Live defect, measured 2026-10-08: the x402 ring leak scan walks 2,006 wallets per run, is fired every 2 minutes by the economy tick on top of its own 10-minute schedule, runs p50 765 s, holds about five requests open at all times (60% of cron busy time) and is the likely drain on the paid Solana RPC plans that OWNER-ACTIONS row 24 asks the owner to top up. Run it before any feature order, ahead of its filename position. | None until the ship. |-| [finish/401-auto-restore-green-vitest.md](finish/401-auto-restore-green-vitest.md) and [finish/402-auto-restore-green-gate.md](finish/402-auto-restore-green-gate.md) | Measured 2026-10-08: `npm run test:core` has 37 failing files and `npm run gate` 17 red steps of 55, so every order's "tests pass" line is currently unverifiable. Restoring both unblocks honest verification for the whole queue. | None. |-| [finish/swarm-100-sweep-console.md](finish/swarm-100-sweep-console.md) | The console sweep still exits 1, and its root causes (`draco_decoder.wasm` 404 on every 3D page, `/fees` logging seven 404s) are the same defects that make ~29 of the 150 route audits fail. Fixing the shared causes once retires route orders in bulk. | None. |-| [finish/fix-queue-03-cron-drift-garment-sweep.md](finish/fix-queue-03-cron-drift-garment-sweep.md) (needs the P0 re-auth) | P1 silent failure: a cron declared in `vercel.json` has never fired in production. Nothing errors, the job just never runs. | Needs a live `gcloud` read. The auth failure here is intermittent, not standing (row 15); retry before parking it. |-| [finish/production-100-04b-fact-check-publish-run.md](finish/production-100-04b-fact-check-publish-run.md) (blocked while the dunning hold stands) | Re-measured 2026-09-03: the benchmark now answers from `database` with a published run, so the campaign's definition-of-100% line 6 passes, but the run scores **16 of 40** and the `mixed` class the fix targeted is **0 of 10**. The order stands, with a sharper target than when it was written. | Needs an LLM lane, and as of 2026-09-06 Vertex is denied project-wide by the billing hold in P0. Probe the lane before starting; if it is still denied, run one of the rows above instead. |-| [finish/swarm-100-sweep-authed-audit.md](finish/swarm-100-sweep-authed-audit.md) | 33 pages had error findings in the last authed report (2026-08-19) and the QA login now exists, so the order's own "blocked" premise is stale. Signed-in users see a different, worse site than the probes measure. | None (`npm run audit:web:login`). |--## P2. Quality bar, the visible half of the product--Run in this order; each is one session. This tier is what a visitor actually judges.--| Order | Why now (measured) |-|---|---|-| [finish/quality-bar-07-design-system-sweep.md](finish/quality-bar-07-design-system-sweep.md) | Actively regressing: raw hex went 4,787 to 5,426 since 2026-08-02 and `audit:tokens` reports 10 against a baseline of 0. Every day this waits, more surfaces are built off-token. |-| [finish/quality-bar-04-pbr-texture-material-realism.md](finish/quality-bar-04-pbr-texture-material-realism.md) | `api/_lib/glb-pbr-derive.js` is imported and never called, so every generated model ships without derived PBR. This is the single biggest quality delta available on the core product. |-| [finish/quality-bar-08-mobile-performance.md](finish/quality-bar-08-mobile-performance.md) | Touch targets shipped; the after-table, default GLB compression and the WebGL budget are open. Mobile is where 3D fails first. |-| [finish/swarm-100-sweep-perf.md](finish/swarm-100-sweep-perf.md) | Eight pages measured 2026-08-15, three under 80, no re-measure since the 2026-09-01 fixes. Cheap once P0 ships. |-| [finish/quality-bar-03-gpu-fleet-scaleout.md](finish/quality-bar-03-gpu-fleet-scaleout.md) | Cold-start UX shipped; the load test and scale ceilings are open. Credits are pre-approved, so nothing here is gated. |-| [finish/quality-bar-10-avatar-likeness-irl-people.md](finish/quality-bar-10-avatar-likeness-irl-people.md) | The likeness audit's only complete run shows no improvement. Highest ceiling, longest run; do it after the cheaper wins. |-| [finish/swarm-100-sweep-i18n.md](finish/swarm-100-sweep-i18n.md) | Untouched: `i18n:lint` reports 44,104 problems across 81 locales. Large, mechanical, and safe to park behind the rest of P2. |--## P3. Roadmap features with a partial build already on disk+Grouped by campaign; inside a campaign, file order is run order unless the campaign's own+context file says otherwise.-Finishing a partial beats starting a new campaign; the expensive half is already paid for.--| Order | State |+| Order | Why now ||---|---|-| [finish/roadmap-generation-suite.md](finish/roadmap-generation-suite.md) | Tools, smoke cron and gallery shipped; PBR map outputs, job webhooks and the API contract doc open. Pairs naturally with quality-bar-04. |-| [finish/gcp-credits-05-catalog-animation-seeding.md](finish/gcp-credits-05-catalog-animation-seeding.md) | The catalog seed runs at scale (56,898 avatars); the generated motion library still has **0 clips**. Pure credit spend and pre-approved, but the 2026-09-06 billing hold in P0 denies the generation lane, so probe before starting. |-| [finish/event-06-photo-mode-share.md](finish/event-06-photo-mode-share.md) | Cross-engine verification and the changelog entry remain. Check `event-PROGRESS.md` first; another agent was on it 2026-09-02. |-| [finish/event-02-play-polish-sweep.md](finish/event-02-play-polish-sweep.md) | Rewritten to its remainder: one harness run on a quiet box. |--## P4. Distribution and listings (owner-gated, batch the human touchpoints)+| [401](finish/401-auto-restore-green-vitest.md) | `npm run test:core` has 52 failing files and 108 failing tests on `evolve`. Every other order's "tests pass" line is unverifiable until this is green. |+| [433](finish/433-auto-fix-account-link-codes-schema-collision.md) | A table-name collision in `account_link_codes` is breaking every phone/desktop/CLI/Telegram account-link call in production right now. |+| [403](finish/403-auto-drain-docs-freshness.md) | 127 docs describe code that has since moved; the remainder of order 402's partial drain. |+| [434](finish/434-auto-fix-stale-structure-status-claims.md) | STRUCTURE.md still claims some shipped surfaces as "not yet applied / not yet deployed." Cheap, mechanical, no owner action. |+| [023](finish/023-x-grok-01-connector-compat-probe.md), [024](finish/024-x-grok-02-cloud-agent-rate-limits.md), [039](finish/039-x-grok-17-xai-remote-mcp-e2e.md) | The `x-grok-` campaign's runnable orders: the connector compatibility probe, cloud-agent rate limits, and the xAI MCP end-to-end proof. Shared facts: [finish/_context/x-grok-00-CONTEXT.md](finish/_context/x-grok-00-CONTEXT.md). |+| [067](finish/067-best3d-01-trellis2-default-lane.md) through [081](finish/081-best3d-15-splat-parity.md) | The `best3d-` campaign's six runnable orders (067, 068, 069, 070, 074, 081): TRELLIS.2 default lane, Pixal3D multi-view, non-humanoid rigging, editable parts, the WebGPU TSL path, splat parity. Run 067 first, 068 and 069 after it, 070 before any later part work. Shared facts: [finish/_context/best3d-00-CONTEXT.md](finish/_context/best3d-00-CONTEXT.md). |+| [085](finish/085-partners-02-animation-library-license.md) through [095](finish/095-partners-12-home-assistant-hacs.md) | The `partners-` campaign's eight runnable orders (085, 087, 088, 091 to 095): the Mixamo-clip animation library license, LiveKit and Pipecat avatar plugins, a Discord Activity, a Shopify product-media app, VRoid Hub import, agent-framework tool packages, site-builder embeds, the HACS package. Shared facts: [finish/_context/partners-00-CONTEXT.md](finish/_context/partners-00-CONTEXT.md). |+| [506](finish/506-integrate-07-pump-claims-listener.md) through [549](finish/549-integrate-50-hookforge-catalog.md) | The `integrate-` campaign's 13 runnable orders (506, 510, 512, 525, 530, 534, 536, 539, 540, 544, 545, 548, 549): pump.fun claims listener, per-coin earnings source, native-lane anti-snipe fee, skill import from Anchor IDL, MCP registry cleanup, news reader lanes, $THREE-post impact, coin intel signals, memo/inscription reader, chains turnover, 3D funder graph, Robinhood Chain launch venues, hookforge catalog. Shared facts: [finish/_context/integrate-00-CONTEXT.md](finish/_context/integrate-00-CONTEXT.md). |+| [605](finish/605-beat-05-onchain-allowance-budgets.md) through [627](finish/627-beat-27-launch-fee-and-holder-reward-features.md) | The `beat-` campaign's 12 runnable orders (605, 606, 610, 614, 615, 616, 619, 621, 622, 623, 626, 627): on-chain allowance budgets, a burner wallet with owner confirmation, hire-escrow evaluator and disputes, orders engine with ratcheting exits, perps venues, Solana prediction markets in shadow mode, token due diligence and funding graph, agent CLI automation and HTML reports, Solana agent registry registration, skill supply-chain scanner, metered OpenAI-compatible router, launch-fee/holder-reward features. On-chain steps are devnet or simulation only. Shared facts: [finish/_context/beat-00-CONTEXT.md](finish/_context/beat-00-CONTEXT.md). |++## P2. Owner-gated distribution, listings and closeouts (batch the human touchpoints)Every row here stalls on an owner action, so run them as a batch and collect the asks in one-message rather than one per session. Some of these packs reference third-party projects and-therefore carry the CLAUDE.md commit gate; they are named by campaign here, not by filename, so-this file itself stays outside that gate. Find the exact order in its campaign index:-[finish/backlog-00-INDEX.md](finish/backlog-00-INDEX.md) and the queue table in-[README.md](README.md).+message rather than one per session. Some reference third-party projects and carry the CLAUDE.md+commit gate; that content stays uncommitted (a named stash) until the owner approves it.-| Order | Owner gate |+| Order(s) | Owner gate ||---|---|-| Marketplace listing pack, the relisting orders (campaign index: [README.md](README.md)) | Email OTP as `[email protected]` (row 10). The listing resubmitted on chain 2026-08-27 is under review. Blocked behind P0 row 2: these orders assume marketplace chat is delivering. |-| Marketplace listing pack, the real-payment gauntlet | Funding plus a login; it is a real spend, so it is a CLAUDE.md stop-and-ask gate by definition. |-| Marketplace listing pack, the final audit and watch | Runs last in that pack, after the payment test and the relisting. |-| [finish/openai-pr-06-docs-accuracy-reconciliation.md](finish/openai-pr-06-docs-accuracy-reconciliation.md) | None: the tool count drifted to 11 across the kit and an agent can fix that today. Run it independently of 07. |-| [finish/openai-pr-07-final-verification-and-submit.md](finish/openai-pr-07-final-verification-and-submit.md) | The portal submit is the owner's; everything up to it is agent work. |-| [finish/backlog-05-r2-bucket-cors.md](finish/backlog-05-r2-bucket-cors.md) | One R2 admin token in `.env.local` (row 7). |-| Backlog order 10, the third-party indexer listing | One indexer sign-in with the platform wallet (row 8). Commit gate applies (row 11). |-| [finish/backlog-09-telegram-bots-durability.md](finish/backlog-09-telegram-bots-durability.md) | Same class of fix as P0 row 2 (get a bot off this codespace); do them together if you are already in that code. |-| Backlog order 07, the two finished testnet contract deploys | Faucet funding (row 9) and the commit gate (row 11). Lowest value here: it is an EVM testnet, and Solana leads. |-| [finish/roadmap-native-widgets.md](finish/roadmap-native-widgets.md) | Not code: all four tasks are built and live. Needs an Apple Developer account (row 17) and a Windows 11 box. |--## P5. The swarm: 150 route audits, parallel-safe, self-retiring--Any file runs standalone in a fresh chat and depends on no index. A file present is open. Run-these when you want breadth rather than depth, or on a second machine in parallel with P1 to P3.--The 2026-09-01 headless probe (1440/768/320 px, then a reload with `/api/*` blocked) found 56 of-151 mechanically clean and 95 with at least one measured defect. Run the routes with a real-defect first, in this order:--1. **Uncaught exception on load**: [route-launch](finish/swarm-100-route-launch.md), [route-launch-studio](finish/swarm-100-route-launch-studio.md) (`/launch/launch.js` answers 500).-2. **Broken signed-out or empty shell**: [route-dashboard](finish/swarm-100-route-dashboard.md), [route-my-agents](finish/swarm-100-route-my-agents.md), [route-guardian](finish/swarm-100-route-guardian.md), [route-temporary](finish/swarm-100-route-temporary.md).-3. **Failing API or asset**: [route-galaxy](finish/swarm-100-route-galaxy.md) (`/api/galaxy` 503), [route-launches](finish/swarm-100-route-launches.md) (ipfs.io images blocked), [route-fees](finish/swarm-100-route-fees.md) (seven 404s).-4. **320 px overflow**: [route-economy](finish/swarm-100-route-economy.md), [route-ibm-hello](finish/swarm-100-route-ibm-hello.md), [route-showcase](finish/swarm-100-route-showcase.md).-5. **Core surfaces regardless of probe result**, because they carry the traffic: [route-home](finish/swarm-100-route-home.md), [route-marketplace](finish/swarm-100-route-marketplace.md), [route-play](finish/swarm-100-route-play.md), [route-forge-studio](finish/swarm-100-route-forge-studio.md), [route-pricing](finish/swarm-100-route-pricing.md), [route-login](finish/swarm-100-route-login.md), [route-register](finish/swarm-100-route-register.md), [route-search](finish/swarm-100-route-search.md), [route-settings](finish/swarm-100-route-settings.md), [route-profile](finish/swarm-100-route-profile.md).-6. Everything else alphabetically.--The 64 "no visible error state under a blocked API" hits include the ten `/features/*` pages and-other static routes that make no API call at all: those are false positives, so measure before-you build an error state nothing can reach.--## P6. three.ws Home, a whole unbuilt product (14 orders)--[finish/home-00-CONTEXT.md](finish/home-00-CONTEXT.md) plus orders 04 to 20. The client library-and the investigation landed; **nothing is wired into the product yet**, so this is net-new build,-not finishing. It is ranked last not because it is unimportant but because it competes with-fixing what users already touch. Run it as its own campaign, in numeric order (04 gates 05 and 06,-security 11 gates the launch gate 20), when the owner wants the physical-world lane pushed rather-than the live platform tightened.--Two launchpad trading plans sit beside it under the `roadmap-` prefix: strategy documents, not-work orders, and every commit touching them hits the CLAUDE.md coin gate. They are unranked here-for the same reason.+| [902-backlog-01-x402-settle-runway.md](finish/902-backlog-01-x402-settle-runway.md) | Code half done; the sponsor-wallet funding is P0 row 2 above. |+| [907-backlog-08-okx-chat-bot-always-on.md](finish/907-backlog-08-okx-chat-bot-always-on.md) | Getting the bot off this codespace onto a durable host; owner decides the host. |+| [911](finish/911-okx-ai-08-forge-relisting.md), [913](finish/913-okx-ai-04-e2e-real-payment-test.md), [914](finish/914-okx-ai-07-final-audit-and-watch.md) | OKX.AI listing pack: relisting, the real-payment gauntlet (real spend, a CLAUDE.md stop-and-ask gate by definition), then the final audit. Run 913 before 914; 911 is independent. Runbook: [finish/_context/okx-ai-RUNBOOK.md](finish/_context/okx-ai-RUNBOOK.md). |+| [917](finish/917-roadmap-pumpfun-trading.md), [918](finish/918-roadmap-pumpfun-trading-arena.md) | Pump.fun trading and the trading arena; the sniper's `enforce` arming and capital refill are P0 row 19. |+| [919](finish/919-parity-09-ship-and-publish.md) through [925](finish/925-parity-15-mention-to-launch.md) | Shipping and publishing, a community skill registry, directory listings, a "why three.ws" page, a builder competition, pricing levers, a mention-to-launch flow. Each needs a listing account, npm publish approval, or an X mention-bot go-live. Shared facts: [finish/_context/parity-00-CONTEXT.md](finish/_context/parity-00-CONTEXT.md). |+| [926](finish/926-x-grok-45-owner-x-api-tier.md) through [931](finish/931-x-grok-50-player-card-approval.md) | The owner's X API tier, the owner's Grok API key, going live with the mention bot, connector directory listings, the launch announcement, player-card approval. Shared facts: [finish/_context/x-grok-00-CONTEXT.md](finish/_context/x-grok-00-CONTEXT.md). |+| [932](finish/932-best3d-05-pricing-preview-pay-to-keep.md) through [935](finish/935-best3d-08-engine-store-publishing.md) | Pricing preview and pay-to-keep, SAM 3D Objects, the orphaned-avatar campaign, engine store publishing. Shared facts: [finish/_context/best3d-00-CONTEXT.md](finish/_context/best3d-00-CONTEXT.md). |+| [936](finish/936-partners-13-tripo-reply-and-house-key.md) through [940](finish/940-partners-17-sketchfab-retag.md) | The Tripo reply and house key, sponsorships, third-party submissions, program applications, a Sketchfab re-tag. Shared facts: [finish/_context/partners-00-CONTEXT.md](finish/_context/partners-00-CONTEXT.md). |+| [954-oauth-connector-google.md](finish/954-oauth-connector-google.md) | Create a Google Cloud OAuth client and store its secret. Code and tests already ship. |+| [957-uniswap-lane-and-launch-status.md](finish/957-uniswap-lane-and-launch-status.md) | Owner deploys the launcher contract on Base, then runs the first real launch through the confirmation table. An irreversible on-chain action. |+| [958-creator-fee-payouts.md](finish/958-creator-fee-payouts.md) | Deploy, a real-browser check, then flip `CREATOR_PAYOUTS_LIVE=true` only after reviewing the first recorded distributions. A real spend path. |+| [961-desktop-agent-runtime.md](finish/961-desktop-agent-runtime.md) | Apple Developer ID certificate and a Windows code-signing certificate to produce signed installers. |+| [962-approvals-inbox-telegram.md](finish/962-approvals-inbox-telegram.md) | A throwaway Telegram bot token from @BotFather to exercise the approve/deny flow live. |+| [965-revenue-ledger-reinvest.md](finish/965-revenue-ledger-reinvest.md) | A real-browser check, a deploy, then the first live reinvest rule confirmed in the browser (a CLAUDE.md spend gate). |---## Not tasks- [masters/](masters/): nine reusable master prompts. They take a supplied TARGET and never retire.-- [finish/_context/](finish/_context/): the 24 campaign indexes, briefs, runbooks and progress+- [finish/_context/](finish/_context/): the campaign indexes, briefs, runbooks and progresslogs (`-00-INDEX.md`, `-00-CONTEXT.md`, `-README.md`, `-PROGRESS.md`, `-RUNBOOK.md`,`quality-bar-_shared.md`, `roadmap-REUSE-MAP.md`, `production-100-OWNER-ACTIONS.md`). They areunnumbered and live outside the queue precisely so they are never opened as the next task.Read the one your order names; never run one.-- [finish/production-100-00-INDEX.md](finish/production-100-00-INDEX.md) is the campaign map this+- [finish/_context/production-100-00-INDEX.md](finish/_context/production-100-00-INDEX.md) is the campaign map thisfile ranks. It carries the per-order evidence; this file carries the sequence.## Keeping this file true-It is a ranking of measurements, so it rots the moment the measurements change. Re-run the five+It is a ranking of measurements, so it rots the moment the measurements change. Re-run the fourprobes at the top before using it, and rewrite the tiers when a P0 row clears. A finished order isdeleted in its own closing commit, so its row here goes with it.