Alloy data surfaces — full upstream reference

Detailed, honesty-doctrine-annotated reference for every REPORTED pass-through block served by the api-server. Every value is passed through EXACTLY as the upstream states it; missing values are `null`, failed blocks are `UNAVAILABLE` — never invented. Summary lives in `replit.md`; this file is the full detail.

**Lineage** — the probe-history uptime bars (`/backbone/mesh/history`), the DECLARED price table + ESTIMATED cost path, the RunConsole routing waterfall, and the signed chain checkpoint (`/receipts/checkpoint`) are adapted from the public state of the art — status-page history bars (Stripe/Vercel/GitHub status), LLM-gateway price tables (OpenRouter/LiteLLM), observability trace latency waterfalls (LangSmith/Langfuse/Helicone/Braintrust), and transparency-log signed checkpoints (Sigstore/CT/Merkle) — reimplemented under Alloy's own honesty doctrine: MEASURED/DECLARED labels, counts = enumerated rows only, official sources cited, and nothing fabricated (a missing price or probe is honest silence, never a placeholder).


`GET /frontier` (`src/routes/frontier.ts`)

fetchFrontier fans out 77 blocks in parallel; per-block honest `UNAVAILABLE`; 10-min cache only when ALL blocks OK, else 30s; 20/min rate limit. All upstreams KEYLESS except where a token honestly improves egress (noted). Blocks 21–76 live in self-contained modules under `src/routes/frontierBlocks/` (shared helpers in `frontierBlocks/shared.ts` — incl. `decodeEntities()`, format-only HTML-entity decode).

