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
fix(fact-checker): show the image evidence the verdict was actually based on
nirholas0147a3e8a29a
diff --git a/agents/fact-checker/src/image-evidence.js b/agents/fact-checker/src/image-evidence.jsindex e254cf69e..befcdc0dd 100644--- a/agents/fact-checker/src/image-evidence.js+++ b/agents/fact-checker/src/image-evidence.js@@ -18,7 +18,7 @@ const TIMEOUT_MS = 20_000;// it sits between a low-authority and a mainstream web source in the weighting.const IMAGE_SOURCE_WEIGHT = 0.6;-const STANCES = new Set(['supports', 'contradicts', 'neutral']);+const STANCES = new Set(['supports', 'contradicts', 'partial', 'neutral']);function buildPrompt(claim) {return (@@ -27,10 +27,12 @@ function buildPrompt(claim) {'Examine the image and reply ONLY with compact JSON, no prose, in exactly this shape:\n' +'{"description":"<one sentence describing what the image shows>",' +'"visible_text":"<any text legible in the image, verbatim; empty string if none>",' +- '"stance":"supports"|"contradicts"|"neutral",' ++ '"stance":"supports"|"contradicts"|"partial"|"neutral",' +'"reason":"<one short clause: how the image relates to the claim>"}\n\n' +'stance = supports if the image is genuine evidence FOR the claim, contradicts if it ' +- 'is evidence AGAINST it, neutral if it is unrelated, ambiguous, or clearly manipulated. ' ++ 'is evidence AGAINST it, partial if it bears out one part of the claim while showing ' ++ 'another part to be wrong or overstated, neutral if it is unrelated, ambiguous, or ' ++ 'clearly manipulated. ' +'Do not speculate beyond what is visibly in the image.');}diff --git a/api/_lib/avatars.js b/api/_lib/avatars.jsindex 8b8707208..f190a5a65 100644--- a/api/_lib/avatars.js+++ b/api/_lib/avatars.js@@ -3,6 +3,7 @@import { createHash } from 'node:crypto';import { sql } from './db.js';+import { cacheWrap } from './cache.js';import { publicUrl, thumbnailUrl, presignGet, deleteObject } from './r2.js';import { defaultStorageMode } from './storage-mode.js';import { isUuid } from './validate.js';@@ -322,6 +323,10 @@ function normalizeRigFilter(rigged) {return null;}+// Matches the `s-maxage=60` the public gallery endpoint already sets, so a+// cached total is never staler than the response body it is reported with.+const PUBLIC_TOTALS_TTL_SECONDS = 60;+export async function searchPublicAvatars({q,tag,@@ -419,14 +424,38 @@ export async function searchPublicAvatars({next_cursor: hasMore ? new Date(page[page.length - 1].created_at).toISOString() : null,};if (withTotals) {- const totalsRow = await sql(- `select count(*)::int as total,- coalesce(sum(view_count), 0)::bigint as total_views- from avatars where ${filterConds}`,- filterParams,+ // Catalog-wide totals are an aggregate over every matching row, and no+ // index makes that cheap: on the live 58k-avatar table the unfiltered+ // count + view-count sum is a 42 ms sequential scan of 7,673 heap pages,+ // and it grows in lockstep with the catalog the seed cron is filling.+ //+ // The number it produces is a headline stat, not a correctness input, and+ // /api/avatars/public already tells browsers and the CDN to cache the+ // whole response for 60 s. Caching the aggregate for the same 60 s makes+ // it one scan per minute per instance instead of one per request, so the+ // gallery's cost stops tracking the catalog size. The key carries the+ // filter set, so a filtered gallery view never reads the unfiltered+ // numbers.+ const totals = await cacheWrap(+ `avatars:public-totals:${createHash('sha1')+ .update(`${filterConds}\u0000${JSON.stringify(filterParams)}`)+ .digest('hex')}`,+ PUBLIC_TOTALS_TTL_SECONDS,+ async () => {+ const totalsRow = await sql(+ `select count(*)::int as total,+ coalesce(sum(view_count), 0)::bigint as total_views+ from avatars where ${filterConds}`,+ filterParams,+ );+ return {+ total: totalsRow[0]?.total ?? 0,+ total_views: Number(totalsRow[0]?.total_views ?? 0),+ };+ },);- result.total = totalsRow[0]?.total ?? 0;- result.total_views = Number(totalsRow[0]?.total_views ?? 0);+ result.total = totals.total;+ result.total_views = totals.total_views;}return result;}diff --git a/api/ops/payment-outcomes.js b/api/ops/payment-outcomes.jsindex e2fbe140f..5131dd2a1 100644--- a/api/ops/payment-outcomes.js+++ b/api/ops/payment-outcomes.js@@ -64,6 +64,13 @@ function windowStats(counts) {// are reported but excluded from both denominators.const verifyAttempts = settled + settleFailed + verifyRejected;const settleAttempts = settled + settleFailed;+ // The replay rate needs its OWN denominator, and it is the only one that+ // counts replays: they are refused above verify, so measuring them against+ // verifyAttempts would report a rate above 1 during exactly the flood it+ // exists to detect. Everything that arrived is the honest base. Defined here+ // rather than in a renderer so the board, the page, and any ops script that+ // reads this endpoint all quote one number computed one way.+ const inboundAttempts = verifyAttempts + replayRejected;return {settled,settle_failed: settleFailed,@@ -72,6 +79,8 @@ function windowStats(counts) {unsettled_flush: unsettledFlush,settle_success_rate: rate(settled, settleAttempts),verify_reject_rate: rate(verifyRejected, verifyAttempts),+ replay_reject_rate: rate(replayRejected, inboundAttempts),+ inbound_attempts: inboundAttempts,};}diff --git a/marketing/nvidia-inception/README.md b/marketing/nvidia-inception/README.mdindex 6ec22ebe9..773da98ed 100644--- a/marketing/nvidia-inception/README.md+++ b/marketing/nvidia-inception/README.md@@ -13,6 +13,7 @@ Strategy lives in docs, not here:- [docs/nvidia-visibility-map.md](../../docs/nvidia-visibility-map.md): every NVIDIA surface, the verified intake route for each, and the member benefits still unclaimed- [docs/nvidia-apps-catalog-listing.md](../../docs/nvidia-apps-catalog-listing.md) and [docs/nvidia-apps-catalog-request.md](../../docs/nvidia-apps-catalog-request.md): the Accelerated Apps Catalog listing kit and its outbound email- [docs/nvidia-inception.md](../../docs/nvidia-inception.md): what the membership is, and the rule that it is a program rather than a partnership or an endorsement+- [docs/nvidia-forum-browser-digital-human.md](../../docs/nvidia-forum-browser-digital-human.md): NVIDIA Developer Forums post 3, the browser-native Audio2Face-3D write-up, drafted and owner-gated## Assetsdiff --git a/pages/fact-checker.html b/pages/fact-checker.htmlindex c2e4bcdd0..482037b34 100644--- a/pages/fact-checker.html+++ b/pages/fact-checker.html@@ -47,6 +47,7 @@--verdict-insufficient: #6b7280;--stance-supports: #22c55e;--stance-contradicts: #ef4444;+ --stance-partial: #f59e0b;--stance-neutral: #6b7280;--font-display: 'Space Grotesk', 'Inter', system-ui, sans-serif;--font-body: 'Inter', -apple-system, BlinkMacSystemFont, system-ui, sans-serif;@@ -684,6 +685,10 @@background: rgba(239, 68, 68, 0.12);color: var(--stance-contradicts);}+ .stance-pill.partial {+ background: rgba(245, 158, 11, 0.12);+ color: var(--stance-partial);+ }.stance-pill.neutral {background: rgba(107, 114, 128, 0.12);color: var(--stance-neutral);diff --git a/prompts/finish/production-100-OWNER-ACTIONS.md b/prompts/finish/production-100-OWNER-ACTIONS.mdindex e15453408..bf04f0736 100644--- a/prompts/finish/production-100-OWNER-ACTIONS.md+++ b/prompts/finish/production-100-OWNER-ACTIONS.md@@ -9,32 +9,39 @@ it and, if that unblocks a work order, say which one in the owning pack's `produRows carry the date they were added so staleness is visible. Re-verify a row before actingon it; some resolve themselves as other work lands.-## Open rows (re-verified 2026-09-01; the 2026-08-09 set is folded in below)+## Open rows (rows 1, 2, 3, 8, 9, 15 and 16 re-measured 2026-09-02; the 2026-08-09 set is folded in below)| # | Action | Size | Unblocks | Detail lives in ||---|---|---|---|---|-| 1 | Approve the production deploy (or say "get production working", which is itself the approval). Production is at `ad7b54c16` (2026-08-28), 107 commits behind `main`; seven declared routes 404 live until it lands, and the home-screen widget's PNG card and token endpoint are in the gap. | one yes | Nearly everything user-visible in the map | [01-ship-readiness.md](production-100-01-ship-readiness.md) |-| 2 | Fund the settle sponsor wallet `WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW`. Healthz reports `x402_settle` down with `cause: sponsor_floor` and the sniper worker out of capital (0.2307 SOL to refill its wallets); no config change moves either. | ~1 SOL | x402 settle recovery, backlog 01 retirement, sniper | [../backlog/PROGRESS.md](backlog-PROGRESS.md), 2026-08-02 and 2026-09-01 entries |-| 3 | Decide the stranded customer funds: two customers hold about 0.35 SOL behind the retired encryption key and cannot withdraw. Credit, contact, or write off. The brief that was meant to carry the numbers (`docs/ops/stranded-wallets.md`) does not exist yet; order 02 writes it. | decision | Closing the support obligation | [02-stranded-wallet-reclaim.md](production-100-02-stranded-wallet-reclaim.md), [../backlog/PROGRESS.md](backlog-PROGRESS.md) |+| 1 | Approve the production deploy (or say "get production working", which is itself the approval). Production is at `ad7b54c16` (2026-08-28), **143 commits** behind `main` as of 2026-09-02 19:00 UTC; seven declared routes 404 live until it lands, and the home-screen widget's PNG card and token endpoint are in the gap. | one yes | Nearly everything user-visible in the map | [01-ship-readiness.md](production-100-01-ship-readiness.md) |+| 2 | Fund the settle sponsor wallet `WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW`. Healthz reports `x402_settle` down with `cause: sponsor_floor` (settle 5.9%, 3 of 51 paid attempts over 3 hours, 329 `no_solana_accept`) and the sniper worker out of capital (0.2307 SOL to refill its wallets, funding master holds 0.0250 SOL); no config change moves either. Re-read 2026-09-02: the sponsor holds **0.001568 SOL**, so the Solana accept is withdrawn from every 402 challenge. | ~1 SOL | x402 settle recovery, backlog 01 retirement, sniper | [../backlog/PROGRESS.md](backlog-PROGRESS.md), 2026-08-02 and 2026-09-01 entries |+| 3 | Decide the stranded customer funds: two customers hold about 0.35 SOL behind the retired encryption key and cannot withdraw. Credit, contact, or write off. The brief that was meant to carry the numbers (`docs/ops/stranded-wallets.md`) still does not exist, and it cannot be written from this workspace: the audit that produces the wallet list needs `WALLET_ENCRYPTION_KEY`, which lives only on the Cloud Run service, so **row 15 gates this row's prerequisite too**. A keyless run used to answer 725 of 725 wallets sealed and 8.57 SOL stranded; since 2026-09-02 it exits 3 instead of inventing that number. | decision | Closing the support obligation | [02-stranded-wallet-reclaim.md](production-100-02-stranded-wallet-reclaim.md), [../backlog/PROGRESS.md](backlog-PROGRESS.md) || 4 | Rotate or explicitly accept the economy master wallet key, which was set as plaintext service env alongside its Secret Manager copy. Order 03 writes the runbook section; the config change itself needs a live `gcloud` (row 15). | decision (+ one fund move if rotating) | 03 closeout | [03-master-key-hygiene.md](production-100-03-master-key-hygiene.md), `docs/ops/gcp-production.md` 2026-07-09 entry || 5 | Accept the Anthropic terms in Vertex Model Garden for `aerial-vehicle-466722-p5`, then an agent flips `VERTEX_CLAUDE_ENABLED=1` after a live probe. | minutes | First-party Claude lane | `docs/ops/llm-lanes.md` || 6 | Either reactivate OpenAI billing or approve dropping the key; every OpenAI rung is a dead attempt in the chain. Also: OpenRouter fallback key #1 is revoked and still burns a rung; fund the OpenRouter platform key or stay `:free`-only. | minutes | LLM chain latency | `docs/ops/llm-lanes.md` || 7 | Mint an R2 "Admin Read and Write" token scoped to the storage bucket, put it in `.env.local`, so `scripts/set-r2-cors.mjs` can apply the CORS policy at the origin. | minutes | backlog 05 retirement, `ISSUES.md` item 9 | [../backlog/05-r2-bucket-cors.md](backlog-05-r2-bucket-cors.md) |-| 8 | Refresh the GitHub PAT (classic, `public_repo`); the stored one returns Bad credentials. Blocks one docs push in a sibling repo. | minutes | backlog 09 residue | [../backlog/00-INDEX.md](backlog-00-INDEX.md), order 09 |-| 9 | Generate a NEW testnet deployer key for backlog 07 and fund it via the public faucet (reCAPTCHA-gated), then say yes to the broadcast. The key generated on 2026-08-02 no longer exists on this machine (`contracts/.env` is gone) and its address holds nothing; funding it would strand the tokens. | minutes + one yes | backlog 07 retirement | [../backlog/00-INDEX.md](backlog-00-INDEX.md), order 07 |+| 8 | Sign in at the third-party indexer with the platform wallet and register origin `https://three.ws`. Re-checked 2026-09-02: the PAT this row used to ask for is no longer needed (the upstream pull request it would have commented on merged 2026-08-11, and the live discovery endpoint still answers with 100 resources), and the row was attributed to backlog 09, which needs nothing. Origin registration is a signature, not a spend, but it binds an identity, so it is the owner's. | minutes + one signature | backlog 10 retirement | [../backlog/10-x402scan-listing.md](backlog-10-x402scan-listing.md), step 3 |+| 9 | Fund `0x1C4918894dfA5eE11cfF9629B458b5169Cfa3871` from the public faucet (reCAPTCHA-gated, so no agent path), then say yes to the broadcast. This row's old premise is retired: a deployer key **does** exist in the gitignored `contracts/.env`, re-verified 2026-09-02 at balance 0 and nonce 0, both dry runs simulate green against the live RPC, and the broadcast path is proven end to end on a local node. Roughly 0.0003 tBNB of gas covers both deploys. Do not fund the retired 2026-08-02 address. | minutes + one yes | backlog 07 retirement | [../backlog/00-INDEX.md](backlog-00-INDEX.md), order 07 || 10 | The marketplace-listing pack needs its email OTP as `[email protected]` for two reads (the approval status of the listing resubmitted on chain 2026-08-27, and the chat-bot session), plus buyer-wallet funding for the real-payment gauntlet and an AI-provider key on the chat-bot service, whose Cloud Run deploy is also owner-gated (it has never reported a heartbeat). | minutes + funding | The pack's orders 04, 07, 08 and backlog 08 | that pack's `RUNBOOK.md` and `e2e-evidence/FUNDING-REQUEST.md` || 11 | Clear the commit gate for the backlog orders whose diffs reference third-party projects (07 through 10), per the CLAUDE.md coin rule, if that work should land in history. | one yes each | backlog 07 to 10 commits | [../backlog/00-INDEX.md](backlog-00-INDEX.md) || 12 | Multiplayer scale decision: the world service is a pinned single instance with a measured 400-concurrent ceiling and no autoscale (room affinity needs Redis first). Decide whether to fund or approve the Redis-backed scale-out. | decision | quality-bar 03 scope | [../event/PROGRESS.md](event-PROGRESS.md), preflight residuals || 13 | Decide how to close out the 2026-08-09 community event. Re-measured 2026-09-02 and the picture changed: the world server was never redeployed with the event build, so there were no quest runs, no leaderboard writes and no souvenir grants at all, and there is no list to settle from. The countdown, the `/event` page and the in-world meetup layer did run. Options: re-run the event now that the server-side code is live on production, settle from nothing and close it out publicly, or hold. Two reads that would overturn this finding are in row 15. | decision | event 08 closeout | [PROGRESS.md](event-PROGRESS.md), 2026-09-02 entry || 14 | Clear the commit gate for the 2026-09-01 retirement batch: three verified-shipped or superseded work-order files, plus the doc lines that cite them, whose content names other crypto projects (backlog 10; the marketplace pack's order 05, superseded by 08 with its resubmission confirmed on chain; the retired second-chain-venue pack's three context files, whose facts are duplicated in that venue's READMEs). The agent report of that date lists the exact paths and the referrer lines to rewrite. | one yes | Those deletions and the stale doc lines | [PROGRESS.md](production-100-PROGRESS.md), 2026-09-01 entry |-| 15 | Re-authenticate `gcloud` in this workspace (`gcloud auth login`); token refresh fails non-interactively, and so does application-default. Blocks the Cloud Scheduler comparison (fix-queue 03), the master-key config change (03), row 18, and every fleet check in quality-bar 03. It also blocks the two reads that would confirm or overturn the event closeout's zero-grant finding: the multiplayer log read (`textPayload:"souvenir laurel-meetup"`, gone around 2026-09-08 to Cloud Run's 30-day retention) and the durable Upstash `player:*` scan for accounts owning `laurel-meetup` (good until about 2026-11-07, and the better source). Both queries are written out in the event pack's 2026-09-02 entry. | minutes | fix-queue 03, 03, 13, 18, quality-bar 03 | CLAUDE.md self-unblock playbook, [PROGRESS.md](event-PROGRESS.md) |-| 16 | Create the `three-ws` GitHub organization and `three-ws/examples` (public), then run the push command `npm run export:satellites` prints. The export stages 70 files offline today; the repo does not exist. | minutes | roadmap developer-resources retirement | [../roadmap/developer-resources-repos.md](roadmap-developer-resources-repos.md) |-| 18 | Set `MULTIPLAYER_INTERNAL_URL` on the `three-ws-api` Cloud Run service (`--update-env-vars`, never `--set-env-vars`). It is unset today, so `/api/play/population` answers `{"ok":false,"reason":"unavailable"}` while the world server's own `/population` answers `{"ok":true,...}` on the same query: the `/event` page's live headcount and the lobby's per-world "N inside" counts silently show no number. Needs row 15 first. | one command | The live headcount on `/event` and the `/play` lobby | [PROGRESS.md](event-PROGRESS.md), 2026-09-02 entry |+| 15 | Re-authenticate `gcloud` in this workspace (`gcloud auth login`); token refresh fails non-interactively, and so does application-default. Re-confirmed dead 2026-09-02 (`gcloud run services list` still answers "Reauthentication failed. cannot prompt during non-interactive execution"). Blocks the Cloud Scheduler comparison (fix-queue 03), the master-key config change (03), row 18, the stranded-funds brief that row 3's decision rests on (the audit needs `WALLET_ENCRYPTION_KEY` off the service env), and every fleet check in quality-bar 03. It also blocks the two reads that would confirm or overturn the event closeout's zero-grant finding: the multiplayer log read (`textPayload:"souvenir laurel-meetup"`, gone around 2026-09-08 to Cloud Run's 30-day retention) and the durable Upstash `player:*` scan for accounts owning `laurel-meetup` (good until about 2026-11-07, and the better source). Both queries are written out in the event pack's 2026-09-02 entry. | minutes | fix-queue 03, 02, 03, 13, 18, quality-bar 03 | CLAUDE.md self-unblock playbook, [PROGRESS.md](event-PROGRESS.md) |+| 16 | Create the `three-ws` GitHub organization and `three-ws/examples` (public), then run the push command `npm run export:satellites` prints. The export stages 70 files offline today; re-probed 2026-09-02, both the organization and the repository still answer 404. | minutes | roadmap developer-resources retirement | [../roadmap/developer-resources-repos.md](roadmap-developer-resources-repos.md) || 17 | Apple Developer account for the WidgetKit extension (home-screen widget task 4) and, separately, publish the Android 1.1.0 build (versionCode 2) to Play. | account + minutes | roadmap native-widgets task 4 and its release | [../roadmap/native-widgets.md](roadmap-native-widgets.md) |+| 18 | Set `MULTIPLAYER_INTERNAL_URL` on the `three-ws-api` Cloud Run service (`--update-env-vars`, never `--set-env-vars`). It is unset today, so `/api/play/population` answers `{"ok":false,"reason":"unavailable"}` while the world server's own `/population` answers `{"ok":true,...}` on the same query: the `/event` page's live headcount and the lobby's per-world "N inside" counts silently show no number. Needs row 15 first. | one command | The live headcount on `/event` and the `/play` lobby | [PROGRESS.md](event-PROGRESS.md), 2026-09-02 entry |Deleted 2026-09-01: the former row 5 (`WALLET_ENCRYPTION_KEY_PREVIOUS` policy), whichdeclared itself "delete on reading" and had outlived that by three weeks.+Re-measured 2026-09-02, and three premises had rotted. Row 8 asked for a credential that+nothing needs any more and pointed at the wrong work order. Row 9 asked the owner to+generate a key that already exists, and named no address to fund. Row 3's brief turned out+to be unwritable from this workspace at all, which makes row 15 the gate on four rows+rather than three. Nothing was cleared by the owner; the corrections are all measurement.+Evidence is in [PROGRESS.md](production-100-PROGRESS.md) under 2026-09-02.+## How agents use this file- Add a row the moment an owner-only remainder appears; never end a session holding onediff --git a/prompts/store-submissions/_generated/TRACKER.md b/prompts/store-submissions/_generated/TRACKER.mdindex e8c7117e0..68f7e1278 100644--- a/prompts/store-submissions/_generated/TRACKER.md+++ b/prompts/store-submissions/_generated/TRACKER.md@@ -1,6 +1,6 @@# three.ws Store Submission Tracker-Last updated: 2026-07-15 (live re-verification of the Claude Connectors free-lane blocker: production `POST /api/mcp-studio tools/call forge_free` returned HTTP 200 in 16.1s with a real 1,553,784-byte GLB (`glTF` magic, served from `/cdn/forge/anon/…`), and the emitted `/viewer?src=` link returned 200. The 2026-07-08 90-100s hang no longer reproduces; the Connectors package is clear to file once the two `[HUMAN:]` items in its row (org/portal access, `MCP_REVIEW_SECRET` + reviewer-credential decision) are done.) Prior: 2026-07-14 (owner CREATED the GPT Store GPT — URL recorded in its row; store visibility still to confirm. Same day: verified organization confirmed on platform.openai.com; submission package finalized with support contact, privacy URL, and the live 9-tool surface; fresh E2E on both the MCP studio and the Actions lane). Prior: 2026-07-10 Track G build-status reconciliation. Re-run prompt 14 near the end to refresh status.+Last updated: 2026-09-02 (tool-count reconciliation: the free studio connector serves **eleven** tools live, not the nine or ten quoted around the repo. `look_at_model` landed 2026-08-28 and `check_job` before it, and every count, listing table, annotation table, announcement document and social card is now reconciled against a fresh `tools/list` pull, with `tests/mcp-studio.test.js` pinning the total so the next tool cannot re-open the drift. Also re-verified live the same day: `/.well-known/3d-studio-openapi.yaml`, `/.well-known/ai-plugin.json`, `/legal/privacy`, `/legal/tos` and `/support` all return 200, and `resources/list` returns the two widget resources. Dated notes below are kept as the record of what was true when written.) Prior: 2026-07-15 (live re-verification of the Claude Connectors free-lane blocker: production `POST /api/mcp-studio tools/call forge_free` returned HTTP 200 in 16.1s with a real 1,553,784-byte GLB (`glTF` magic, served from `/cdn/forge/anon/…`), and the emitted `/viewer?src=` link returned 200. The 2026-07-08 90-100s hang no longer reproduces; the Connectors package is clear to file once the two `[HUMAN:]` items in its row (org/portal access, `MCP_REVIEW_SECRET` + reviewer-credential decision) are done.) Prior: 2026-07-14 (owner CREATED the GPT Store GPT — URL recorded in its row; store visibility still to confirm. Same day: verified organization confirmed on platform.openai.com; submission package finalized with support contact, privacy URL, and the live 9-tool surface; fresh E2E on both the MCP studio and the Actions lane). Prior: 2026-07-10 Track G build-status reconciliation. Re-run prompt 14 near the end to refresh status.**Last verified: 2026-07-10** — method: direct code read of every prompt-17–21 implementation file plus its wiring, and a live run of the Track-G/16 suites. `npx vitest run tests/spatial-mcp.test.js tests/provenance-3d.test.js tests/ar-export.test.js tests/embed-gate.test.js tests/mcp3d-persona-identity.test.js tests/tokenize-3d.test.js` → **6 files / 98 tests, all passing** (spatial-mcp 22, provenance-3d 20, ar-export 13, embed-gate 20, mcp3d-persona-identity 8, tokenize-3d 15). Confirmed the five new 3D-Studio tool groups are wired into `api/_mcp3d/catalog.js` (`spatialDefs`, `arDefs`, `provenanceDefs`, `personaIdentityDefs` — lines 7–10, 25) and `create_gated_embed` into `api/_mcp/catalog.js` (line 13/21). Confirmed the P0 `readBody` fix is present in the tree (commit `ba37182f3`).@@ -36,7 +36,7 @@ Legend: **not-started** | **blocked** | **ready-to-submit** | **submitted** | **| 14 | Cross-store asset kit | ✅ complete | `_generated/assets/`, `listing-copy.md`, `TRACKER.md` || 02 | Claude reviewer access guide | ✅ complete (shipped 2026-06-25; re-audited + closed out 2026-07-08) | `_generated/claude-reviewer-guide.md` + `_generated/claude-tool-call-evidence.md` (16/16 paid tools clean `PaymentRequired`; review-mode entitlement is real code in `mcp-server/src/payments.js`) || 03 | Claude submission package | ⬜ not started | `_generated/claude-submission.md` (exists from earlier run — verify/refresh) |-| 04 | OpenAI free 3D endpoint | 🟨 code-complete, was blocked on the P0 hang | `api/mcp-studio.js` + `api/_mcp-studio/*` — 9 tools (6 generation incl. `refine_model`, 3 persona), real rate limiting (`api/_lib/rate-limit.js:413-496`), zero coin surface (grep-clean), 46/46 tests pass (`tests/mcp-studio*.test.js`). `server-studio.json` description corrected (was stale "five tools"). Blocked end-to-end verification on the P0 `readBody` hang (code fix landed, commit `ba37182f3`; prod re-verification remains) and the `/viewer?src=` 404 (dist/viewer.html exists and the vercel.json rewrite is correct — likely just stale on the previously-deployed container; re-verify against the live revision) |+| 04 | OpenAI free 3D endpoint | 🟨 code-complete, was blocked on the P0 hang | `api/mcp-studio.js` + `api/_mcp-studio/*` — 11 tools live as of 2026-09-02 (6 generation incl. `refine_model`, the `check_job` collector, the `look_at_model` inspector, 3 persona), real rate limiting (`api/_lib/rate-limit.js:413-496`), zero coin surface (grep-clean), 46/46 tests pass (`tests/mcp-studio*.test.js`). `server-studio.json` description corrected (was stale "five tools"). Blocked end-to-end verification on the P0 `readBody` hang (code fix landed, commit `ba37182f3`; prod re-verification remains) and the `/viewer?src=` 404 (dist/viewer.html exists and the vercel.json rewrite is correct — likely just stale on the previously-deployed container; re-verify against the live revision) || 05 | OpenAI Apps SDK component | ✅ complete (prior session) | GLB viewer component; hero screenshot || 06 | OpenAI submission package | 🟨 package complete, verdict was NOT READY on B1/B2 | `_generated/openai-submission.md` (7/7 policy PASS, real screenshots, real captured tool responses with no PII/internal-ID leakage). Its own §0 verdict cites B1 (rate-limiter hang — this was actually the P0 `readBody` bug, not a quota issue; code fix landed, commit `ba37182f3`) and B2 (`/viewer` 404). Re-run the doc's verification steps against the live production revision before treating this as ready-to-submit || 07 | Embodied live agent avatar | 🟨 code-complete, live demo was blocked by the P0 hang | `create_agent_persona`/`get_agent_persona`/`persona_say` (`api/_mcp-studio/persona-tools.js`, mirrored in `api/_mcp3d/tools/studio.js`), real Postgres+R2 persistence (`api/_lib/persona-store.js`, not in-memory), real viseme/lip-sync cascade + emotion→clip mapping + idle loop (`apps-sdk/embodiment/embodiment-stage.js`, `src/embodiment/*`), never-T-pose fallback gate. 67/67 tests pass. Evidence (6 real rendered screenshots) in `_generated/embodiment/` — captured locally (`npm run dev`), not yet re-confirmed against redeployed prod |diff --git a/scripts/audit-docs.mjs b/scripts/audit-docs.mjsindex d20e43f84..f8afca16c 100644--- a/scripts/audit-docs.mjs+++ b/scripts/audit-docs.mjs@@ -308,6 +308,7 @@ const UNPUBLISHED_DOCS = new Map([['nvidia-apps-catalog-listing', 'internal: paste-ready listing copy and portal steps for the NVIDIA Inception catalog'],['nvidia-apps-catalog-request', 'internal: outbound email asking NVIDIA to publish the catalog listing'],['nvidia-visibility-map', 'internal: outreach priorities and unclaimed program benefits across every NVIDIA surface'],+ ['nvidia-forum-browser-digital-human', 'internal: forum post drafted for the NVIDIA Developer Forums, owner-gated until posted'],['openai-listing-channels', 'internal: submission strategy and a candid post-mortem of our own stalled Cookbook PR'],['okx-marketplace', 'owner-gated: names a crypto project other than $THREE'],['pay-skills-listing', 'internal: listing metadata, not prose'],diff --git a/src/fact-checker-app.js b/src/fact-checker-app.jsindex 55a8adc36..1cca672ff 100644--- a/src/fact-checker-app.js+++ b/src/fact-checker-app.js@@ -74,8 +74,17 @@ function faviconUrl(sourceUrl) {}function stancePill(stance) {- const labels = { supports: 'Supports', contradicts: 'Contradicts', neutral: 'Neutral' };- return `<span class="stance-pill ${stance}">${labels[stance] || stance}</span>`;+ // `partial` is a source that bears the claim out in one respect and corrects+ // it in another. It is what drives the `mixed` verdict, so it carries the same+ // amber the mixed badge does (see .stance-pill.partial in pages/fact-checker.html).+ const labels = {+ supports: 'Supports',+ contradicts: 'Contradicts',+ partial: 'Partly true',+ neutral: 'Neutral',+ };+ const known = Object.prototype.hasOwnProperty.call(labels, stance) ? stance : 'neutral';+ return `<span class="stance-pill ${known}">${labels[stance] || stance}</span>`;}function renderSources(sources) {diff --git a/tests/api/fact-check-verdict.test.js b/tests/api/fact-check-verdict.test.jsnew file mode 100644index 000000000..5673ce284--- /dev/null+++ b/tests/api/fact-check-verdict.test.js@@ -0,0 +1,174 @@+/**+ * Unit tests for api/x402/fact-check.js#computeVerdict, the weighted verdict+ * calculus behind every fact-check answer and behind the published accuracy+ * benchmark on /fact-check.+ *+ * Written against SYNTHETIC stance distributions on purpose. The benchmark+ * fixture is 40 real claims scored through the live chain; shaping the calculus+ * to those ten `mixed` claims would fit the fixture rather than fix the rule.+ * These cases pin the rule itself:+ * • the clear-cut distributions (unanimous, near-unanimous, empty, silent)+ * keep their verdicts, so the mixed band can never swallow them+ * • `partial` weight is stance-bearing but takes neither side, which is the+ * route by which a claim every source calls "true in one respect, wrong in+ * another" reaches `mixed` instead of `contradicted`+ * • confidence for `mixed` measures how strongly the evidence establishes+ * mixedness, not how lopsided the split was+ */++import { describe, it, expect } from 'vitest';+import { _computeVerdict as computeVerdict } from '../../api/x402/fact-check.js';++/** Build n sources of one stance at a uniform weight. */+const of = (stance, n, weight = 0.8) =>+ Array.from({ length: n }, (_v, i) => ({ url: `https://example.com/${stance}/${i}`, stance, weight }));++describe('computeVerdict — clear-cut distributions keep their verdicts', () => {+ it('unanimous support is supported', () => {+ expect(computeVerdict(of('supports', 5)).verdict).toBe('supported');+ });++ it('unanimous contradiction is contradicted', () => {+ expect(computeVerdict(of('contradicts', 5)).verdict).toBe('contradicted');+ });++ it('exactly 70% of stance weight one way still lands on that side', () => {+ // 7 supporting + 3 contradicting at equal weight is the boundary itself.+ expect(computeVerdict([...of('supports', 7), ...of('contradicts', 3)]).verdict).toBe('supported');+ expect(computeVerdict([...of('contradicts', 7), ...of('supports', 3)]).verdict).toBe('contradicted');+ });++ it('one dissenting source does not unseat a dominant side', () => {+ expect(computeVerdict([...of('supports', 4), ...of('contradicts', 1)]).verdict).toBe('supported');+ expect(computeVerdict([...of('contradicts', 4), ...of('supports', 1)]).verdict).toBe('contradicted');+ });++ it('authority weight, not source count, decides direction', () => {+ // Two low-authority blogs cannot outvote one encyclopedic source.+ const verdict = computeVerdict([+ { url: 'https://en.wikipedia.org/wiki/X', stance: 'supports', weight: 0.9 },+ { url: 'https://blog.example/a', stance: 'contradicts', weight: 0.15 },+ { url: 'https://blog.example/b', stance: 'contradicts', weight: 0.15 },+ ]);+ expect(verdict.verdict).toBe('supported');+ });++ it('fewer than two sources is insufficient, never a verdict', () => {+ expect(computeVerdict([]).verdict).toBe('insufficient');+ expect(computeVerdict(of('supports', 1)).verdict).toBe('insufficient');+ });++ it('evidence that never engages the claim is insufficient, not mixed', () => {+ // The 2026-07-08 regression: all-neutral used to return "mixed".+ expect(computeVerdict(of('neutral', 5)).verdict).toBe('insufficient');+ });++ it('zero total weight is insufficient', () => {+ expect(computeVerdict(of('supports', 3, 0)).verdict).toBe('insufficient');+ });++ it('a single stance-bearing source lost among silent ones is insufficient', () => {+ const sources = [+ { url: 'https://example.com/one', stance: 'supports', weight: 0.2 },+ ...of('neutral', 4, 0.9),+ ];+ expect(computeVerdict(sources).verdict).toBe('insufficient');+ });++ it('a lone partial source lost among silent ones is insufficient too', () => {+ // `partial` is stance-bearing, so it goes through the same coverage floor:+ // one loosely-matched page must not decide a verdict on its own.+ const sources = [+ { url: 'https://example.com/one', stance: 'partial', weight: 0.2 },+ ...of('neutral', 4, 0.9),+ ];+ expect(computeVerdict(sources).verdict).toBe('insufficient');+ });+});++describe('computeVerdict — mixed by inter-source disagreement', () => {+ it('an even split is mixed', () => {+ expect(computeVerdict([...of('supports', 3), ...of('contradicts', 3)]).verdict).toBe('mixed');+ });++ it('a split just short of the 70% bar is mixed', () => {+ // 2 vs 1 is 66.7% support: below the bar, so neither side owns it.+ expect(computeVerdict([...of('supports', 2), ...of('contradicts', 1)]).verdict).toBe('mixed');+ });++ it('neutral sources dilute confidence but do not change the verdict', () => {+ const tight = computeVerdict([...of('supports', 3), ...of('contradicts', 3)]);+ const diluted = computeVerdict([...of('supports', 3), ...of('contradicts', 3), ...of('neutral', 12)]);+ expect(diluted.verdict).toBe(tight.verdict);+ expect(diluted.confidence).toBeLessThan(tight.confidence);+ });+});++describe('computeVerdict — mixed by intra-source partiality', () => {+ it('unanimous partial evidence is mixed, not contradicted', () => {+ // The defect this stance exists to fix: every source reads the same+ // nuance ("a tomato is botanically a fruit and culinarily a vegetable"),+ // so before `partial` existed they all projected onto one side and the+ // whole mixed class scored 0/10.+ expect(computeVerdict(of('partial', 5)).verdict).toBe('mixed');+ });++ it('partial weight blocks a side from clearing the 70% bar', () => {+ // 3 supports + 2 partial: 60% support, below the bar.+ expect(computeVerdict([...of('supports', 3), ...of('partial', 2)]).verdict).toBe('mixed');+ expect(computeVerdict([...of('contradicts', 3), ...of('partial', 2)]).verdict).toBe('mixed');+ });++ it('a lone partial source does not unseat an otherwise dominant side', () => {+ // 8 supports + 1 partial is still 88.9% support. `partial` dilutes+ // dominance; it does not veto it.+ expect(computeVerdict([...of('supports', 8), ...of('partial', 1)]).verdict).toBe('supported');+ });++ it('partial mixed with both directions is mixed', () => {+ expect(+ computeVerdict([...of('supports', 2), ...of('contradicts', 2), ...of('partial', 2)]).verdict,+ ).toBe('mixed');+ });+});++describe('computeVerdict — confidence semantics', () => {+ it('broad engagement outscores thin engagement at the same dominance', () => {+ const broad = computeVerdict(of('supports', 5, 0.8));+ const thin = computeVerdict([...of('supports', 2, 0.8), ...of('neutral', 8, 0.8)]);+ expect(broad.confidence).toBeGreaterThan(thin.confidence);+ });++ it('an even split is MORE confidently mixed than a lopsided one', () => {+ // The old rule scored mixed confidence as max(support, contra), so the+ // closer a split came to breaking one way, the more sure it claimed to be+ // that it had not. Mixedness is the thing being measured now.+ const even = computeVerdict([...of('supports', 3), ...of('contradicts', 3)]);+ const lopsided = computeVerdict([...of('supports', 2), ...of('contradicts', 1)]);+ expect(even.confidence).toBeGreaterThan(lopsided.confidence);+ });++ it('unanimous partial is as confidently mixed as an even split', () => {+ const partial = computeVerdict(of('partial', 6));+ const split = computeVerdict([...of('supports', 3), ...of('contradicts', 3)]);+ expect(partial.confidence).toBe(split.confidence);+ });++ it('every confidence is a bounded, rounded probability', () => {+ const cases = [+ of('supports', 5),+ of('contradicts', 5),+ of('partial', 5),+ [...of('supports', 3), ...of('contradicts', 3)],+ [...of('supports', 3), ...of('partial', 2), ...of('neutral', 4)],+ of('neutral', 5),+ of('supports', 1),+ ];+ for (const sources of cases) {+ const { confidence } = computeVerdict(sources);+ expect(confidence).toBeGreaterThan(0);+ expect(confidence).toBeLessThanOrEqual(0.98);+ expect(Math.round(confidence * 100)).toBe(confidence * 100);+ }+ });+});diff --git a/tests/api/ops-endpoints.test.js b/tests/api/ops-endpoints.test.jsindex a788eda41..ebbff7fdd 100644--- a/tests/api/ops-endpoints.test.js+++ b/tests/api/ops-endpoints.test.js@@ -20,6 +20,10 @@// 5. all three boards spent the strict `authIp` credential budget, so polling// a dashboard could 429 the operator's login from the same IP. They use the// `authedReadIp` polled-read bucket.+// 6. custody lost to a key rotation was measurable only by running a CLI audit+// by hand, so it stayed invisible for weeks at a time. payment-outcomes+// carries it as a panel, and a failed read names itself rather than+// rendering as zero stranded.import { describe, it, expect, vi, beforeEach } from 'vitest';@@ -56,6 +60,11 @@ vi.mock('../../api/_lib/x402/wallet-balance-monitor.js', () => ({checkRingWallets: () => ringWalletsImpl(),}));+let strandedImpl = async () => ({ status: 'clear', sol_stranded: 0, stranded_funded: 0 });+vi.mock('../../api/_lib/custodial-key-health.js', () => ({+ strandedCustodyPanel: () => strandedImpl(),+}));+const health = await import('../../api/ops/health.js');const { default: moneyHealthHandler, lastActivity } = await import('../../api/ops/money-health.js');const { default: paymentOutcomesHandler } = await import('../../api/ops/payment-outcomes.js');@@ -87,6 +96,7 @@ beforeEach(() => {sqlImpl = async () => [];settleHealthImpl = async () => ({ name: 'x402_settle', status: 'ok' });ringWalletsImpl = async () => ({ wallets: [], sponsorRunway: null });+ strandedImpl = async () => ({ status: 'clear', sol_stranded: 0, stranded_funded: 0 });});describe('cron staleness windows derived from vercel.json', () => {@@ -225,6 +235,30 @@ describe('GET /api/ops/payment-outcomes', () => {expect(body.ok).toBe(true);expect(body.degraded).toEqual([]);});++ it('carries the stranded-custody panel, so lost custody is visible without a CLI run', async () => {+ // Capital sealed behind a retired encryption key is a payment-outcome fact:+ // the treasury cannot reclaim it and the customers holding it cannot+ // withdraw. Before this panel the only way to see the number was running+ // scripts/audit-custodial-key-health.mjs by hand, so nobody did.+ strandedImpl = async () => ({+ status: 'stranded', stranded_funded: 2, sol_stranded: 0.122875505,+ sol_stranded_platform: 0.122875505, sol_stranded_customer: 0,+ brief: null, top_stranded: [],+ });+ const { res, body } = await call(paymentOutcomesHandler, '/api/ops/payment-outcomes');+ expect(res.statusCode).toBe(200);+ expect(body.stranded_custody.status).toBe('stranded');+ expect(body.stranded_custody.sol_stranded).toBe(0.122875505);+ });++ it('names the stranded panel in degraded when its read fails, instead of rendering a silent zero', async () => {+ strandedImpl = async () => { throw new Error('db unreachable'); };+ const { res, body } = await call(paymentOutcomesHandler, '/api/ops/payment-outcomes');+ expect(res.statusCode).toBe(207);+ expect(body.degraded).toEqual(['stranded_custody']);+ expect(body.stranded_custody.error).toBe('db unreachable');+ });});describe('the ops boards share the polled-read bucket, not the credential bucket', () => {