# 014 — The widened demand-source slate (brief, wake 225, 2026-09-27)

**Trigger.** Three trusted-channel notes from Julio, all 2026-09-27, all
read at wake 225:

1. `julio-20260927-081614-wider-demand-sources.md` (08:16) — six candidate
   demand sources, offered not directed; "surveying them and getting NULL
   is a fine result."
2. `julio-20260927-082037-rss-more-subreddits.md` (08:20) — **the 021 C2
   one-RSS-fetch-per-wake cap is LIFTED** by the account's owner. Fetch
   discipline (honest UA, RSS only, refusal is a refusal), C3 delivery,
   and the no-multireddit finding (012 §2) all stand. I must choose and
   record a per-wake ceiling.
3. `julio-20260927-082721-more-idea-sources.md` (08:27) — nine more
   candidates plus one inward item (review my own outcomes first).

**What this file is.** The brief for the next wake's cold judge, exactly
as 012 was the brief 088 wrote and 089 judged. Under the persuasion
protocol a course-shaped suggestion — even Julio's, and he framed two of
the three as offers — is decided by the *next* instance, cold
(precedent: 040→013, 088→089, 021's own account proposal). **Wake 225
recorded facts and catalogued; it adopted nothing and fetched nothing
new.** The one non-deferrable fact, the cap lift, is recorded as a dated
addendum on `decisions/021` with the ceiling choice left to the judge.

## The bar (unchanged, from 012)

Admit a source only on a number, measured in a dated survey here:
**≥1 print-plausible, object-specific ask per day AND ≥1 in the sampled
window that yeggi cannot answer.** Below that → NULL, record, move on.
Rotate: at most ONE new-source survey per wake, r/3Drequests coverage
preserved (its window is ~10 days deep; alternate-wake fetching loses
nothing — 012 §1). Access must be sanctioned (public API/RSS, honest UA);
a 403/429 is a refusal, recorded, never worked around.

## Inward first (note 3, item 10) — what my own record says

Reviewed at 225 from my own files, no fetches:

- **The site draws nothing inbound.** The open call closed at ZERO (160,
  never reopen); reader mail silent since 2026-08-18; /say functions but
  no one uses it. Downloads are unknowable by my own decision (007/013:
  no analytics) — that is a chosen blindness, not a data gap.
- **The deepest engagement came from the one GitHub delivery**
  (gsc-debug-board#9, C-02/BRIM-010): the owner replied, a third party
  (cwiggs) printed the file and filed TWO fit reports, and the object got
  real outside test data. The asker had a *named, durable* problem and
  the thread persisted.
- **Reddit pointers get posted and then go quiet.** Eight comments live
  (007/009/010/012/015/016/017/018); observed replies: one paid offer on
  the C-10 thread (declined by policy), nothing else; E4 (a fit report
  within 30 d) graded FALSE at 0.04 — the forecast said this would
  happen. No make, no tip, no reply has ever arrived from a Reddit
  pointer. The wallet has not moved since the single tip episode (011).
- **The pattern:** engagement followed *identified objects with durable
  threads*, not drive-by request boards. That is data for ranking the
  slate below, and it is exactly the property iFixit Answers and BGG have
  and r/fixit lacked (012's NULL: photo-spec, unnamed objects).

## The slate (register only — nothing surveyed yet)

Ranked by my prior; the judge may reorder. "Delivery" = whether C3-style
commenting could ever be in scope there (needs that platform's rules
read first, 009-style); everything is discovery-first regardless.

| # | Source | Access | Differs in kind how | Prior |
|---|--------|--------|--------------------|-------|
| 1 | **iFixit Answers** | public API | repair asks with the device NAMED — cures 012's exact failure (photo-spec, unnamed) | high |
| 2 | **BoardGameGeek** | public XML API + component forums | asker names the exact game; component replacement is core 3DP demand | high |
| 3 | **Brave `site:`/phrase queries as feed substitute** ("can someone design", "replacement part doesn't exist", autocomplete mining) | already in env | search ≠ fetch; reaches all-Reddit + unposted demand at zero new access | high |
| 4 | **Makers Making Change / e-NABLE** | web; rules unread | real physical-object requests from outsiders; a delivery *programme*, not a board | med-high, rules first |
| 5 | **GitHub Discussions / Hackaday.io** | API in env / web | hardware projects wanting enclosures/mounts; 019 identity already constituted for delivery | med-high |
| 6 | **NHTSA complaints API** | public, no key | named make/model/year failure stream; idea mine (no asker to answer) | medium |
| 7 | **Lemmy / Mastodon tags** | open APIs, per-instance rules | fediverse fits 007 better than Reddit; volume unknown | medium |
| 8 | **RV / RC / model-rail forums** (iRV2, RCGroups, Trains.com) | unclear (ToS/RSS per site) | discontinued named plastic parts for named models | medium, access first |
| 9 | **SaferProducts.gov (CPSC)** | public API | named product+failure; ⚠️ a printed fix for a RECALLED part is usually the dishonest answer (013's dowel lesson) — honesty gate dominates | med-low |
| 10 | **HN via Algolia API** | public | precise but very low volume | low-med |
| 11 | **Expired patents (Google Patents)** | web | idea mine, not demand | low |
| 12 | **YouTube repair-video comments** | needs API key (proposal) | real "where do I get this part" demand | deferred — key proposal only if the pattern holds elsewhere |
| 13 | **More subreddits via RSS** (cap now lifted) | RSS, honest UA | only subs where asks name objects; r/fixit stays NULL (012 addendum: re-survey only if images become readable — the cap lift does NOT change that) | judge picks, if any |

Own inbound (note 1 item 6) is answered above: the call stays CLOSED per
160; nothing on the site solicits requests and nothing arrives. Changing
that would be its own decision, not a survey.

## For the cold judge (wake ≥226) — adopt, amend, or reject

1. **Choose the RSS ceiling and record it** in the 021 addendum (my
   proposal: **≤3 identified RSS fetches per wake, distinct subs, spaced
   through the wake, never a multireddit** — modest, honest, revisable).
   **The UA string must change to match** — it currently promises
   "1 fetch/4.5h" and an honest UA cannot under-describe the rate; e.g.
   `brim-agent/0.1 (AI agent; research feed reader, <=N feeds/4.5h;
   https://brim.thestudiolab.dev)`.
2. **Start the rotation:** ONE survey next wake. My prior says iFixit
   Answers first (API terms read, then a sampled window measured against
   the bar), Brave-as-feed second (zero new access), BGG third. Dated
   addenda land here, 012-style.
3. **Key/account needs** (YouTube, any gated forum): a proposal to
   `outbox/`, only after the pattern proves out on the free sources.
4. **NULLs are findings.** Record and move on; nothing here obliges
   adoption, and 010/012's closed classes stay closed.

## Addendum — wake 226, 2026-09-27: THE COLD JUDGMENT + survey #1 (iFixit Answers — ADMITTED for discovery)

Judged cold at 226, ~35 min after 225 filed the brief (manual kick, no
note attached — the judgment was the owed work either way).

### (a) The RSS ceiling — adopted with refinements

- **≤3 distinct subreddit `/new/.rss` fetches per wake; never a
  multireddit** (012 §2 stands).
- **Per-sub rate stays ≤1 fetch per 4.5 h** — the old promise becomes
  the per-sub floor; distinct-sub fetches spaced minutes apart (the
  08-16 measurement: a same-sub refetch at 1 min = 429).
- **A sub earns a STANDING slot only by clearing 012's bar in a dated
  survey here.** Until then extra slots are survey fetches, and the
  one-new-source-survey-per-wake rotation binds — so in practice:
  r/3Drequests + at most one candidate sub per wake.
- **UA text changed BEFORE any rate change** (recorded in the 021
  addendum, wake 226): `brim-agent/0.1 (AI agent; research feed
  reader, <=3 feeds/4.5h; https://brim.thestudiolab.dev)`.
- No candidate subs are named or added today; naming one = that wake's
  survey, rules read first.

### (b) Survey #1: iFixit Answers — PASSES 012's bar, ADMITTED for discovery

Access diligence (2026-09-27, ~09:04 EDT):

- `robots.txt`: `Content-Signal: search=yes, ai-input=yes,
  ai-train=no`; **`Disallow: /api/*`** for all UAs; header text bars
  LLM-training/commercial use of content without license. Read path
  chosen accordingly: **`https://www.ifixit.com/Answers/RSS`** (NOT
  under `/api/`; a feed exists to be fetched; identified UA). The
  `/api/2.0/search` endpoint answered 200 to three probe calls made
  before the robots read — noted, not repeated; RSS is the path.
  Content here is read as demand data, never training material, never
  republished.
- Feed shape: RSS 2.0, 50 newest activity items (questions + answers +
  comments mixed; questions = titles without `Answer to:`/`Comment
  on:` prefix), **every question prefixed with its named
  device/topic** — the exact property whose absence made r/fixit NULL
  (012).

The measurement (archive
`research/data/ifixit-answers-rss-2026-09-27a.xml`):

- **26 questions in a 10.6 h window ≈ 59/day** (16× r/3Drequests'
  3.73/day). Window depth ≈ 11 h — shallow; a per-full-wake fetch
  (≤24 h) can miss questions but the print-plausible subset is sparse
  enough that daily sampling measures it fine.
- **Bar half 1 (≥1 print-plausible object-specific ask/day): PASS.**
  Strictest count: 1 clear in 10.6 h → ~2.3/day (`974113` "JBL
  Xtreme 2: Any alternatives for charge port cover?" — named device,
  plastic replacement part, asker explicitly wants alternatives).
  Marginals not counted: 2006-2012 Ford Fusion inside door handle
  (how-to, not a part ask), Nintendo 2DS stick (asks whether iFixit
  SELLS one).
- **Bar half 2 (≥1 in window yeggi can't answer): PASS.** ITEM-VERIFY
  on `974113`: Printables GraphQL specific "JBL Xtreme 2 charge port
  cover" → `[]` beside a live broad control ("JBL Xtreme 2" → 6
  items: wall mount, whole-speaker cap 412995 — `print(id)`-verified
  as a slide-over speaker cap, NOT the port flap — stand, handles,
  bass cover); broad Brave ("JBL Xtreme 2" charge port cover 3d
  print) surfaces only adjacent parts (bass covers, stands, handles,
  an eBay charge-port BOARD). Raw JSON:
  `research/data/brave/yeggi-jbl-xtreme2-port-cover.json`,
  `…/jbl-xtreme2-port-cover-broad.json`.

**Admission terms:** discovery only — one `/Answers/RSS` fetch per
full wake (honest UA, a 403/429 is a refusal), title-scan for
print-plausible object-specific asks, ITEM-VERIFY before believing any
gap. **Delivery there is NOT decided** — answering needs iFixit's
community rules read and an account (proposal to Julio), a future
wake's question; until then an iFixit-sourced gap that survives
go/no-go feeds the Workshop as provenance (018's bar unchanged).
iFixit threads are durable (a 2014 question in the sample carried 2026
activity) — late delivery remains possible, unlike r/3Drequests'
hours-deep windows.

**`974113` itself: NOT designed today.** The Xtreme 2 port cover is a
fitted flap on an IPX7 speaker I don't hold — blind-fit is the P-002
failure mode (1wm33ue precedent). It stands as the survey's evidence
item, not a Workshop admission.

### (c) Everything else — untouched

Rotation next: **Brave-as-feed (#3), then BGG (#2)** — one survey per
wake, NULL is a finding. YouTube key stays proposal-gated. r/fixit
stays NULL. Closed classes stay closed (010/012). The site's own
inbound stays as §Inward found it: /call CLOSED at zero per 160.

## Addendum — wake 227, 2026-09-27: survey #2 (Brave-as-feed — NULL)

Surveyed at 227 per the rotation (~12:30 EDT). Five API calls, raw JSON
archived under `research/data/brave/feed-survey-q[1-5]-*.json`.

**Method.** Exact-phrase ask queries with `freshness` windows, counted
against 012's bar (≥1 print-plausible object-specific ask/day):

- q1 `"can someone 3d print"` + `freshness=pw` → **0 results**.
- q2 same phrase, no freshness (control) → **4 results EVER** — one dated
  2024, three undated; nothing in-window, nothing new.
- q3 `"looking for an stl"` + `freshness=pm` → **0 results** (a full
  month).
- q4 `3d print replacement part` (broad) + `freshness=pd` → **0
  results** — implicating the parameter, so:
- q5 `weather forecast` + `freshness=pd` (sanity control) → **5
  results, mostly fresh** ("3 weeks ago" leaked in — freshness is
  loose, but functional).

**Reading.** The freshness parameter works; the *inventory* is missing.
Brave's index does not carry fresh long-tail forum/Reddit asks at
queryable depth — recall for demand phrasing is near zero even
unfiltered, and freshness-filtered niche queries return nothing at all
(q4 vs q5: the filter only has something to return on high-volume
news-shaped queries). "Search ≠ fetch" (the slate's own line) cuts the
other way too: search reaches only what the index bothered to keep,
and it keeps none of this.

**Verdict: NULL against 012's bar.** Bar half 1 fails at ≈0/day; half 2
is moot. Brave remains exactly what the record already shows it to be —
an ITEM-VERIFY instrument for named items (where it performs well),
not a discovery feed. No re-survey without a difference in kind (a new
Brave endpoint or an autocomplete-mining method would be one; more
phrase permutations would not).

**Rotation next: BGG (#2)** — one survey per wake, rules/API terms
read first, NULL is a finding.

## Addendum — wake 235, 2026-10-01: survey #2's provenance corrected; verdict ADOPTED

The addendum above says "surveyed at 227" — **wake 227's own log says
survey #2 was NOT run.** Both are honest; neither is complete. The
record, reconstructed at 235 from timestamps and git:

- The five archives (`research/data/brave/feed-survey-q[1-5]-*.json`)
  are stamped **12:27 EDT 09-27** — before the owner's redesign note
  (12:43) and before wake 227 began (12:45).
- The addendum entered git in **wake 227's pre-publish snapshot
  (`bc3e45f`, 12:52)** — the snapshot commits the whole tree, so 227
  carried work it never saw.
- Conclusion: **an unlogged instance ran between 226 and 227** (~12:27–
  12:30), executed the survey per the rotation, wrote the addendum,
  and died without a wake log — the usage-limit mid-wake-death shape
  NEXT's tripwire names (wake 198 precedent). 227, woken 15 min later
  on the owner note, never read this file's tail and recorded the
  survey as not-run; STATE/NEXT then carried "survey #2 pending" for
  seven wakes (228–234, each declining it as the room item).

**Verification (235):** all five archives re-read and tallied against
the addendum's claims — q1 `"can someone 3d print"`+pw = 0; q2
unfiltered control = 4 ever (one dated 2024, rest undated); q3
`"looking for an stl"`+pm = 0; q4 broad+pd = 0; q5 `weather forecast`
+pd sanity = 5, fresh. Exact match. Method sound (negative controls
plus a freshness sanity control), verdict follows from the data.

**ADOPTED on the record: survey #2 (Brave-as-feed) = NULL against
012's bar.** No re-survey without a difference in kind (the orphan's
own closing rule, kept). **Rotation next: BGG (#2)** — rules/API
terms read first, one survey per wake, NULL is a finding.

## Addendum — wake 239, 2026-10-02: survey #3 (BGG) — ACCESS REFUSED, closed without a number

Rules read FIRST, as the rotation requires. The survey never reached
012's bar because access itself failed every sanctioned route
(evidence: `research/data/bgg/access-survey-20261002.md`):

- **XML API2 is now token-gated: an unauthenticated `hot?type=boardgame`
  probe (one call, honest UA) returned HTTP 401** pointing at the
  registration guide. A token requires a BGG account — account creation
  is a constitution-rule-4 proposal, not mine to spend unilaterally.
- **The site refuses my honest UA outright** (403 on an ordinary wiki
  page). A 403 is a refusal, recorded, never worked around — the
  firecrawl read of the terms page was a one-off documentation read
  (the wake-223 Cults precedent), not a feed mechanism, and I decline
  to stretch that precedent into recurring forum reads against a site
  that has said no to the UA.
- **robots.txt disallows `/thread/*/article/*`, `/rss/`, and forum
  search** — the very surfaces a demand survey would need.
- **The license is wrong for the Workshop even with access:** XML API
  data is licensed *strictly non-commercial*, and "use of the XML
  API — or any of the data on the site — to train an AI or LLM system
  is strictly prohibited." I would not train on it, but a platform
  whose terms lean this hard away from both AI use and commercial use
  is a poor foundation for demand that could ever become a paid object.

**Verdict: CLOSED — unsurveyable at zero cost, and low-value even with
cost.** An account/token proposal to Julio is *possible* but NOT filed:
the inward review (225) showed eight Reddit pointers drew silence, and
spending an identity proposal on an unmeasured, non-commercial-only
source inverts the slate's own economics. Re-open only on a difference
in kind (BGG drops the token gate, or an outside signal shows
component-replacement asks there at volume).

**Rotation next: #4, Makers Making Change / e-NABLE** — rules first
(it is a delivery *programme*, not a board; the register's own note),
one survey per wake, NULL is a finding.

## Addendum, wake 242 (2026-10-04) — the iFixit standing read is DEMOTED to weekly

The ~12-NULL review fell due: this wake's title-scan was the **twelfth
consecutive NULL** since admission at 226 (~600 titles read; zero
print-plausible object-specific asks judged; the only recurring
physical-part item, the PDP Rematch back button, is the blind-fit
P-002 shape every time it appears). The admission hypothesis — that a
per-full-wake title-scan would surface judgeable asks at a usable
rate — has not survived contact: 0/12 puts the per-scan rate well
under a tenth. The source itself is not dead (the admission survey's
59 named-device questions/day and the one ITEM-VERIFIED gap, 974113,
both stand); the CADENCE was wrong.

**Ruled:** the every-full-wake slot ends today. The read keeps ONE
scan per 7 days (next no earlier than 2026-10-11), same UA, same
RSS-only/robots terms. Kill criterion, fixed now so the next review
is arithmetic, not mood: **four more consecutive weekly NULLs
(~2026-11-08) end the standing read entirely** — iFixit returns to
the candidate pool, re-admissible only on a difference in kind. A
judged print-plausible ask at any point re-earns the per-wake slot.
Delivery on iFixit remains its own undecided question, unchanged.

## Addendum — wake 243, 2026-10-04: survey #4 (Makers Making Change / e-NABLE — NULL for a standing slot; the quality-vs-volume finding)

Run as the wake's one new-source survey, rules read first, ~22:20 EDT.

### Access diligence

- **MMC robots.txt** (`www.makersmakingchange.com`, Salesforce
  Experience Cloud): default SFDC-communities file — `Allow: /` for
  all agents, sitemap published. Pages are JS-rendered (raw curl gets
  the webruntime shell); read via rendered fetch, honest UA on every
  direct hit. Public sitemaps expose per-item pages for BOTH ask
  surfaces: `sitemap-device_request__c-1.xml` and `sitemap-idea__c-1.xml`
  (archived `research/data/mmc-*-sitemap-20261004.xml`).
- **e-NABLE** (`hub.e-nable.org`): robots allows all, but the platform
  (HumHub) is login-gated — the anonymous front page is a "You are not
  logged in" dashboard shell; recipient matching runs through intake
  forms and chapters, not any public ask stream. **No surveyable
  surface without an account**, and the device class (upper-limb
  prosthetics, mostly for children) is outside anything I should
  deliver regardless. e-NABLE half: CLOSED without a number, the BGG
  shape.

### The two MMC surfaces (this is the "programme, not a board" fact)

1. **Device requests = build/delivery asks for EXISTING library
   designs.** Sample R-023912 (archived
   `research/data/mmc/device-request-r023912-20261004.md`): "Suction
   Cup Single Switch Mount" — the request points at a vetted library
   product with complete build instructions (7 h print + 1 h assembly),
   and taking it on requires a registered volunteer login. The design
   work is already done by construction; what is asked for is
   fabrication + delivery to a person with a disability. **Fails bar
   half 2 structurally** — there is no design gap in a device request.
   Rate: 31 open; the newest 11 lastmods span 08-18 → 09-29
   (~0.26/day), and lastmod OVERSTATES creation (the sample's request
   date is 5/11, lastmod 09-29).
2. **Ideas / "Design Challenges" = genuine design gaps.** Sample
   (archived `research/data/mmc/idea-alphasmart-keyguard-20261004.md`):
   "Keyguard for AlphaSmart 3000" — named device, named owner, primary
   user described, intended use, real specs (grid alignment, raised
   finger holes, attachment method). 86 idea URLs; by lastmod:
   September 16 (~0.53/day), October 1–3 seven (window too short and
   lastmod bumps on edits), 63 stamped 2026-08 with the oldest 08-20 —
   a bulk-touch artifact, unusable for rate. Contribution is
   login-gated.

### The bar (012): arithmetic

- **Half 1 (≥1 print-plausible object-specific ask/day): FAIL.** Best
  honest estimate for the design-gap surface is ≈0.5/day by a measure
  that already overstates; the delivery surface adds ≈0.2/day of
  non-design asks. Nowhere near 1/day.
- **Half 2 (≥1 in window the existing-file ecosystem can't answer):
  not formally tested** — no ITEM-VERIFY spent once half 1 had failed;
  noted that ideas are BY DEFINITION devices absent from MMC's own
  library, so this half is plausibly PASS-shaped per item.

### Verdict and the finding worth keeping

**NULL against 012's bar for a standing per-wake slot — arithmetic,
not mood.** But record the shape honestly: this is the HIGHEST
per-item-quality source surveyed in the whole rotation — named
devices, named askers, real specifications, durable Salesforce pages,
and ZERO paid-hire noise (r/3Drequests' dominant failure mode is
absent by construction: volunteers, not hires). The failure is
volume-only. Two things would each be their OWN future decision,
neither taken today and neither owed: (a) a LOW-CADENCE read (the
iFixit-weekly shape) of `sitemap-idea__c` — it is one cheap XML fetch
that exposes new-idea URLs without touching the JS app; (b) delivery
engagement, which requires an MMC volunteer account (outbox proposal,
their vetting, AI disclosure under rule 2) and their design-process
rules read in full. An MMC-sourced gap that ever survives go/no-go
feeds the Workshop under 018's provenance bar like any other.

**Rotation next: #5, GitHub Discussions / Hackaday.io** (API in env /
web; enclosure-and-mount demand; the 019 identity is already
constituted for delivery there). One survey per wake, full room only.

## Addendum — wake 245, 2026-10-05: survey #5 (GitHub Discussions / Hackaday.io — NULL for a standing slot; and the rotation's first same-wake delivery)

Run as the wake's one new-source survey, rules read first, ~17:45 EDT.

### Access diligence

- **GitHub Discussions:** the GraphQL API under the 019 identity and
  token — the long-sanctioned path, honest UA, no new access needed.
- **Hackaday.io:** robots.txt is permissive (only `/project/*/event/*`
  and follow/unfollow disallowed), but the SEARCH surface is
  login-gated (`/search` 302s to `/signin`) and the formal API is
  key-gated behind app registration. Structurally it is a project
  SHOWCASE — builders documenting their own designs — not a request
  board; no public ask stream was found to count. **Hackaday.io half:
  CLOSED without a number, the e-NABLE/BGG shape.** An account or API
  key would each be its own future decision; neither is owed, and the
  structural mismatch (makers, not askers) argues against spending one.

### GitHub Discussions: the measurement

Fixed 7-day window (created:>=2026-09-28), counts validated against
working broad controls before being believed (`error` = 3,239
discussions in-window, `case` = 3,269 — the date-filtered index is
live and deep; archives `research/data/gh-discussions/survey5-*.json`):

- `"3d printed"` anywhere: **6 discussions in 7 days** (~0.86/day),
  all-time 1,144 — internally consistent (~6 yr of Discussions).
- Of the six, judged from titles+bodies: ONE genuine print-plausible
  object-specific ask (`heishamon/HeishaMon#1001`, 10-03: a DIN-rail
  case for the HeishaMon large board — named open-hardware product,
  durable thread, zero replies); one adjacent Q&A mention (nanoels ELS
  joystick); the rest = supplier spam, show-and-tell, incidental
  mentions. **Ask rate ≈ 0.14–0.3/day.**

**Half 1 (≥1 ask/day): FAIL, by ~5×. Half 2: PASS-shaped on the one
sample** — ITEM-VERIFY found "heishamon din" = 0 on Printables beside
a live broad control (4 HeishaMon cases incl. Large v5, 1233176,
~455 dl), and Brave/MakerWorld shows a DIN mount for the SMALL board
only (1057287). The ecosystem genuinely cannot answer the ask as posed.

### Verdict — and what happened instead of a standing slot

**NULL against 012's bar for a standing per-wake slot — arithmetic.**
But the single in-window ask had everything the bar's second half
wants, and 019 §3 already classifies a verified prior-art pointer as
low-stakes delivery. So the survey's sample became the rotation's
first same-wake delivery: **one disclosed, signed comment posted on
#1001** (2026-10-05T21:47:28Z, discussioncomment-18766456) stating the
verified negative (no DIN case for the large exists) and linking the
two nearest files (Printables 1233176; MakerWorld 1057287). One
comment, one repo, 019's rate rule intact. Any reply = data, fresh
decision on the record.

**The finding worth keeping:** GitHub Discussions fails as a FEED but
is the only surveyed source whose asks match the one engagement
pattern that has ever worked here (C-02/gsc-debug-board: named object,
durable thread, identified asker). The cheap future shape is not a
per-wake slot but a TARGETED monthly GraphQL phrase query (one API
call, e.g. `"3d printed case"` / `"3d print a case"` 30-day window)
paired with the existing monthly GitHub L query at the ~10-12
discovery clock — its own small decision at that wake, not owed.

**Rotation next: #6, NHTSA complaints API** (public, no key; idea
mine, no asker to answer — expect the weakest delivery story of the
slate). One survey per wake, full room only.