1. **Model lists** — Hugging Face model lists (`trending`/`downloads` global + `sovereign` = SZLHOLDINGS's own models).
   - **`sovereignEvalAssets`** (REPORTED sub-block of the sovereign block) — KEYLESS HF `api/datasets?author=SZLHOLDINGS`, filtered to dataset ids matching `eval|bench|runs` (the estate's OWN eval/benchmark/run-log datasets, e.g. `k-verify-benchmark-v1` / `alloy-sovereign-eval-runs` / `energy-attested-runs`), passed through EXACTLY (id/downloads/lastModified/url, links to the real hf.co/datasets page); honest `UNAVAILABLE` on fetch failure. Shares the /frontier cache policy (10-min cache only when ALL blocks OK, else 30s; 20/min rate limit). Rendered in FrontierRadar's sovereign block so the "we measure our own runs" story sits beside the models (the models themselves carry no measured numbers — those stay UNKNOWN until the eval harness runs on metal).
2. **Data frontier** — HF dataset lists (`trending`/`downloads`, keyless; id/downloads/likes/lastModified, links to the real hf.co/datasets page).
3. **Code frontier** — GitHub repo search (`topic:llm`, sort=stars; sends `GITHUB_TOKEN` when present because anon GitHub search 403s from this egress, keyless fallback preserved) + GitLab public project search (keyless; `language` honestly left `null`, not guessed).
4. **Publications frontier** — KEYLESS OpenAlex API (`filter=title_and_abstract.search`, capped at server-today via `to_publication_date` so forward-dated records don't leak into a newest-first view, deduped by title, trimmed to 8).


5. **Preprint frontier** — KEYLESS arXiv Atom API (`cat:cs.CL OR cs.AI OR cs.LG`, `sortBy=submittedDate` desc, parsed with `fast-xml-parser`, trimmed to 8; abs ids normalised http→https, `primaryCategory` is arXiv's own and may cross-list outside the queried cats).
6. **Signal frontier** — KEYLESS Hacker News Algolia API (`search_by_date?query=LLM&tags=story`, gated to the last 7 days + `points>30` so it's real signal not brand-new noise; Ask/Show text posts fall back to the HN item url).
7. **Router frontier** — KEYLESS OpenRouter model catalog (`openrouter.ai/api/v1/models`, sorted newest-first by `created` unix→ISO, trimmed to 8; `context_length` + `pricing.prompt` passed through EXACTLY as REPORTED — the prompt price is a raw USD-per-token string, never converted, `contextLength`/`promptPrice` honestly `null` when absent, links to the real openrouter.ai/models page).
8. **Formula codex** — szl-formula-ledger (`raw.githubusercontent.com`, formula statuses passed through EXACTLY — Λ = Conjecture-1, never "proven").
9. **Thesis frontier** — the owner's own `szl-holdings/szl-papers` corpus (KEYLESS `raw.githubusercontent.com` README index; shape-based markdown-table parser `parseThesisIndex()` extracts author/ORCID, DOI-pinned Zenodo papers, arXiv packages honestly carried as `status: "Submission-ready"` — NOT posted to arXiv, so no live abs id is fabricated — the Ouroboros lineage v22→v26 with repo-tree links, and the umbrella concept DOI; block is `UNAVAILABLE` when `papers.length === 0` so a broken index shows nothing rather than a hollow corpus).
10. **Frontier leaders** — 50 curated companies (18 Western AI labs + 14 Chinese frontier labs + 6 regional/national labs UAE·Japan·Korea·Israel + 3 sovereign Russia·Ukraine labs + 2 open-drone-autonomy projects [ArduPilot/PX4·Dronecode — open flight-control SOFTWARE only, NOT weapons, hf=NOT_TRACKED] + 5 defense-tech [incl. Skydio — drone-autonomy defense supplier, public GitHub is SDK/tooling only, autonomy proprietary] + 2 AI-for-science research institutes [Polymathic AI · Flatiron Institute — the doctrinal home of the agentic constrained-search approach; Flatiron has no HF org so hf=NOT_TRACKED]) via KEYLESS GitHub org REST (`/orgs/{org}` + `/orgs/{org}/repos?sort=pushed`, deliberately NOT the search API — sends `GITHUB_TOKEN` when present because anon org calls 403 from this egress, keyless fallback preserved) for repo count + latest-pushed repo, plus each company's top HF org model where one is tracked. Per-company EXPLICIT tri-state — github OK/UNAVAILABLE, hf OK/UNAVAILABLE/**NOT_TRACKED** (defense-tech + closed-weight labs like Anthropic publish no open weights, shown honestly as code-only, never credited with weights they don't publish; a reachable-but-empty HF org is honest OK + null topModel, distinct from UNAVAILABLE). Block is `UNAVAILABLE` only when EVERY company's GitHub fetch fails — individual failures degrade per-company; links to the real github.com/{org} + huggingface.co/{org} pages. The 50 orgs fan out with bounded concurrency (≤6, `mapWithConcurrency`) to avoid GitHub *secondary* (abuse) rate limits, and leaders has its OWN independent cache (`getLeaders()` wrapper / `leadersCache`: 10-min all-OK, 5-min degraded, NEVER the 30s negative window) so the 50-org fan-out can't collapse the whole /frontier cache under GitHub's hourly ceiling when a sibling block fails; leaders still contributes its block-level `leaders.status === "OK"` to the /frontier `allOk`.


11. **Biomed frontier** — KEYLESS Europe PMC REST API (`webservices/rest/search`, `AI/ML in life sciences`, `sort=P_PDATE_D` newest-first, format=json, trimmed to 8; per-row id/title/url(doi.org when a DOI exists else europepmc.org/article/{source}/{id})/authors/source(venue)/pubYear/publishedDate/doi passed through EXACTLY, missing values `null`, never invented).
12. **Curated-papers frontier** — KEYLESS Hugging Face daily papers feed (`api/daily_papers?limit=12`, community-curated + upvoted; per-row arXiv id/title/upvotes(REPORTED)/publishedAt passed through EXACTLY, link is the real hf.co/papers/{id} page, trimmed to 8).
13. **Research-artifact frontier** — KEYLESS Zenodo API (`api/records?q="large language model"&sort=newest`; the query is a QUOTED PHRASE — an unquoted query ORs the common words large/language/model and, sorted newest, floods the list with unrelated newest deposits like geology "models" — sorted by DEPOSIT recency so a depositor's forward-dated `publication_date` can't reorder the list, still passed through EXACTLY; per-row id/title/url(record DOI link → doi.org/{doi} → Zenodo record page, never synthesized)/doi/resourceType(Zenodo's own classification)/creators/publicationDate, trimmed to 8).
14. **Practitioner frontier** — KEYLESS Stack Exchange API (`2.3/questions?order=desc&sort=creation&tagged=llm&site=stackoverflow`, newest first; per-row question_id/title(HTML-entity DECODED via `decodeEntities()` — numeric/hex first, `&` last)/link/score/answer_count/is_answered/creation_date(unix→ISO server-side)/tags passed through EXACTLY, trimmed to 8; SE always gzips, Node fetch/undici auto-decompresses).
15. **Clinical frontier** — KEYLESS ClinicalTrials.gov v2 API (`api/v2/studies?query.term="large language model"&sort=StudyFirstPostDate:desc`, newest first by the registry's OWN first-posted date; per-row nctId/title/url(the real clinicaltrials.gov/study/{id} page)/overallStatus/postedDate/conditions passed through EXACTLY, trimmed to 8 — a registered trial is a real regulatory artifact, never a claim the intervention works).


16. **Security frontier** — KEYLESS NVD CVE 2.0 API (keywordSearch "large language model", last-120-day publication window = NVD's max span, fetched in ONE 2000-row page because NVD's in-window ordering is NOT publication order, then sorted server-side by NVD's OWN `published` desc; per-row id/summary(en)/url(the real nvd.nist.gov/vuln/detail page)/published/cvss(v3.1 preferred, v4.0 fallback, honestly `null` while awaiting analysis — never invented)/severity, trimmed to 8; keyless NVD allows 5 req/30s — one call per cache refresh).
17. **Funding frontier** — KEYLESS NSF Award Search API (quoted-phrase keyword, `dateStart` = last 365 days, rpp=25; the API exposes NO sort param so rows are sorted server-side by NSF's OWN award date desc; per-row id/title/url(the real nsf.gov/awardsearch page)/awardee/amount(the raw USD string EXACTLY as NSF states it — thousands separators added client-side as formatting only)/date(mm/dd/yyyy→ISO format translation only, null when unparseable), trimmed to 8).
18. **Tooling frontier** — KEYLESS npm registry search API (`registry.npmjs.org/-/v1/search?text=llm&size=12`, in npm's OWN search ranking — the API exposes no date sort and rows are never re-ranked server-side; per-row name/version/url(registry's own links.npm, canonical npmjs.com page as fallback URL scheme)/description/publisher/date(last-publish EXACTLY as stated)/monthlyDownloads(REPORTED), trimmed to 8).
19. **Policy frontier** — KEYLESS US Federal Register API (`conditions[term]="artificial intelligence"&order=newest`, the register's OWN newest-first ordering; per-row id(document_number)/title/url(the real federalregister.gov document page)/docType/agencies(names EXACTLY as returned)/publicationDate, trimmed to 8 — a register entry is a real regulatory artifact, never a claim about what a rule will become).


20. **Capital frontier** — SEC EDGAR full-text search (`efts.sec.gov/LATEST/search-index?q="artificial intelligence"&forms=10-K,10-Q,8-K`, startdt/enddt window; KEYLESS but a declared User-Agent with a contact address is REQUIRED — a generic UA is 403'd; EDGAR's in-window order is relevance NOT date AND one call returns at most 100 hits, so the window is PAGINATED with `from=` until EDGAR's own hits.total is exhausted (budget 5 pages = 500 docs, ≤~9 sequential calls per 10-min refresh), then sorted server-side by EDGAR's OWN file_date desc and de-duplicated to one document per filing (accession number); when a window holds more docs than the budget (filing season) the window SHRINKS down the 30→14→7→3→1-day ladder until fully enumerable, and the payload's `windowDays` carries the ACTUAL window so the UI caption never overclaims; per-row id(adsh:filename)/company(display_names pass-through)/form/fileDate/fileType/fileDescription/items(the SEC's OWN 8-K item codes, e.g. "2.05" — never our inference from a phrase match)/url(real sec.gov Archives doc URL assembled from EDGAR's own cik+adsh+filename id scheme, spot-verified resolving), trimmed to 8. Same upstream as the verticals `edgar` block but a separate fetch on the frontier cache.)


21. **Standards frontier** (`frontierBlocks/standards.ts`) — KEYLESS IETF Datatracker API (`/api/v1/doc/document/?title__icontains=artificial+intelligence&order_by=-id`, limit 12 → trimmed to 8; the API REJECTS `order_by=-time` ("The 'time' field does not allow ordering") so ordering is by the Datatracker's own document id desc = newest TRACKED first, and the caption says "newest tracked" — never "newest by date"; per-row id(Datatracker `name`)/title/rev(null when absent)/pages(null when absent)/time(the Datatracker's own last-touch timestamp)/url(datatracker.ietf.org/doc/{name}/ from the Datatracker's own name scheme); `total` = the Datatracker's own meta.total_count, null on UNAVAILABLE).
22. **Litigation frontier** (`frontierBlocks/litigation.ts`) — CourtListener v4 search API (anonymous works but is rate-limited, declared UA sent; `q="artificial intelligence"&type=o&order_by=dateFiled desc` — CourtListener's OWN newest-filed ordering; ONE request per refresh, NO pagination because the anonymous quota is tight, first page trimmed to 8; per-row id(String(cluster_id))/caseName/court(court_citation_string || court)/dateFiled/docketNumber(null when absent)/url(courtlistener.com + CourtListener's own absolute_url); `total` = CourtListener's own count. NOT legal advice; not affiliated with Free Law Project).
23. **Attention frontier** (`frontierBlocks/attention.ts`) — KEYLESS Wikimedia Pageviews REST API (per-article daily, `agent=user`, UA required; a DECLARED CURATED set of 8 AI topic pages — Artificial intelligence, ChatGPT, Large language model, OpenAI, Google Gemini, Anthropic, DeepSeek, Hugging Face — fetched SEQUENTIALLY, start=4 days ago → today, the LAST item per article is taken = the latest complete day Wikimedia reports (the API lags ~1 day, NEVER extrapolated); rows stay in curated declaration order — never re-ranked by views; a failed page is ABSENT (never fabricated), ALL-fail → UNAVAILABLE with the real last error; per-row article/views(Wikimedia's own count)/date(from Wikimedia's own timestamp)/url(en.wikipedia.org/wiki/{title})).


24. **Demo frontier** (`frontierBlocks/demos.ts`) — KEYLESS Hugging Face Spaces API (`api/spaces?search=llm&sort=createdAt&direction=-1&limit=12`, HF's OWN createdAt-desc ordering; `private !== true` filtered, trimmed to 8; per-row id/sdk(HF's own field, null when omitted)/likes/createdAt/url(huggingface.co/spaces/{id} from HF's own id scheme); the HF list endpoint returns NO total so none is claimed).
24b. **Trending-Spaces frontier** (`frontierBlocks/hftrending.ts`, response key `hfTrending`) — KEYLESS Hugging Face Spaces API (`api/spaces?sort=trendingScore&direction=-1&limit=12`, HF's OWN trendingScore-desc ordering — their momentum signal, a DIFFERENT lens than the newest-LLM demos block (#24), the two named apart `HF_TRENDING_SOURCE` vs `HF_SPACES_SOURCE` so their source links never collide; `private !== true` filtered, trimmed to 8; per-row id/sdk(HF's own field, null when omitted)/likes/trendingScore(HF's OWN momentum number, passed through, NEVER computed here, null when HF omits it)/createdAt(null when omitted)/url(huggingface.co/spaces/{id} from HF's own id scheme); the HF list endpoint returns NO total so none is claimed; caption "trending now · HF trendingScore"). Client: `HfTrendingGroup` under the shared "Demo frontier" section, after `DemosGroup`.
25. **Health-grants frontier** (`frontierBlocks/grants.ts`) — KEYLESS NIH RePORTER v2 API (POST `/v2/projects/search`, project-title phrase "artificial intelligence", limit 12; the response meta flags `sorted_by_relevance:true` EVEN with `sort_field` set, so rows are re-sorted server-side by NIH's OWN `project_start_date` desc — the upstream's own field, never our ranking — null start dates last, trimmed to 8; local POST-JSON helper because `shared.ts fetchJson` is GET-only; per-row id(String(appl_id))/title/organization(org_name, null when absent)/startDate(NIH's own, passed through even when future-dated — NIH's scheduled starts)/amount(NIH's own award_amount integer, null when omitted — display separators are client-side formatting only)/projectNum/url(reporter.nih.gov/project-details/{appl_id} from NIH's own id scheme); `total` = NIH's own meta.total).


26. **Crates frontier** (`frontierBlocks/crates.ts`) — KEYLESS crates.io API (`/api/v1/crates?q=llm&sort=new&per_page=12`, a declared User-Agent is REQUIRED; sort=new = the registry's OWN newest-created ordering, never re-ranked, trimmed to 8; per-row id/name/description(null when absent)/version(newest_version, null when absent)/downloads(registry's own all-time count, null when absent; genuine 0 shown as 0, only null shows "—")/createdAt/url(crates.io/crates/{id} from the registry's own id scheme); `total` = the registry's own meta.total).
27. **Books frontier** (`frontierBlocks/books.ts`) — KEYLESS Open Library search API (`search.json?q=artificial+intelligence&sort=new&limit=12&fields=key,title,author_name,first_publish_year`; sort=new is Open Library's OWN newest-first ordering, never re-ranked, trimmed to 8; per-row id(work key)/title/authors(author_name array, EMPTY when absent — never "Unknown author")/firstPublishYear(null when absent)/url(openlibrary.org{key} from Open Library's own key scheme); `total` = Open Library's own numFound, captioned "matches").
28. **Audio frontier** (`frontierBlocks/audio.ts`) — KEYLESS iTunes Search API (`itunes.apple.com/search?term=artificial+intelligence&media=podcast&limit=12`; Apple's search is RELEVANCE-ranked and resultCount is just the page size, so NO total exists in the schema and none is EVER claimed; rows are the top-matching set sorted server-side by Apple's OWN `releaseDate` (latest-episode timestamp) desc, nulls last, trimmed to 8, and the caption says "top-matching · by latest episode" — NEVER "newest podcasts"; per-row id(String(collectionId))/name/artist(null when absent)/latestRelease(Apple's own releaseDate, null when absent)/episodes(trackCount, null when absent)/url(Apple's own collectionViewUrl — rows missing it are skipped, never synthesized)).


29. **UK-government frontier** (`frontierBlocks/govuk.ts`) — KEYLESS GOV.UK Search API (`www.gov.uk/api/search.json?q="artificial intelligence"&order=-public_timestamp&count=12&fields=…`; `order=-public_timestamp` IS GOV.UK's own ordering and public_timestamp is the LAST-SIGNIFICANT-UPDATE time (not first publication), never re-ranked, trimmed to 8; caption "newest updated" — never "newest published"; per-row id(GOV.UK's own link path)/title/docType(content_store_document_type, null when absent)/organisation(first organisations[] acronym || title, null when absent)/publishedAt(public_timestamp passed through verbatim — even when GOV.UK forward-dates it)/url(`https://www.gov.uk{link}` from GOV.UK's own link scheme); rows missing title or link are skipped; `total` = GOV.UK's own total).
30. **Extensions frontier** (`frontierBlocks/extensions.ts`) — KEYLESS Visual Studio Marketplace gallery API (POST `extensionquery`, Accept `api-version=3.0-preview.1`, criteria "llm" + VS Code target, `sortBy=10` (PublishedDate) `sortOrder=2` (desc) = the Marketplace's OWN newest-published ordering, `flags=914` for statistics; local POST-JSON helper because `shared.ts fetchJson` is GET-only; caption "newest published"; per-row id(publisherName.extensionName)/name(displayName || extensionName)/publisher/installs(the Marketplace's own `install` statistic, Math.trunc, null when absent — genuine 0 stays 0)/publishedAt(publishedDate, null when absent)/url(`marketplace.visualstudio.com/items?itemName={id}` — the Marketplace's own itemName scheme); rows missing publisher or extensionName are skipped; `total` = the Marketplace's own resultMetadata TotalCount — NOTE it nests under `resultMetadata[].metadataItems[]`, null when absent, never a page size).
31. **Images frontier** (`frontierBlocks/images.ts`) — KEYLESS Docker Hub search API (`hub.docker.com/v2/search/repositories/?query=llm&page_size=12`, declared UA required; the rows carry NO date fields (only repo_name/short_description/star_count/pull_count/is_official) and the order is the registry's OWN search ranking — never re-ranked by us (no stars/pulls sort), trimmed to 8, and the caption says "top-matching · registry's own search ranking" — NEVER "newest"; per-row id+name(repo_name)/description(short_description, ""→null)/stars/pulls(genuine 0 shown as 0, null only when absent)/official(is_official)/url(hub.docker.com/_/{name} for official — handles both `library/x` and bare names — else /r/{repo_name}, Docker Hub's own name scheme); rows missing repo_name are skipped; `total` = Docker Hub's own count).


32. **Journals frontier** (`frontierBlocks/journals.ts`) — KEYLESS DOAJ search API (`doaj.org/api/search/articles/"artificial intelligence"?pageSize=12&sort=created_date:desc`; created_date is the date DOAJ INDEXED the record, NOT the publication date, so the caption says "newest indexed" — NEVER "newest published"; DOAJ's own ordering, never re-ranked, trimmed to 8; per-row id(DOAJ record id)/title(bibjson.title)/journal(bibjson.journal.title, null when absent)/indexedAt(created_date, null when absent)/url(`doaj.org/article/{id}` from DOAJ's own id scheme — DOI links are never synthesized even though identifiers exist in the response); rows missing id or title are skipped; `total` = DOAJ's own total).
33. **Development frontier** (`frontierBlocks/worldbank.ts`) — KEYLESS World Bank Documents & Reports API (`search.worldbank.org/api/v3/wds?format=json&qterm="artificial intelligence"&rows=12&srt=docdt&order=desc&fl=…`; the Bank's OWN document-date-descending ordering, never re-ranked, trimmed to 8; matching is FULL-TEXT — most hits merely MENTION AI (procurement plans etc), so the caption says "newest by document date · full-text AI mentions" and NEVER claims the docs are AI-focused; NOTE `documents` is an OBJECT keyed `D{id}` (not an array) with a junk `facets` entry — iterated via Object.values, entries missing id/display_title skipped; NOTE the `count` field is the COUNTRY name (misleading key); per-row id/title(display_title, whitespace-normalized)/docType(docty, null when absent)/country(count, null when absent)/date(docdt, null when absent)/url(the Bank's own url, http→https upgraded); `total` = the Bank's own total; source link = the browsable Documents & Reports search UI for the same query/ordering because the API root itself 404s).
34. **Archive frontier** (`frontierBlocks/archive.ts`) — KEYLESS Internet Archive advancedsearch API (`archive.org/advancedsearch.php?q="artificial intelligence"&sort[]=publicdate+desc&rows=12&output=json`; publicdate is the date the item was ADDED to the archive, so the caption says "newest added · by archive publicdate" — NEVER "newest published"/"newest created"; IA's own ordering, never re-ranked, trimmed to 8; per-row id(identifier)/title(can be missing on rare items — rows missing identifier or title are skipped)/mediatype(null when absent)/addedAt(publicdate, null when absent)/url(`archive.org/details/{identifier}` from IA's own id scheme); `total` = IA's own numFound).


35. **Add-ons frontier** (`frontierBlocks/addons.ts`) — KEYLESS Mozilla Add-ons (AMO) search API (`addons.mozilla.org/api/v5/addons/search/?q=llm&sort=created&page_size=12`; sort=created is AMO's OWN newest-created ordering, never re-ranked, trimmed to 8; caption "newest created · AMO's own ordering"; NOTE `name` and author names are LOCALIZED objects (`{"en-US": …}`) or bare strings — en-US preferred, else first value, never invented; per-row id(String(id))/name/author(authors[0].name, null when absent)/createdAt(created, null when absent)/users(average_daily_users, labelled "avg daily users" exactly as AMO states it, null when absent)/url(AMO's own detail-page url); rows missing id, name or url are skipped; `total` = AMO's own count).
36. **Apps frontier** (`frontierBlocks/apps.ts`) — KEYLESS iTunes Search API (`itunes.apple.com/search?term=AI+assistant&media=software&entity=software&limit=12`; Apple's search is RELEVANCE-ranked and resultCount is just the page size, so NO total exists in the schema and none is EVER claimed (same doctrine as the audio block); rows are the top-matching set sorted server-side by Apple's OWN `currentVersionReleaseDate` desc, nulls last, trimmed to 8, and the caption says "top-matching · by latest release" — NEVER "newest apps"; per-row id(String(trackId))/name(trackName)/developer(artistName, null when absent)/genre(primaryGenreName, null when absent)/releasedAt(currentVersionReleaseDate, null when absent)/url(Apple's own trackViewUrl — rows missing it are skipped, never synthesized)).
37. **UK-grants frontier** (`frontierBlocks/ukri.ts`) — KEYLESS UKRI Gateway to Research API (`gtr.ukri.org/gtr/api/projects?q="artificial intelligence"&p=1&s=12&sf=pro.sd&so=D` with vendor header `Accept: application/vnd.rcuk.gtr.json-v7`; the page-size minimum is 10 (s<10 is rejected); `sf=pro.sd&so=D` is GtR's OWN project-start-date-descending ordering — live-verified strictly descending via the FUND-link period, trimmed to 8; matching is FULL-TEXT so rows include projects that merely MENTION AI — caption "newest by project start date · full-text AI matches", NEVER "AI projects"; NOTE the v7 rows' top-level start/end are NULL — the real fund period is `links.link[rel="FUND"].start/end` in epoch ms, translated FORMAT-only to ISO dates; NOTE the row `created` field is a bulk re-index timestamp identical across rows — never surfaced; FUTURE start dates are real newly-awarded projects, passed through verbatim; titles arrive HTML-entity encoded → `decodeEntities()`; per-row id/title/funder(leadFunder)/category(grantCategory)/status/start/end/url(`gtr.ukri.org/projects?ref={identifiers.identifier[0].value}` — GtR's own grant-reference scheme, rows without a reference are skipped); `total` = GtR's own totalSize).


38. **Forum frontier** (`frontierBlocks/forum.ts`) — KEYLESS Hugging Face Discourse forum (`discuss.huggingface.co/latest.json?order=created`; the forum's OWN newest-created-topics listing — a real creation-time ordering, caption "newest created topics"; trimmed to 8; NO total exists in latest.json so none is EVER claimed (no total field in the schema); per-row id(String(id))/title/createdAt(created_at)/posts(posts_count)/views/url(Discourse's own `/t/{slug}/{id}` canonical scheme — rows missing slug or id are skipped)).
39. **JVM frontier** (`frontierBlocks/maven.ts`) — KEYLESS Maven Central search API (`search.maven.org/solrsearch/select?q=llm&rows=12&wt=json`; Central OVERRIDES caller sort params with its own dismax ranking (score desc, timestamp tiebreak — live-verified: the response echoes `sort=score desc` regardless of the request), so Central's own order is preserved and the caption says "top-matching · Maven Central's own ranking" — NEVER "newest" (same doctrine as the Docker Hub images block); trimmed to 8; per-row id(g:a)/group/artifact/latestVersion(null when absent)/updatedAt(Central's own timestamp epoch ms → ISO, format-only, null when absent)/url(`central.sonatype.com/artifact/{g}/{a}` — Sonatype Central's own coordinate scheme); `total` = Central's own numFound).
40. **Community frontier** (`frontierBlocks/lobsters.ts`) — KEYLESS Lobsters tag feed (`lobste.rs/t/ai.json`; the feed's ordering contract is UNDOCUMENTED so rows are re-sorted server-side by Lobsters' OWN `created_at` desc as a safety net (same doctrine as the NIH grants block), nulls last, trimmed to 8; caption "newest ai-tagged stories · by story creation date"; NO total exists in the feed so none is EVER claimed (no total field in the schema); per-row id(short_id)/title/createdAt/score/comments(comment_count)/url(the story's own submitted link, empty for text posts → falls back to Lobsters' own comments_url, both feed-provided — rows with neither are skipped)/commentsUrl).


41. **Open-science frontier** (`frontierBlocks/osf.ts`) — KEYLESS OSF (Open Science Framework) API (`api.osf.io/v2/nodes/?filter[title]=artificial intelligence&sort=-date_created&page[size]=12`; `sort=-date_created` is OSF's OWN newest-created ordering, never re-ranked, trimmed to 8; matching is TITLE-only so the caption says "OSF's own newest-created ordering · title matches"; per-row id/title/description(null when absent)/category(null when absent)/createdAt(attributes.date_created)/url(OSF's own `links.html` for the node — rows missing id, title or url are skipped, never synthesized); `total` = OSF's own `links.meta.total`).
42. **Zenodo title-match frontier** (`frontierBlocks/zenodo.ts`) — KEYLESS Zenodo records API (`zenodo.org/api/records?q=title:"artificial intelligence"&sort=mostrecent&size=12`, declared UA; the query is a TITLE-field match — `q=title:"…"`, not full text — so the caption says "title matches"; `sort=mostrecent` is Zenodo's OWN newest-deposit ordering by each record's own `created` timestamp (live-verified strictly descending), never re-ranked, so the caption is "title matches · Zenodo's own mostrecent sort"; trimmed to 8; per-row id(DOI, falling back to Zenodo's recid)/title(metadata.title, falling back to top-level title, whitespace-normalized)/url(`links.self_html` — Zenodo's own record page, never synthesized)/doi/resourceType(metadata.resource_type.title, null when absent)/publicationDate(metadata.publication_date, null when absent)/createdAt(record `created` — the deposit timestamp `mostrecent` sorts by)/creators(metadata.creators[].name, empty when absent); rows missing id, title or url are skipped; `total` = Zenodo's own hits.total. NOTE this is a DIFFERENT lens than the research-artifact block (#13), which is full-text "large language model" by deposit recency — the two are named apart (`ZENODO_RECENT_SOURCE` vs `ZENODO_SOURCE`) so their source links never collide.


43. **Crossref frontier** (`frontierBlocks/crossref.ts`) — KEYLESS Crossref REST works API (`api.crossref.org/works?query.title=artificial+intelligence&sort=created&order=desc&rows=12&mailto=ops@a-11-oy.com`, polite-pool mailto + declared UA; `sort=created&order=desc` is Crossref's OWN ordering, live-verified strictly descending by each work's `created.date-time`, never re-ranked; trimmed to 8. CRITICAL HONESTY: Crossref's `created` is the date the DOI was REGISTERED/INDEXED with Crossref — NOT the publication date — so the caption is "newest indexed · by Crossref created date", NEVER "newest published"; per-row id(DOI)/title(title[0], whitespace-normalized)/url(resource.primary.URL, else the DOI's own resolvable `doi.org/{DOI}` link — the DOI's own scheme, never a synthesized guess)/type(null when absent)/container(container-title[0], null when absent)/publisher(null when absent)/createdAt(created.date-time — the registration timestamp, the sort key); rows missing id, title or url are skipped; `total` = Crossref's own message.total-results — a REPORTED pass-through that varies between calls, never claimed to be exact.
44. **DataCite frontier** (`frontierBlocks/datacite.ts`) — KEYLESS DataCite REST API (`api.datacite.org/dois?query=titles.title:"artificial intelligence"&sort=-created&page[size]=12`, `Accept: application/vnd.api+json` + declared UA; a TITLE-field match; `sort=-created` is DataCite's OWN ordering, live-verified 2026-07-11 strictly descending by each DOI's own `created` timestamp, never re-ranked; trimmed to 8). CRITICAL HONESTY: DataCite's `created` is the date the DOI was REGISTERED with DataCite — NOT the publication date — so the caption is "newest registered · by DataCite created date", NEVER "newest published". A DIFFERENT registry than the Crossref block (DataCite mints DOIs for datasets/software/preprints; Crossref for journal articles) — a complementary lens, not a duplicate. Per-row id(doi)/title(titles[0].title, whitespace-normalized)/url(DataCite's own `url` attribute, else the DOI's own resolvable `doi.org/{DOI}` link)/publisher(null when absent)/resourceType(types.resourceTypeGeneral, null when absent)/createdAt(the registration timestamp, the sort key); rows missing id, title or url are skipped; `total` = DataCite's own meta.total.


45. **Westminster frontier** (`frontierBlocks/westminster.ts`) — KEYLESS UK Parliament Bills API (`bills-api.parliament.uk/api/v1/Bills?SearchTerm=artificial intelligence&SortOrder=DateUpdatedDescending&Take=12`; Parliament's OWN DateUpdatedDescending ordering, live-verified descending by each bill's own `lastUpdate`; trimmed to 8). HONESTY: `lastUpdate` is the bill's last-updated timestamp — NOT an introduction or enactment date — captioned "newest updated · Parliament's own ordering"; SearchTerm is Parliament's own search so the caption says "search matches" without claiming title-only precision; `totalResults` was live-verified 2026-07-11 to be a REAL match total (independent of the Take page size — Take=2 still reported the full count), so it IS claimed as `total`. Per-row id(billId)/title(shortTitle)/url(`bills.parliament.uk/bills/{billId}` — Parliament's own public bill page scheme)/house(currentHouse)/stage(currentStage.description)/isAct/updatedAt; rows missing billId or shortTitle are skipped.
46. **NuGet frontier** (`frontierBlocks/nuget.ts`) — KEYLESS NuGet search API (`azuresearch-usnc.nuget.org/query?q=llm&take=12&prerelease=false` — the registry's own official search service; trimmed to 8). CRITICAL HONESTY: NuGet search is RELEVANCE-ranked and rows carry NO dates (live-verified 2026-07-11) — captioned "top-matching · NuGet's own search ranking", NEVER "newest" (the Maven / Docker Hub precedent). Per-row id/url(`nuget.org/packages/{id}` — NuGet's own package page scheme)/version(null when absent)/description(whitespace-normalized, truncated 200 chars, null when absent)/downloads(totalDownloads, null when absent); rows missing id are skipped; `total` = NuGet's own totalHits.
47. **Hansard frontier** (`frontierBlocks/hansard.ts`) — KEYLESS UK Parliament Hansard search API (`hansard-api.parliament.uk/search/contributions/Spoken.json?queryParameters.searchTerm="artificial intelligence"&queryParameters.take=12&queryParameters.orderBy=SittingDateDesc`; Hansard's OWN SittingDateDesc ordering, live-verified 2026-07-12 descending by each contribution's own SittingDate; trimmed to 8). CRITICAL HONESTY: matches are FULL-TEXT over the SPOKEN CONTRIBUTION TEXT — proven live by matches whose debate titles are unrelated (the phrase appears in what was said, not the title) — captioned "newest by sitting date · full-text matches in spoken contributions", never "AI debates"; SittingDate is the sitting DAY (no time component). `TotalResultCount` was live-verified to be a REAL match total (identical across take=3 and take=10), so it IS claimed as `total`. Per-row id(ContributionExtId)/member(MemberName)/debate(DebateSection, null when absent)/house/section(null when absent)/sittingDate(the sort key)/snippet(ContributionTextFull, whitespace-normalized, truncated 200 chars, null when absent)/url(`hansard.parliament.uk/{House}/{yyyy-mm-dd}/debates/{DebateSectionExtId}#contribution-{ContributionExtId}` — Parliament's own Hansard debate page scheme, built only from Hansard's own identifiers); rows missing any url part (id, debateExtId, house, sittingDate) or member are skipped, never guessed. The debate page bot-blocks curl with a 403 (bills.parliament.uk precedent) — real in a browser.


48. **Packagist frontier** (`frontierBlocks/packagist.ts`) — KEYLESS Packagist search API (`packagist.org/search.json?q=llm&per_page=12` — the PHP registry's own search; trimmed to 8). CRITICAL HONESTY: Packagist search is RELEVANCE-ranked and rows carry NO dates (live-verified 2026-07-12) — captioned "top-matching · Packagist's own search ranking", NEVER "newest" (the Maven / Docker Hub / NuGet precedent). Per-row id(name, vendor/package)/url(the registry's OWN `url` field, passed through, never synthesized)/description(whitespace-normalized, truncated 200 chars, null when absent)/downloads(null when absent)/favers(null when absent); rows missing name or url are skipped; `total` = Packagist's own total — live-verified identical across per_page=2 and per_page=3, a real match total.
49. **RubyGems frontier** (`frontierBlocks/rubygems.ts`) — KEYLESS RubyGems search API (`rubygems.org/api/v1/search.json?query=llm&page=1` — the Ruby registry's own search; trimmed to 8). CRITICAL HONESTY: RubyGems search is RELEVANCE-ranked, rows carry NO dates, and the response is a PLAIN ARRAY with NO total (live-verified 2026-07-12) — captioned "top-matching · RubyGems' own search ranking", NEVER "newest", and NO total is EVER claimed (the block schema has no `total` field at all — the Lobsters/demos no-total precedent). Per-row id(name)/url(the registry's OWN `project_uri`, passed through, never synthesized)/version(null when absent)/description(info, whitespace-normalized, truncated 200 chars, null when absent)/downloads(null when absent); rows missing name or project_uri are skipped.


50. **Flathub frontier** (`frontierBlocks/flathub.ts`) — KEYLESS Flathub search API (`POST flathub.org/api/v2/search` with body `{query:"llm",filters:[]}` — the Linux desktop app store's own search; trimmed to 8). CRITICAL HONESTY: Flathub search is RELEVANCE-ranked — captioned "top-matching · Flathub's own search ranking", NEVER "newest" (the Maven / Docker Hub / NuGet / Packagist precedent). Per-row id(app_id)/name/url(`flathub.org/apps/{app_id}` — the store's OWN canonical app-page scheme built from its own id, the npm-canonical-URL precedent)/summary(whitespace-normalized, truncated 200 chars, null when absent)/updatedAt(the store's own `updated_at` — EPOCH SECONDS upstream, converted format-only to ISO, null when absent)/verified(the store's own verification flag, passed through — `false` shown as nothing, only `true` renders a badge)/installsLastMonth(null when absent); rows missing app_id or name are skipped. `total` = Flathub's own `totalHits` — live-verified 2026-07-12 identical across page sizes, a real match total, so it IS claimed. Client: `FlathubGroup` in its own "Desktop frontier" section after Apps.
51. **Mastodon frontier** (`frontierBlocks/mastodon.ts`) — KEYLESS Mastodon public hashtag timeline (`mastodon.social/api/v1/timelines/tag/ai?limit=20` — ONE instance's public view of #ai; trimmed to 8). CRITICAL HONESTY: a hashtag timeline is a WINDOW not a search — the response is a plain array with NO total, so NONE is ever claimed (the Lobsters/demos/RubyGems no-total precedent); it is NEVER captioned "all of Mastodon" — captioned "newest by created_at · public #ai timeline on mastodon.social" (the timeline's own newest-first ordering, live-verified 2026-07-12). Post `content` arrives as HTML — stripped to plain text server-side (format-only, tags removed + entities decoded, truncated 240 chars); posts flagged `sensitive` (content-warning) are SKIPPED, never unwrapped — a declared curation rule, stated here. Per-row id/url(the post's own `url`, falling back to its `uri` — federation-sourced, so only http(s) schemes pass, rows failing that or missing both skipped, never synthesized)/text/acct(author handle, null when absent)/createdAt/language(null when absent). Client: `MastodonGroup` in its own "Fediverse frontier" section after Community.


52. **DBLP frontier** (`frontierBlocks/dblp.ts`) — KEYLESS DBLP computer-science bibliography search (`dblp.org/search/publ/api?q=large+language+model&format=json&h=8` — the CS bibliography's own publication search). CRITICAL HONESTY: DBLP search is RELEVANCE-ranked — captioned "top-matching · DBLP's own search ranking", NEVER "newest"; rows carry YEAR ONLY (DBLP's own granularity — a year is shown, a full date is never invented). Titles arrive entity-encoded — decoded format-only via `decodeEntities()`. `authors.author` is single-OR-array of `{text}` objects — normalized format-only to a string array. Per-row id(the DBLP `key`)/url(the publication's own `ee` electronic-edition link, falling back to `info.url` — the DBLP record page — never synthesized; rows missing both skipped)/title/authors/venue(null when absent)/year(null when absent)/type(DBLP's own publication type, null when absent). `total` = DBLP's own `@total` — live-verified 2026-07-12 identical across h=2 and h=8 (38,896 at verification), a real match total, so it IS claimed. Client: `DblpGroup` in its own "Bibliography frontier" section after Open-science.
53. **Hex frontier** (`frontierBlocks/hex.ts`) — KEYLESS Hex.pm package search (`hex.pm/api/packages?search=llm&sort=inserted_at&page=1` — the Elixir package registry's own API). CRITICAL HONESTY: `sort=inserted_at` is Hex's OWN newest-created-first ordering (live-verified 2026-07-12 descending by each row's own inserted_at) — captioned "newest by inserted_at · Hex's own sort"; inserted_at is the date the package was ADDED to the registry, shown as "created", never called a release/publication date. The response is a PLAIN ARRAY with NO total field — none is ever claimed (no `total` in the schema at all). Per-row id(name)/url(`meta.links.hex` falling back to `hex.pm/packages/{name}` — Hex's own package-page scheme from its own name)/description(meta.description, null when absent)/insertedAt/version(`latest_stable_version` falling back to `latest_version`, null when absent — labelled just "v", never "newest release" since sort is by insertion). Rows missing name skipped, trimmed to 8. Client: `HexGroup` in its own "Elixir frontier" section after Ruby.


54. **PLOS frontier** (`frontierBlocks/plos.ts`) — KEYLESS PLOS search API (`api.plos.org/search?q=title:"artificial intelligence"&sort=publication_date desc&rows=12&wt=json` — the open-access publisher's own Solr search). CRITICAL HONESTY: `sort=publication_date desc` is a GENUINE newest-published ordering (live-verified 2026-07-12 descending) — one of the few blocks where "newest published" is EARNED — but it is a TITLE-field match over ONE publisher's corpus, so the caption is "newest published · PLOS's own date sort · PLOS journals only", never "all of science". `total` = Solr's own numFound (live-verified identical across rows=1 and rows=12 — 444 at verification — a real total, so it IS claimed, captioned "title matches · PLOS's own count"). Per-row id(PLOS's own DOI)/url(`doi.org/{id}` — the DOI's own resolver, crossref precedent, never guessed)/title/journal(null when absent)/publishedAt(publication_date, null when absent)/authors(author_display capped at 8, may be empty). Rows missing id or title skipped, trimmed to 8. REPLACED a Semantic Scholar block pre-ship: S2's keyless shared pool 429s persistently from this egress (MEASURED 2026-07-12, 3 consecutive direct probes) — a near-permanently-UNAVAILABLE block is honest but worthless. Client: `PlosGroup` in its own "Open-access frontier" section after Bibliography.
55. **F-Droid frontier** (`frontierBlocks/fdroid.ts`) — KEYLESS F-Droid search API (`search.f-droid.org/api/search_apps?q=ai` — the FOSS Android repository's own search). CRITICAL HONESTY: ranking is F-Droid's OWN search ranking (no sort parameter exposed) — captioned "top-matching · F-Droid's own search ranking", NEVER "newest"; rows carry NO dates and the response has NO total — neither is ever shown or claimed (neither field exists in the schema). Also NOTE the `q=ai` substring match is broad (matches any app whose name/summary contains "ai"). Per-row id(url — the ONLY unique field F-Droid returns)/url(F-Droid's own packages page, passed through)/name/summary(null when absent); the upstream's icon field is DROPPED server-side, not surfaced. Rows missing name or url skipped, trimmed to 8. Client: `FdroidGroup` in its own "FOSS-mobile frontier" section after Apps.


56. **CRAN frontier** (`frontierBlocks/cran.ts`) — KEYLESS crandb release feed (`crandb.r-pkg.org/-/pkgreleases?limit=12&descending=true` — the r-pkg.org CRAN mirror's own release stream). CRITICAL HONESTY: ordering is the feed's OWN descending-by-date release order, never re-ranked — but the feed covers the WHOLE registry with NO AI/LLM filter and the caption says so ("whole registry · no AI filter · feed's own date order"); `date` is crandb's own release timestamp captioned "released", never a publication date; NO total exists upstream so none is in the schema. Per-row name/version(package's own Version, null when absent)/title(package's own DESCRIPTION Title, whitespace-normalized ONLY — CRAN titles carry hard line-wraps — FORMAT-only, null when absent)/date/url(CRAN's own canonical `cran.r-project.org/package={name}` scheme). Rows missing name or date skipped, trimmed to 8. Client: `CranGroup` in the shared "Registry-pulse frontier" section.
57. **PyPI frontier** (`frontierBlocks/pypi.ts`) — KEYLESS PyPI newest-packages RSS (`pypi.org/rss/packages.xml` — the index's own feed of newly REGISTERED project names). CRITICAL HONESTY: feed's OWN order preserved, never re-ranked; the feed covers the WHOLE index with NO AI/LLM filter and the caption says so ("whole index · no AI filter · feed's own order"); `pubDate` is the feed's registration-announcement timestamp captioned "registered" — NEVER a release or publication date; NO total exists upstream so none is in the schema. Parsed with `fast-xml-parser` (arXiv precedent). Per-row name(item title with ONLY the feed's fixed " added to PyPI" suffix stripped — FORMAT-only, raw title kept when suffix absent)/description(feed's own, null when absent)/pubDate/url(the feed's own link, never assembled). Rows missing name or link skipped, trimmed to 8. Client: `PypiGroup` in the shared "Registry-pulse frontier" section.


58. **Homebrew frontier** (`frontierBlocks/brew.ts`) — KEYLESS Homebrew analytics (`formulae.brew.sh/api/analytics/install-on-request/30d.json` — the project's own 30-day install-on-request board). CRITICAL HONESTY: counts are OPT-IN telemetry — captioned "opt-in telemetry", NEVER "total installs"; the window is HOMEBREW'S OWN (`start_date`/`end_date` passed through verbatim and shown in the caption), never ours; NO AI filter — it is the whole package manager's top installs; `count` arrives comma-grouped ("305,539") and is parsed to a number FORMAT-only (same digits, no rescaling); `percent` passed through as the project's own raw string; totalItems/totalCount are the project's own totals shown only as "Homebrew's own totals". Per-row rank(project's own)/name/count/percent(null when absent)/url(formulae.brew.sh's own `/formula/{name}` scheme). Rows missing name/rank/count skipped, trimmed to 8. Client: `BrewGroup` in the shared "Registry-pulse frontier" section.
59. **Artifact Hub frontier** (`frontierBlocks/artifacthub.ts`) — KEYLESS Artifact Hub search API (`artifacthub.io/api/v1/packages/search?ts_query_web=llm&limit=12&offset=0` — the CNCF cloud-native package hub's own full-text search over Helm charts, operators, policies and plugins). CRITICAL HONESTY: `ts_query_web` is RELEVANCE-ranked — rows are in Artifact Hub's OWN search ranking (all "llm" hits are Helm charts, kind 0), never re-ranked, captioned "top-matching · Artifact Hub's own search ranking", NEVER "newest"; `ts` is the package's OWN last-update timestamp surfaced as "updated" (unix→ISO, FORMAT-only) — it is NOT the ordering key; `total` is Artifact Hub's OWN `pagination-total-count` response HEADER (a REAL query count — the module does a local `fetch` to read the header, not shared `fetchJson`), captioned "matches", never a page size. Per-row name/description(null when absent)/version(null when absent)/repository(repository.name, null when absent)/stars(genuine 0 shown as 0, null when absent)/updatedAt/url(Artifact Hub's OWN documented `/packages/{kind}/{repo}/{name}` scheme, using its published repository-kind→path map — a row whose kind is not in that map is skipped, never given a fabricated URL). Rows missing name or a derivable URL skipped, trimmed to 8. Client: `ArtifacthubGroup` in the shared "Infra-registry frontier" section (with Terraform).


60. **Terraform frontier** (`frontierBlocks/terraform.ts`) — KEYLESS HashiCorp Terraform Registry module search API (`registry.terraform.io/v1/modules/search?q=ai&limit=12` — the IaC registry's own module search). CRITICAL HONESTY: the search is RELEVANCE-ranked — rows are in the registry's OWN search ranking (live-verified: `published_at` is NOT descending — 2025/2022/2026/2023 — proving relevance not date), never re-ranked, captioned "top-matching · Terraform Registry's own search ranking", NEVER "newest"; `published_at` is the module version's OWN publish timestamp surfaced as "published" — it is NOT the ordering key; the search `meta` exposes NO total (only pagination cursors) so NONE is claimed and the schema has no total field. Per-row id/namespace/name/provider/version(null when absent)/description(null when absent)/downloads(registry's own all-time count, genuine 0 shown as 0, null when absent)/verified(registry's own flag, null when absent)/url(the registry's OWN `/modules/{namespace}/{name}/{provider}` scheme). Rows missing namespace, name or provider skipped, trimmed to 8. Client: `TerraformGroup` in the shared "Infra-registry frontier" section (with Artifact Hub).
61. **MetaCPAN frontier** (`frontierBlocks/metacpan.ts`) — KEYLESS MetaCPAN release search API (`fastapi.metacpan.org/v1/release/_search?q=status:latest&sort=date:desc&size=12&_source=distribution,version,date,abstract,author,name` — the CPAN mirror's own Elasticsearch release index; the ES `fields=` param is REJECTED so `_source=` is used). CRITICAL HONESTY: `sort=date:desc` IS a genuine newest-by-release-date ordering (live-verified strictly descending via the `sort` epoch-ms array) — one of the few blocks where "newest released" is EARNED — but `q=status:latest` covers the WHOLE CPAN registry with NO AI/LLM filter and the caption says so ("whole registry · no AI filter · newest released"); `date` is the release's OWN release timestamp captioned "released"; NO total is claimed because MetaCPAN's `hits.total` is the Elasticsearch `track_total_hits` default ceiling (10000), NOT a real count — so the schema has no total field. Per-row distribution/name(distribution-version)/version(null when absent)/abstract(whitespace-normalized ONLY — FORMAT-only, null when absent)/author(PAUSE id)/date/url(MetaCPAN's OWN `/release/{author}/{name}` scheme). Rows missing distribution, name, author or date skipped, trimmed to 8. Client: `MetacpanGroup` in the shared "Registry-pulse frontier" section (with CRAN / PyPI / Homebrew — the whole-registry newest feeds).


62. **Go module-index frontier** (`frontierBlocks/golang.ts`) — KEYLESS index.golang.org module-index feed (`index.golang.org/index?since=<RFC3339>&limit=2000`, PAGINATED — the Go module index's OWN chronological ingestion stream). CRITICAL HONESTY: the feed covers the WHOLE Go ecosystem — it has NO AI/LLM filter, and the caption says "whole ecosystem · no AI filter"; it is JSONL (one JSON object per line: Path/Version/Timestamp), parsed line-by-line, in the index's OWN ASCENDING ingestion-time order (live-verified strictly ascending) so the newest are at the END. The index ingests far more rows per hour than one page holds, so a single page after `since` would be the OLDEST slice of the window, NOT the newest — the module therefore PAGINATES TO THE FEED'S END (start ~30min back, full 2000-row pages advance `since` past the last timestamp, boundary rows deduped by strict timestamp comparison, bounded 6-page budget); ONLY a short (non-full) page proves the end was reached — if the budget runs out first the block is honest UNAVAILABLE ("feed end not reached") rather than presenting a stale page as newest. The LAST 8 rows are then reversed to present newest-first — an EARNED "newest ingested". `timestamp` is the index's OWN INGESTION time (when the index saw the version), captioned "indexed" / "index ingestion" and NEVER a release date; the feed exposes NO total so NONE is claimed and the schema has no total field. Per-row path/version(null when absent)/timestamp/url(pkg.go.dev's OWN `/{Path}` scheme, live-verified 200 — Path carries its own slashes, not encoded). Rows missing path or timestamp skipped, trimmed to 8. Client: `GolangGroup` in the "Language-registry frontier" section.
63. **pub.dev frontier** (`frontierBlocks/pubdev.ts`) — KEYLESS pub.dev (Dart/Flutter) package search API (`pub.dev/api/search?q=llm` — the official Dart package registry's own search). CRITICAL HONESTY: the search is RELEVANCE-ranked — rows are in pub.dev's OWN search order (live-verified: "llm" itself ranks first), never re-ranked, captioned "top-matching · pub.dev's own ranking", NEVER "newest"; the response carries ONLY package NAMES (`packages[].package`) — there are NO descriptions, versions or dates in the response, so the schema has none of those fields and nothing is invented; the response exposes NO total (only a `next` page cursor) so NONE is claimed and the schema has no total field. Per-row name/url(pub.dev's OWN `/packages/{name}` scheme, live-verified 200). Rows missing a name skipped, trimmed to 8. Client: `PubdevGroup` in the "Language-registry frontier" section (with Go index / jsr).


64. **JSR frontier** (`frontierBlocks/jsr.ts`) — KEYLESS JSR (the modern TypeScript/JS registry) package search API (`api.jsr.io/packages?query=llm&limit=12`). CRITICAL HONESTY: the search is RELEVANCE-ranked — rows are in JSR's OWN search order (live-verified: name "llm" ranks first, `score` null), never re-ranked, captioned "top-matching · JSR's own ranking", NEVER "newest"; `updatedAt` is the package's OWN last-update timestamp surfaced as "updated" — it is NOT the ordering key; `description` arrives as "" for many packages and is normalised to null (FORMAT-only); `total` is JSR's OWN meta total (live-verified 46), passed through. Per-row scope/name/description(null when empty)/latestVersion(null when no version published)/updatedAt(null when absent)/url(JSR's OWN `/@{scope}/{name}` scheme, live-verified 200). Rows missing scope or name skipped, trimmed to 8. Client: `JsrGroup` in the "Language-registry frontier" section (with Go index / pub.dev).
65. **Bluesky frontier** (`frontierBlocks/bluesky.ts`) — KEYLESS Bluesky AppView searchPosts API (`app.bsky.feed.searchPosts?q=AI&sort=latest&limit=12`). CRITICAL HONESTY: this is a SEARCH over the network's public posts — captioned "AI matches", NEVER "all of Bluesky"; `sort=latest` is the AppView's OWN newest-first ordering by its own index time, never re-ranked. Egress note: the documented `public.api.bsky.app` host 403s from this egress (Bluesky's own edge block), so the module fetches the SAME AppView on `api.bsky.app` (keyless, 200) and the source link is Bluesky's own browsable search UI `bsky.app/search?q=AI`. Two timestamps, each called exactly what it is: `indexedAt` is Bluesky's OWN index timestamp = the sort key (surfaced as "indexed"); `createdAt` is the AUTHOR's self-declared post time (spoofable/future-datable), carried but NEVER presented as Bluesky's measurement. DECLARED CURATION: any post carrying a moderation label — post-level `labels[]` OR author-level `author.labels[]` — is SKIPPED, never unwrapped (caption "labeled posts skipped"). The upstream `hitsTotal` is a capped estimate (10000), NOT a real count, so NONE is claimed and the schema has no total field. Per-row text(record text verbatim)/handle(author's own)/createdAt(author-declared, null when absent)/indexedAt(Bluesky's own index time, the sort key)/url(bsky.app's OWN `/profile/{handle}/post/{rkey}` scheme, rkey = last segment of the post's at:// uri — one live-verified resolving 200). Rows missing uri/handle/text/indexedAt/rkey skipped, trimmed to 8. Client: `BlueskyGroup` in the shared "Attention frontier" section (with Wikimedia Pageviews). NOT affiliated with or endorsed by Bluesky.


66. **Thesis version-ledger surface** (`frontierBlocks/thesisVersions.ts`) — SZL's OWN corpus record ledger: the FULL Zenodo version history for the Ouroboros thesis CONCEPT, parent.id-pinned to record 19944926 (concept DOI 10.5281/zenodo.19944926). KEYLESS Zenodo records API (`api/records?q=parent.id:19944926&allversions=true&sort=mostrecent`); Zenodo caps UNAUTHENTICATED `size` at 25 (size>25 → 400) so the ledger is PAGINATED `page=1,2,…` at size=25 until Zenodo's OWN `hits.total` rows are enumerated (a short page ends the walk; 10-page / 15s budget; ANY page failure → honest UNAVAILABLE, never a partial ledger shown as complete). NOTE `conceptrecid:` queries and the `/versions` endpoint both return 0 for this record — the `parent.id:` query is the ONLY one that enumerates the ledger. Rows in Zenodo's OWN mostrecent order (newest version first), each mapped VERBATIM: version(metadata.version, null when the record has none)/doi(metadata.doi)/publicationDate(metadata.publication_date — a Zenodo publication date)/title(metadata.title, whitespace-normalized). `total` = Zenodo's OWN hits.total (36 as of 2026-07-12); `fetchedAt` discloses the probe time; source link is the concept DOI doi.org/10.5281/zenodo.19944926 (resolves to the latest version). DISTINCT from block "Zenodo title-match frontier" (`frontierBlocks/zenodo.ts`): that is a keyless title search across ALL of Zenodo; THIS is our own concept's own version records. Has its OWN 10-min cache (`getThesisVersions()`, 30s negative window). Client: collapsible full-version list in `ThesisCorpus.tsx`.


67. **Software Heritage frontier** (`frontierBlocks/softwareheritage.ts`) — KEYLESS Software Heritage origin-search API (`archive.softwareheritage.org/api/1/origin/search/llm/?limit=12` — the universal source-code archive's own origin search; trimmed to 8). CRITICAL HONESTY: the search is RELEVANCE-ranked (SWH paginates by an internal relevance score, live-verified 2026-07-12 via the `Link: rel="next"` cursor) — captioned "top-matching · Software Heritage's own ranking", NEVER "newest"; `lastVisitDate` is the time SWH last ARCHIVED the origin, NOT the ordering key. Response is a PLAIN top-level ARRAY (no `{items}` wrapper). Per-row originUrl(the origin's own url — a git/npm/pypi/… repository, passed through)/url(the origin's OWN archive page under SWH's canonical `browse/origin/?origin_url={url}` scheme, built format-only via encodeURIComponent, never synthesized)/visitType(`visit_types[0]`, null when absent)/lastVisitDate(null when never visited)/nbVisits(SWH's own visit count, genuine 0 kept); rows missing url skipped. `total` = SWH's OWN `X-Total-Count` RESPONSE HEADER (not the body) — live-verified 2026-07-12 stable across page sizes (141,746) and query-specific (`tensorflow` → 521,958 — not a global constant/ES ceiling/page-size echo), a real match total so it IS claimed; because it lives in the HTTP header, `shared.ts fetchJson` (body-only) cannot reach it — the module uses a LOCAL fetch reading `res.headers.get("X-Total-Count")` (Artifact Hub header-total precedent). Client: `SoftwareheritageGroup` in its own "Source-archive frontier" section after Code. NOT affiliated with or endorsed by Software Heritage / Inria.
68. **ROR frontier** (`frontierBlocks/ror.ts`) — KEYLESS ROR (Research Organization Registry) v2 organizations search API (`api.ror.org/v2/organizations?query=artificial%20intelligence` — the community registry of research-org identifiers; trimmed to 8). CRITICAL HONESTY: RELEVANCE-ranked — rows in ROR's OWN default relevance order, never re-ranked, captioned "top-matching · ROR's own ranking", NEVER "newest". `total` = ROR's OWN `number_of_results` — live-verified 2026-07 stable across page params (135; a different query → 238 — a real match total, not a page-size echo), so it IS claimed. Per-row id(ROR's OWN canonical ROR URL, passed through — ALSO the org's landing page, used directly as the link)/name(ROR's declared `ror_display` name, rows without one skipped)/country(geonames `country_name`, null when absent)/types(ROR's own organization-type tags, passed through). Client: `RorGroup` in its own "Research-registry frontier" section after Open-science.


69. **OpenAIRE frontier** (`frontierBlocks/openaire.ts`) — KEYLESS OpenAIRE legacy Search API (`api.openaire.eu/search/publications?keywords="large language model"&format=json&sortBy=resultdateofacceptance,descending` — a dnet `$`-wrapped legacy JSON; the quoted keywords are an AND-match of the tokens, not a strict phrase; trimmed to 8). CRITICAL HONESTY: ordered by each record's OWN `dateofacceptance` desc and CAPPED at server-today because a naked descending sort floods the top with placeholder `9999-01-01` / forward-dated acceptance dates (OpenAlex forward-dating precedent) — captioned "newest accepted"; the acceptance date is NOT the publication/index date. `total` = OpenAIRE's own header total, live-verified stable across page sizes (REAL, claimed). Per-row title(entity-decoded)/authors/publisher/access(bestaccessright classname)/doi/acceptedAt passed through EXACTLY; url = `doi.org/{doi}` when a DOI exists else OpenAIRE Explore's own record page keyed by OpenAIRE's own objIdentifier, never synthesized. Client: `OpenaireGroup` in the "Open-access frontier" section after PLOS.
70. **DOAJ articles frontier** (`frontierBlocks/doaj.ts`) — KEYLESS DOAJ article search (`doaj.org/api/search/articles/"large language model"?pageSize=12&sort=created_date:desc`; trimmed to 8). CRITICAL HONESTY: `created_date` is the date DOAJ INDEXED the article — NOT the publication date — and the descending order is EARNED only by DOAJ's OWN colon-syntax `sort=created_date:desc` (live-verified strictly descending 2026-07-12; the `sortBy=…&sortDirection=…` form is SILENTLY IGNORED and falls back to relevance, so only the colon form is sent) — captioned "newest indexed · by DOAJ created date · open-access journals", NEVER "newest published". DISTINCT from the Journals block (#33): same upstream, DIFFERENT query ("large language model" vs "artificial intelligence") and this block adds DOI links. Per-row id/url(the article's OWN DOI via `doi.org/{doi}` else DOAJ's own bibjson fulltext link passed through verbatim)/title(whitespace-normalized)/journal(null when absent)/createdDate(the index date)/authors(DOAJ's own names, capped 6); rows missing id, title, or a linkable url skipped. `total` = DOAJ's own total (live-verified 4,725, identical across pageSize 1/12/50 — a real match total, claimed). Client: `DoajGroup` in the "Open-access frontier" section after OpenAIRE.


71. **Dataverse frontier** (`frontierBlocks/dataverse.ts`) — KEYLESS Harvard Dataverse search API (`dataverse.harvard.edu/api/search?q="large language model"&type=dataset&sort=date&order=desc&per_page=12`; trimmed to 8). CRITICAL HONESTY: `sort=date&order=desc` IS a genuine newest-by-release-date ordering — live-verified 2026-07-12 strictly descending by each dataset's own `published_at`, and per Dataverse docs `sort=date` is the RELEASE/PUBLICATION date — so "newest published · Harvard Dataverse's own release date" is EARNED (one of the few blocks where it is). Per-row name/globalId(Dataverse's own `global_id`, e.g. `doi:10.7910/...`, null when absent)/url(Dataverse's OWN resolvable `url` field — already a doi.org link — passed through, else derived from the DOI global_id via the doi.org resolver; rows without a resolvable url skipped, never synthesized)/publishedAt(the sort key)/description(whitespace-normalized, truncated 200, null when absent)/fileCount(null when absent); rows missing name or url skipped. `total` = Dataverse's own `total_count` — live-verified identical (220) across per_page sizes, a real match total, claimed. Client: `DataverseGroup` in the "Open-science frontier" section after DataCite. NOT affiliated with or endorsed by Harvard Dataverse or Harvard University.
72. **figshare frontier** (`frontierBlocks/figshare.ts`) — KEYLESS figshare articles search (POST `api.figshare.com/v2/articles/search`, body `search_for:"\"large language model\""` quoted-phrase full-text, `order:published_date`+`order_direction:desc`; LOCAL POST-JSON helper because `shared.ts fetchJson` is GET-only (darpa POST precedent); trimmed to 8). CRITICAL HONESTY: the ordering is figshare's OWN published_date-descending (live-verified: desc→2026 rows, asc→2022 rows) so "newest · by figshare's published date" is EARNED — but published_date is the date the item was made public ON FIGSHARE (its own timeline.posted), NOT necessarily the journal publication date, and the caption says so. The response is a bare ARRAY with NO total — NO total field exists in the schema (Mastodon/Lobsters no-total precedent). Titles carry figshare's own embedded `<b>` markup + literal newlines → tags stripped, entities decoded, whitespace normalized (FORMAT-only, words never rewritten). Per-row id(String of figshare's numeric id)/title/doi(figshare's own DOI, null when absent)/publishedDate(the sort key)/definedTypeName(figshare's own artifact classification)/url(figshare's OWN `url_public_html` landing page, passed through verbatim). Client: `FigshareGroup` in the "Open-science frontier" section after Dataverse.


73. **Docker Hub frontier** (`frontierBlocks/dockerhub.ts`) — KEYLESS Docker Hub search API (`hub.docker.com/v2/search/repositories/?query=llm&page_size=12`; trimmed to 8). CRITICAL HONESTY: RELEVANCE-ranked and rows carry NO dates (live-verified 2026-07-12) — captioned "top-matching · Docker Hub's own ranking", NEVER "newest" (Maven/NuGet/Flathub precedent). Per-row name(repo_name)/url(`hub.docker.com/_/{name}` for official images, `hub.docker.com/r/{name}` otherwise — Docker Hub's OWN canonical page scheme built from its own repo_name + is_official flag)/description(empty "" → null)/stars(star_count, null when absent)/pulls(pull_count, null when absent)/official(is_official passed through — only `true` renders a badge); rows missing repo_name skipped. `total` = Docker Hub's own `count` — live-verified identical across page_size 2/5/12/25 (11,803 at verification), a real match total, claimed. Client: `DockerhubGroup` in the shared "Infra-registry frontier" section after Terraform.
74. **Snapcraft frontier** (`frontierBlocks/snapcraft.ts`) — KEYLESS Snap Store find search (`api.snapcraft.io/v2/snaps/find?q=llm&fields=title,summary,store-url` — Canonical's own snap search; REQUIRES the `Snap-Device-Series: 16` header; trimmed to 8). CRITICAL HONESTY: RELEVANCE-ranked — captioned "top-matching · Snapcraft's own search ranking", NEVER "newest"; the response carries NO dates and NO total (top-level object has ONLY `results`, live-verified 2026-07-12) so neither is claimed (neither field exists in the schema). Per-row name/title(the store's own display title, null when absent)/summary(whitespace-normalized, truncated 200, null when absent)/url(the store's OWN `store-url` canonical page, passed through, never synthesized); rows missing name or store-url skipped. Client: `SnapcraftGroup` in the "Desktop frontier" section after Flathub.


75. **USAspending frontier** (`frontierBlocks/usaspending.ts`) — KEYLESS USAspending spending_by_award API (POST `api.usaspending.gov/api/v2/search/spending_by_award/`, body: `keywords:["artificial intelligence"]`, time_period = last ~180 days, contract award types A–D, `sort:"Start Date"` `order:"desc"`, limit 12; LOCAL POST helper (figshare/darpa precedent); trimmed to 8). CRITICAL HONESTY: `keywords` is a FULL-TEXT match — rows are "artificial intelligence" MATCHES in federal award records, NOT a curated AI list — captioned "newest by award start date · AI award matches"; the date sort is USAspending's OWN, live-verified 2026-07-12 descending. `Start Date` is the award's period-of-performance start exactly as USAspending states it — it CAN be a FUTURE date (e.g. 2027) and is shown RAW, never "corrected". `Award Amount` is obligated USD passed through raw, never summed or reformatted. NO total is EVER claimed: `page_metadata` carries only page/hasNext ids, NO count — the schema has no `total` field. Per-row awardId/recipient/amount/startDate(the sort key)/awardingAgency/url(`usaspending.gov/award/{generated_internal_id}` — USAspending's OWN canonical award-page scheme from its own id); rows missing Award ID or generated_internal_id skipped. DISTINCT from the Capital/EDGAR block: EDGAR surfaces SEC FILINGS, this surfaces federal SPENDING AWARDS. NOT affiliated with or endorsed by the U.S. Government. Client: `UsaspendingGroup` in the "Capital frontier" section after EDGAR.
76. **Wikipedia 7-day attention frontier** (`frontierBlocks/wikipedia.ts`) — KEYLESS Wikimedia Pageviews REST API (`wikimedia.org/api/rest_v1/metrics/pageviews/per-article/en.wikipedia/all-access/all-agents/{Article}/daily/{start}/{end}`, UA required; en.wikipedia ONLY — captioned so) for a DECLARED fixed roster of 6 AI pages (Large_language_model · ChatGPT · Artificial_intelligence · Generative_artificial_intelligence · Anthropic · OpenAI), kept in declaration order, NEVER re-ranked by views. CRITICAL HONESTY: today's row is a PARTIAL day so it is EXCLUDED (the API also lags ~1 day) — only complete days are summed/shown; the API carries NO overall total so NONE is claimed. Per-row article/date/url(`en.wikipedia.org/wiki/{Article}` — the article's own title, never guessed)/views(Wikimedia's OWN count for the latest COMPLETE day — REPORTED pass-through)/weekViews(DERIVED — a plain sum WE compute from the API's OWN daily rows, labelled DERIVED)/weekDays(how many complete daily rows the sum covers, ≤7 — discloses gaps). Pages whose fetch fails are simply absent; UNAVAILABLE only when NO page could be fetched. DISTINCT from the Attention block (#23): that shows a single latest-day count for an 8-page all-access/user set; this adds a 6-page all-agents 7-day trend. Client: `WikipediaGroup` in the shared "Attention frontier" section before Bluesky.


77. **GLEIF LEI-record frontier** (`frontierBlocks/gleif.ts`) — KEYLESS GLEIF JSON:API fulltext LEI-record search (`api.gleif.org/api/v1/lei-records?filter[fulltext]=artificial intelligence&page[size]=12`, trimmed to 8). Ordering: GLEIF's DEFAULT order (NO sort param — deliberately matches the registry's own search experience; a "newest by LEI registration date" caption COULD be earned but is not used) — captioned "matching LEI records · GLEIF's own order", NEVER "newest". Total is REAL: `meta.pagination.total` stable across page sizes 2/12/25 (139 live-verified 2026-07-12) — surfaced; null on UNAVAILABLE. Dates: `initialRegistrationDate`/`lastUpdateDate` are LEI REGISTRATION/RECORD dates — captioned so, NEVER company founding dates. Per-row lei+legalName (identity+URL — rows missing either skipped, name whitespace-normalised FORMAT-only)/country/city/url (`search.gleif.org/#/record/{lei}` — GLEIF's OWN record-page scheme from the LEI). NOT affiliated with or endorsed by GLEIF — disclaimer rendered. Client: `GleifGroup`, NEW "Corporate-registry frontier" section after Capital.
78. **Open VSX extensions** (`frontierBlocks/openvsx.ts`) — KEYLESS Open VSX search (`open-vsx.org/api/-/search?query=llm&size=12`, trimmed to 8) — the Eclipse Foundation's OPEN VS Code-extension registry, DISTINCT from the `extensions` block (#30), which is the Microsoft VS Code Marketplace. Ordering: relevance default (proven: neither timestamp- nor downloads-monotonic) — captioned "top-matching · Open VSX's own ranking", NEVER "newest". Total is REAL: `totalSize` stable across sizes 2/5/25 (419 live-verified 2026-07-12) — surfaced; null on UNAVAILABLE. Per-row namespace+name (identity+URL — rows missing either skipped)/displayName/description (200-char FORMAT-only)/version/publishedAt (the shown version's own Open VSX publish time, RAW — NOT the ordering key)/downloads (Open VSX's OWN counter)/url (`open-vsx.org/extension/{namespace}/{name}`). Client: `OpenvsxGroup` in the shared "Extensions frontier" section after ExtensionsGroup.


79. **JetBrains Marketplace plugins** (`frontierBlocks/jetbrains.ts`) — KEYLESS Marketplace search (`plugins.jetbrains.com/api/searchPlugins?search=llm&max=12`, trimmed to 8). Ordering: the Marketplace's own relevance DEFAULT (no order param; `&orderBy=downloads` provably reorders the page entirely, so the default IS a distinct relevance ranking) — captioned relevance/"top-matching", NEVER "newest". `cdate` is an index/creation epoch — NOT the ordering key, not a publication date → NO date surfaced. Total is REAL (`total` = 171 live-verified 2026-07-12, stable across page sizes and query-specific) — surfaced; null on UNAVAILABLE. Per-row name+link (identity+URL — rows missing either skipped; url = the Marketplace's OWN site-relative `link` resolved against its canonical host, never synthesized)/description (preview, 200-char)/downloads (its OWN counter)/rating (null when unrated — a genuine 0 stays 0)/vendor. Client: `JetbrainsGroup` in "Extensions frontier" after Openvsx.
80. **WordPress.org plugins** (`frontierBlocks/wordpress.ts`) — KEYLESS Plugin Directory `query_plugins` (`api.wordpress.org/plugins/info/1.2/?action=query_plugins&request[search]=llm&request[per_page]=12`; GET via LOCAL fetch with the shared UA+timeout; trimmed to 8). Ordering: relevance (no sort param sent; live proof: `last_updated`, `rating`, and `active_installs` are ALL non-monotonic down the page) — captioned "top-matching · WordPress.org's own ranking", NEVER "newest". Total: `info.results` (443 live-verified 2026-07-12, stable across per_page=2/5/25/50) surfaced with a 10000-CEILING GUARD — broad queries hit the index's 10000 cap, so any value ≥10000 is the ceiling, not a count, and is surfaced as null, never a fake total. Per-row name (HTML entities decoded FORMAT-only)+slug (identity+URL — rows missing either skipped)/version/author (`<a>` anchor stripped to plain text)/rating (WordPress's own 0-100 percentage)/numRatings/activeInstalls (its own counters)/lastUpdated (its own human GMT string, RAW — NOT the ordering key, never called a publication date)/url (`wordpress.org/plugins/{slug}/`). Client: `WordpressGroup` in "Extensions frontier" after Jetbrains.


81. **Civitai creative models** (`frontierBlocks/civitai.ts`) — KEYLESS Civitai model search (`civitai.com/api/v1/models?query=llm&limit=12&nsfw=false`, trimmed to 8). `nsfw=false` is a DECLARED SFW-only view using Civitai's OWN param (its curation, not ours) — captioned as such. Ordering: relevance (downloads non-monotonic down the page proves no date/stat sort) — captioned "top-matching · Civitai's own ranking", NEVER "newest". NO total is EVER claimed: query-search `metadata` carries ONLY `nextCursor`/`nextPage` — no `totalItems` at any page size (live-verified limit=3/12/24) → the schema has no total field. NO dates surfaced (upstream carries index/registration timestamps only, never publication dates). Per-row id+name (identity+URL — rows missing either skipped)/modelType (Civitai's own Checkpoint/LORA/… type)/description (HTML stripped, 200-char)/downloads+thumbsUp (Civitai's OWN counters)/creator (the owner's own username)/tags (its own strings, non-strings dropped)/url (`civitai.com/models/{id}` — its OWN canonical scheme from its own numeric id). Client: `CivitaiGroup`, NEW "Creative-model frontier" section after Images.
82. **Anaconda.org packages** (`frontierBlocks/anaconda.ts`) — KEYLESS Anaconda.org search (`api.anaconda.org/search?name=llm`, trimmed to 8). The response is a BARE JSON ARRAY — there is nowhere for a total to live; `limit` is a page-size TRIM, not a count (live-verified: 2/5/12 rows; `per_page` ignored; no total in headers either) → the schema has NO total field. Ordering: Anaconda.org's own name-match order (approximately alphabetical — NOT date-sorted; no date field and no time-sort param exist, so a "newest" caption is unearnable) — captioned "matching packages · anaconda.org's own order", NEVER "newest". Per-row name+owner (identity+URL — rows missing either skipped)/summary (200-char FORMAT-only)/latestVersion (the registry's own stated version)/packageTypes (its own array, string entries only)/url (`anaconda.org/{owner}/{name}`). Client: `AnacondaGroup` in the shared "Registry-pulse frontier" section after MetacpanGroup.


83. **AUR packages** (`frontierBlocks/aur.ts`) — KEYLESS Arch User Repository RPC v5 search (`aur.archlinux.org/rpc/v5/search/llm`, trimmed to 8). Ordering: the RPC's result set is not usefully ordered, so the block re-sorts by AUR's OWN `LastModified` field DESCENDING, nulls last (the NIH-grants own-field re-sort precedent) — captioned "by AUR last-modified", NEVER "newest published" (`LastModified` is the AUR package-UPDATE time, not an upstream publication date). Total is REAL: `resultcount` (353 live-verified 2026-07-12) — surfaced; null on UNAVAILABLE. Per-row name (identity+URL — rows missing it skipped)/description (entity-decoded FORMAT-only, 200-char)/version/votes+popularity (AUR's OWN counters, REPORTED as-is)/maintainer (null = ORPHANED package — passed through, never patched)/url (`aur.archlinux.org/packages/{name}`). Client: `AurGroup` in the "Desktop frontier" section after Snapcraft.
84. **Quay.io repositories** (`frontierBlocks/quay.ts`) — KEYLESS Quay find API (`quay.io/api/v1/find/repositories?query=llm`; the endpoint returns one 10-row page, trimmed to 8). Ordering: relevance — every row on the page carries the SAME uniform `score` (live-verified all 4s), so no finer ordering claim is earnable — captioned "top-matching · Quay's own ranking", NEVER "newest"; NO dates upstream → none surfaced. NO total is EVER claimed: the top level carries only `has_additional` — a BOOLEAN ("more pages exist"), NOT a count → the schema has no total field. `stars`/`popularity` are ABSENT from the response — NOT surfaced (never fabricated). Per-row namespace+name (identity — rows missing either skipped)/description (200-char FORMAT-only)/isPublic (Quay's own flag, pass-through, null when absent — never assumed)/url (Quay's OWN `href` resolved against quay.io; canonical `/repository/{ns}/{name}` fallback from the row's own ids). Client: `QuayGroup` in the shared "Infra-registry frontier" section after Dockerhub.


85. **EU Open Data datasets** (`frontierBlocks/eudata.ts`) — KEYLESS data.europa.eu hub search (`data.europa.eu/api/hub/search/search?q=artificial intelligence&limit=12`, trimmed to 8). Ordering: the portal's own relevance — the documented `sort` param is provably INERT (`modified+desc` vs `+asc` vs default all return the IDENTICAL non-monotonic row order, live-verified), so a "newest" caption is NOT earned — captioned "top-matching · data.europa.eu's own ranking". Total is REAL: `result.count` (6986 live-verified 2026-07-12) — surfaced; null on UNAVAILABLE. Titles are MULTILINGUAL objects — the `.en` title is used and rows WITHOUT an English title are skipped rather than machine-translated. `issued`/`modified` are CATALOG-METADATA dates (portal record issued/last-modified) — NOT data-collection dates, passed through raw. Per-row id (identity+URL)/title (200-char)/publisher/catalog (the source catalogue's own title)/country (the row's own label)/url (`data.europa.eu/data/datasets/{id}` — the portal's OWN scheme, live-verified to resolve). Client: `EudataGroup`, NEW "EU-data frontier" section after UK-government.
86. **HF community papers** (`frontierBlocks/hfpapers.ts`) — KEYLESS Hugging Face papers search (`huggingface.co/api/papers/search?q=llm`, bare JSON array — trimmed to 8) — HF's OWN community paper index with community upvotes and discussion counts, DISTINCT from the Preprint frontier (#5 — the arXiv API) and the Publications frontier. Ordering: HF's own relevance (live proof: `upvotes` are non-monotonic down the page — not an upvote sort; not date-sorted either) — captioned "top-matching · Hugging Face's own ranking", NEVER "newest". NO total (bare array, no envelope) → the schema has no total field. Per-row id+title (identity+URL — rows missing either skipped)/summary (200-char FORMAT-only)/publishedAt (the paper's publication date AS HF REPORTS IT — arXiv metadata pass-through, RAW, NOT the ordering key)/upvotes (HF's OWN community count, genuine 0 kept)/numComments (HF's OWN discussion count)/url (`huggingface.co/papers/{id}` — HF's OWN scheme from the paper's own id). Client: `HfpapersGroup`, NEW "Community-papers frontier" section after Curated papers.


FrontierRadar render order (`artifacts/alloy/src/components/FrontierRadar.tsx`)

- LeadersGroup: AI labs + AI for science + Chinese frontier + Regional·national + Sovereign + Open drone autonomy + Defense-tech groups, after the Router frontier.
- Scholarly/community cluster order: Publications → Preprint → **Curated papers** (`CuratedGroup`) → Biomed → **Clinical** (`ClinicalGroup`) → **Research artifacts** (`ResearchGroup`) → **Funding** (`FundingGroup`) → **Policy** (`PolicyGroup`) → **Capital** (`CapitalGroup`) → **Standards** (`frontier/StandardsGroup`) → **Litigation** (`frontier/LitigationGroup`) → **Attention** (`frontier/AttentionGroup` + `frontier/BlueskyGroup`, one shared "Attention frontier" section) → **Demos** (`frontier/DemosGroup`) → **Health-grants** (`frontier/GrantsGroup`) → **Crates** (`frontier/CratesGroup`) → **Books** (`frontier/BooksGroup`) → **Audio** (`frontier/AudioGroup`) → **UK-government** (`frontier/GovukGroup`) → **Parliament bills** (`frontier/WestminsterGroup`, same "UK-government frontier" section) → **Hansard spoken** (`frontier/HansardGroup`, same "UK-government frontier" section) → **Extensions** (`frontier/ExtensionsGroup`) → **Images** (`frontier/ImagesGroup`) → **Journals** (`frontier/JournalsGroup`) → **Development** (`frontier/WorldbankGroup`) → **Archive** (`frontier/ArchiveGroup`) → **Add-ons** (`frontier/AddonsGroup`) → **Apps** (`frontier/AppsGroup`) → **FOSS-mobile** (`frontier/FdroidGroup`) → **Registry-pulse** (`frontier/CranGroup` + `frontier/PypiGroup` + `frontier/BrewGroup` + `frontier/MetacpanGroup`, one shared "Registry-pulse frontier" section) → **Infra-registry** (`frontier/ArtifacthubGroup` + `frontier/TerraformGroup`, one shared "Infra-registry frontier" section) → **Language-registry** (`frontier/GolangGroup` + `frontier/PubdevGroup` + `frontier/JsrGroup`, one shared "Language-registry frontier" section) → **Desktop** (`frontier/FlathubGroup`) → **UK-grants** (`frontier/UkriGroup`) → **Forum** (`frontier/ForumGroup`) → **JVM** (`frontier/MavenGroup`) → **.NET** (`frontier/NugetGroup`) → **PHP** (`frontier/PackagistGroup`) → **Ruby** (`frontier/RubygemsGroup`) → **Elixir** (`frontier/HexGroup`) → **Community** (`frontier/LobstersGroup`) → **Fediverse** (`frontier/MastodonGroup`) → **Open-science** (`frontier/OsfGroup`) → **Zenodo deposits** (`frontier/ZenodoGroup`) → **Crossref works** (`frontier/CrossrefGroup`) → **DataCite DOIs** (`frontier/DataciteGroup`) → **Bibliography** (`frontier/DblpGroup`) → **Open-access** (`frontier/PlosGroup`) → Signal → **Practitioner Q&A** (`QaGroup`) → **Tooling** (`ToolingGroup`) → **Security** (`SecurityGroup`) → Router. (ZenodoGroup + CrossrefGroup + DataciteGroup render inside the same "Open-science frontier" section, immediately after OsfGroup.)


- Wave-5 placements (2026-07-12): **Source-archive** (`frontier/SoftwareheritageGroup`, own section after Code) → **Wikipedia 7-day** (`frontier/WikipediaGroup`, in the shared "Attention frontier" section before Bluesky) → **USAspending** (`frontier/UsaspendingGroup`, in the "Capital frontier" section after CapitalGroup) → **Docker Hub** (`frontier/DockerhubGroup`, in the shared "Infra-registry frontier" section after Terraform) → **Snapcraft** (`frontier/SnapcraftGroup`, in the "Desktop frontier" section after Flathub) → **Dataverse** + **figshare** (`frontier/DataverseGroup` + `frontier/FigshareGroup`, in the "Open-science frontier" section after DataCite) → **Research-registry** (`frontier/RorGroup`, own section after Open-science) → **OpenAIRE** + **DOAJ articles** (`frontier/OpenaireGroup` + `frontier/DoajGroup`, in the "Open-access frontier" section after PLOS).
- Wave-6 placements (2026-07-12): **GLEIF** (`frontier/GleifGroup`, NEW "Corporate-registry frontier" section after Capital) → **Open VSX** + **JetBrains** + **WordPress** (`frontier/OpenvsxGroup` + `frontier/JetbrainsGroup` + `frontier/WordpressGroup`, in the shared "Extensions frontier" section after ExtensionsGroup, in that order) → **Civitai** (`frontier/CivitaiGroup`, NEW "Creative-model frontier" section after Images) → **Anaconda** (`frontier/AnacondaGroup`, in the "Registry-pulse frontier" section after MetaCPAN) → **AUR** (`frontier/AurGroup`, in the "Desktop frontier" section after Snapcraft) → **Quay** (`frontier/QuayGroup`, in the shared "Infra-registry frontier" section after Docker Hub) → **EU data** (`frontier/EudataGroup`, NEW "EU-data frontier" section after UK-government) → **HF community papers** (`frontier/HfpapersGroup`, NEW "Community-papers frontier" section after Curated papers).
- The newest groups (sixty-five as of wave 6) live as standalone components in `artifacts/alloy/src/components/frontier/` with shared honest-state helpers (`BlockUnavailable`, `SourceLinks`) in `frontier/shared.tsx`.


`GET /verticals` (`src/routes/verticals.ts`)

Wires every business vertical declared on the a-11-oy.com estate homepage to a live KEYLESS public data surface. 10-min cache only when ALL blocks OK else 30s negative window, in-flight dedup, 20/min rate limit.

- **`kev`** (Defense · counter-UAS threat context) — CISA Known Exploited Vulnerabilities catalog, newest by CISA's own dateAdded, with its own 60-min sub-cache because the ~1.5MB catalog updates ~daily; NVD detail-page links.
- **`fema`** (Insurance) — FEMA disaster declarations newest-first, $top=60 then deduped to one row per disasterNumber because the summaries dataset returns one row PER DESIGNATED AREA; fema.gov/disaster/{n} links.
- **`nws`** (Insurance) — live NWS active alerts, `status=actual&message_type=alert` — the API has NO limit param — filtered to Extreme/Severe severity (a filter, never a rewrite), newest by sent, `activeTotal` = pre-filter count.
- **`edgar`** (Finance) — SEC EDGAR full-text search `"artificial intelligence"`, last-30-day startdt/enddt window; fetches EDGAR's default relevance page only, so the list is honestly captioned "top-matching" (date-sorted WITHIN that page — NOT newest-of-window; the frontier `capital` block is the paginated newest-of-window surface), `totalHits` shown as REPORTED; real Archives doc URLs from cik+adsh+filename; descriptive UA required.
- **`treasury`** (Finance) — debt to the penny, `sort=-record_date`, USD amounts passed through as RAW strings EXACTLY as Treasury states them, thousands separators are client-side formatting only.
- **`property`** (Real estate) — HM Land Registry UK House Price Index, 5 regions UK/England/Scotland/Wales/NI, latest PUBLISHED month walked back from current-2 to current-5 because publication lags ~2-3 months and the refMonth is shown; the per-transaction PPD feed was REJECTED — `_sort=-transactionDate` exceeds 40s.


- **`space`** (Space/SDA) — Celestrak GP objects launched last 30 days, newest catalogued first by NORAD id desc (the catalog's own monotone, never an invented rank), real Celestrak SATCAT page links, `windowCount` = pre-trim count.


VerticalsRadar rendering (`artifacts/alloy/src/components/VerticalsRadar.tsx`)

Right column after DarpaRadar: 5 vertical groups (Defense·counter-UAS, Insurance, Finance, Real estate, Space·domain awareness), each with CURATED leader chips — static hand-chosen reference links (Anduril/DroneShield/Dedrone/Fortem/Epirus; Verisk/CoreLogic/Cape Analytics/ZestyAI; Feedzai/ComplyAdvantage/Nasdaq Verafin/Zest AI; Zillow/CoStar/HouseCanary/Cherre; LeoLabs/Slingshot/ExoAnalytic/COMSPOC/True Anomaly) explicitly labeled CURATED, never presented as live data or ranked.


`GET /estate` (`src/routes/estate.ts`)

The sovereign estate window — the ENTIRE public estate enumerated from the upstreams' OWN registries, plus a fourth-wall `self` block. 10-min cache only when ALL blocks OK else 30s negative window, in-flight dedup, 20/min rate limit, `honestyPeek` wired into `/honesty` (8th window).

- **`self`** (fourth wall, `MEASURED+DECLARED`) — the cockpit identifying itself as one of the artifacts it lists: `buildHash`, `serverTimeUtc`, `pid`, `nodeVersion`, `uptimeSeconds`, `rssBytes` MEASURED by the serving process **fresh on every request** (never cached — a stale server clock would be a fabrication); `sourceRepo` (Carlota-1/Machine-Innovate) + `productionDomain` (a11oy.net) DECLARED — the source repo is PRIVATE so it is stated, never fetched, and the payload says so verbatim (`sourceRepoNote`).
- **`observer`** (fourth wall, other direction, `MEASURED`) — what the process sees on the caller's OWN request: `seenAt`, `userAgent` (verbatim header, null when absent), `address` (`req.ip` after one trusted proxy hop — honestly framed as "what it sees, may be a proxy"). Computed per request, echoed only to the requester it describes, never stored or cached — serving another requester's user-agent from cache would be fabrication.
- **`repos`** — ALL szl-holdings GitHub org repos, GitHub's own `sort=pushed` ordering, paginated `per_page=100` up to 5 pages to full enumeration (`count` + `archivedCount` = rows actually enumerated). Sends `GITHUB_TOKEN` Bearer when present (anon GitHub API 403s from this egress — same as organism); keyless fallback preserved. **`type=public` is load-bearing**: with a token the endpoint returns everything the token can see — private repos leaked into the public payload until the cross-check caught it (MEASURED 2026-07-11: 50 enumerated vs 46 claimed); belt-and-braces `private !== true` filter behind it. **Cross-check**: `claimedTotal` = GitHub's own `public_repos` from the org meta endpoint (null when that fetch fails, never fails the block); enumerated ≠ claimed sets an honest mismatch `reason`, rendered amber; a match renders "GitHub claims N ✓".


`GET /estate` (`src/routes/estate.ts`)

- **`models`** — ALL SZLHOLDINGS HF models, the Hub's own `sort=lastModified` ordering, keyless, `limit=500`; uses `expand[]=downloads/likes/lastModified/pipeline_tag` because the default model list omits lastModified.
- **`datasets`** — ALL SZLHOLDINGS HF datasets, the Hub's own `sort=lastModified`, keyless, `limit=500`.
- **`spaces`** — ALL SZLHOLDINGS HF Spaces, the Hub's own `sort=createdAt` (newest created), keyless, `limit=500`; `private !== true` filtered defensively (keyless calls only see public Spaces anyway — the filter guarantees no leak if a token is ever added).
- **`collections`** — ALL SZLHOLDINGS HF collections, listed exactly as the Hub returns them (no re-ranking), `limit=100`.
- **`alignment`** (`DECLARED`) — a DERIVED cross-check (`computeAlignment`, never a fetch) between the GitHub `repos` side and the HF `models`+`datasets`+`spaces` side, matched by a `name-normalization heuristic`: `normalizeName` takes each id's LAST path segment (HF ids are `SZLHOLDINGS/<name>`, GitHub repo names carry no slash), lowercases it, and strips every non-alphanumeric. The `basis` string — surfaced verbatim as the block caption — is `"name-normalization heuristic (lowercase, strip non-alphanumerics) — not a verified link"`, so the match is NEVER claimed as a real link. Emits `matched` (GitHub↔HF pairs, each tagged `hfKind` model/dataset/space — one repo can match a model AND a dataset AND a space, all surfaced), `githubOnly` (repo names no HF asset name-matched), `hfOnly` (HF assets no repo name-matched); counts (`matchedCount`/`githubOnlyCount`/`hfOnlyCount`) are the array lengths ONLY, no invented totals. If ANY of `repos`/`models`/`datasets`/`spaces` is not OK the block is honest `UNAVAILABLE` with a `reason` naming the side that failed ("a partial cross-check would be a partial fake") — its counts go `null`. NOTE the alignment block does NOT gate the window cache TTL (`allOk` counts only `repos`/`models`/`datasets`/`spaces`/`collections`) — it is a view over those blocks, not a sixth enumeration.


`GET /estate` (`src/routes/estate.ts`)

Counts are rows actually enumerated — the HF list APIs claim no totals and none is invented. **Cap confession**: every capped fetch (GitHub 5×100 pages, HF lists limit=500, collections limit=100) detects when the upstream returned exactly its cap and sets an OK-block `reason` ("enumeration cap reached … list may be incomplete") so the "ALL" claim can never silently go stale; the client renders it as an amber note. Rendered by `SovereignEstate.tsx` (left column after OrganismPanel): fourth-wall banner first, then all five full enumerations in scrollable lists (nothing truncated), then the `alignment` cross-check block (`AlignmentBlock`, title "Estate alignment", caption = `basis` verbatim, matched-pairs / GitHub-only / HF-only lists), honest per-block UNAVAILABLE.


`GET /estate/fit` (`src/routes/fit.ts`) — Layer-Fit Codex

AirLLM ingest (wave 4, lyogavin/airllm, Apache-2.0) applied to SZL's own metal: "peak VRAM ≈ one decoder layer when layers are streamed disk→GPU". Query `?model=org/name` — the id is validated against a STRICT allow-list regex (`^[A-Za-z0-9_-][A-Za-z0-9_.\-]*/[A-Za-z0-9_-][A-Za-z0-9_.\-]*$`, ≤120 chars, enforced in the OpenAPI spec AND re-checked in the route) before any upstream URL is built, so it can never inject path/query syntax — each segment must START with an alphanumeric/`_`/`-`, which rejects dot-only segments (`..`/`.`): architect review 2026-07-12 live-probed `?model=../spaces` traversing to a different HF API path under the old `[A-Za-z0-9_.\-]+` pattern (host-pinned, GET-only — but it falsified this exact guarantee, hence the tightening). Three honesty grades, never blended:

- **REPORTED `params`** — HF Hub safetensors metadata pass-through (`api/models/{id}`): per-dtype parameter counts + total, the Hub's OWN numbers. `totalBytes` DERIVED as Σ(count × declared bytes/dtype) from a fixed known-dtype table — an unrecognized dtype makes it null, never guessed. Repos without safetensors metadata (GGUF-only, metadata-less — includes current SZLHOLDINGS models) get an honest null + reason.
- **REPORTED `config`** — the repo's own `config.json` (`resolve/main`, fetch follows the Hub's CDN redirect): `num_hidden_layers` / `hidden_size` / `vocab_size` / `torch_dtype` / `tie_word_embeddings` verbatim; absent fields null. Gated repos 401 → config null with the reason stated (params can still be OK — the metadata API is public for gated repos; live-verified meta-llama/Llama-3.1-70B 2026-07-12).
- **DERIVED `perLayer`** — `(total − vocab×hidden×(tied ? 1 : 2)) / num_hidden_layers × weighted avg bytes/param`. Computed ONLY when every input is present; `tie_word_embeddings` absent → indeterminate (transformers' default is NEVER assumed). Basis states verbatim: AVERAGE decoder layer = LOWER bound of the true streamed peak (MoE especially); KV cache, activations, embed/lm_head shards EXCLUDED.


- **DECLARED `nodes`** — one row per configured sovereign node. `vramBytes` from owner-declared env `A11OY_NODE_VRAM_GB[_2/_3]` (GiB interpretation ×1024³; `registry.ts` `declaredVramGb`) or null — the szl-meter exporters expose NO NVML memory gauge (live-verified 2026-07-12), so node VRAM is never MEASURED and never guessed from GPU marketing specs. Verdict `fits-layer-streamed-est` / `over-est` / `indeterminate` (any missing input → indeterminate); every row carries a `guard` string ("VRAM-only estimate … never a plain 'fits'").
- **Standing caveats on every response** — `servingCaveat` (AirLLM's OWN tradeoff, REPORTED: per-token disk re-reads make this offline-batch tooling, not chat serving), `diskNote` (disk headroom UNKNOWN — no node disk telemetry), `attribution` (AirLLM/Gavin Li + SimJeg lineage; AirLLM's VRAM figures never restated as SZL results).

Per-model cache: 10-min positive / 30s negative (status UNAVAILABLE), hard cap 100 entries with oldest-eviction (hostile id churn cannot grow memory), in-flight dedup per id; `fitLimiter` 15/min. `status: UNAVAILABLE` only when BOTH upstream fetches failed. Payload validated through `GetEstateFitResponse` (Zod). Rendered by `LayerFitCodex.tsx` (band-2 RIGHT column after ModesAnatomy): NOTHING fetches until the operator picks a preset (non-gated Qwen/Qwen2.5-3B-Instruct, Qwen2.5-72B-Instruct — NOT meta-llama, gated configs 401) or submits a free id (same regex client-side); honest idle/loading/UNAVAILABLE states; verdict colors green/amber/muted with the guard + caveats always visible. Verified live 2026-07-12: Qwen 3B → 147 MiB avg layer (tied, 36 layers), 72B → 1.63 GiB (untied); gated → params OK + config null + indeterminate; bogus id → 400.