Text version of this page

Tech Audit: 84 website mechanicals, measured

This is a plain-text copy of this page for readers and agents without JavaScript. Agents should start at /for-agents/, or read the site's plain-text index at /llms.txt.

Machine-readable access: the MCP endpoint at /api/mcp (JSON-RPC 2.0 over HTTP, read-only, no authentication), the OpenAPI description at /openapi.json, and the capabilities manifest at /agents.json.

Futurum mechanicals — trial.futurumgroup.com

Futurum mechanicals

trial.futurumgroup.com · probed 2026-11-19 10:49 UTC · probe 1.0.3 · pack mechanicals@2026.09.0 · supersedes the 2026-09-24 readout

A guide for the team, not a public page. This audit is for the Futurum web team, the TFG and Polaris people, and analysts who want to see how the new site is built and where it stands. It is removed before launch.

The deterministic floor: 84 checks that are either correct or not, that nobody has to have an opinion about. This is the current readout for the new build, measured on trial.futurumgroup.com — what is shipped and working, and the one thing left. Every line carries its own evidence. Both sites were probed within seconds of each other.

84measurable mechanicals a 2026 website needs

futurumgroup.com today

45

New build cutover day

78

45 → 7814 → 0 failing

Overview Capabilities What changed Shipped Left to go Security Publish Cutover to-do

A 2026 website has at least

84

measurable mechanicals that decide whether search engines, answer engines and AI agents can find it, quote it and use it.

The new build passes 78 of 84 by cutover, up from 45 today, with zero failures. Every check carries its own evidence.

45

working on futurumgroup.com today

14 failing outright

→

78

working on the new build on cutover day: 71 today, plus 7 that switch on at cutover

0 failing

Show how the 84 are counted

futurumgroup.comlive today

45

9

14

4

12

New buildtrial.futurumgroup.com

71

7

6

0of all 84 mechanicals84

working held for cutover (analytics, pixels, Search Console, MCP registry listing) partial failing not applicable can't be verified (no access to WordPress source)

72vs84

A higher ceiling. A WordPress site can only be scored on the 72 checks anyone can run from its URL. The new build can be held to all 84: 12 more, because every surface (llms.txt, sitemaps, the MCP server, feeds, .well-known) is a generated route in its source code, so it can be proven rather than hoped. The new build passes all 12.

+26 mechanicals ahead today · +33 on cutover day · 14 → 0 failures · +12 checks only the new build can prove

Where all 84 stand on the new build

78 of the 78 that apply, on cutover day

71

7

6

71

Working today 59 public checks + all 12 repo checks. The live site's repo can't be scanned, so the comparison above counts its 12 as unverifiable.

7

Switch on at cutover, by decision GA4 · Tag Manager · Google Ads · Reddit pixel · Meta pixel · Search Console · the public MCP registry listing (it must name futurumgroup.com, so it can't be listed from trial)

6

Not scored, and not gaps

4 don't apply to this site: language variants (one language); OAuth login metadata (the MCP server is deliberately open); an alternative analytics tool (GA4 is the plan); www-vs-apex host (trial has no www host)

1 this tool can't measure: a WebMCP hint (needs a real browser)

1 optional, skipped: humans.txt

One of those 6 turns into a real check at cutover: www.futurumgroup.com must 301 to the apex, as the live site already does. It is on the README cutover checklist (PR #64), with the MCP registry listing.

The 72 public checks, check by check (hover a dot for its check id)

futurumgroup.com

T0 crawl & index

T1 answer-engine files

T2 agent & MCP

T3 on-page & citability

T4 measurement

T5 hygiene

New build

T0 crawl & index

T1 answer-engine files

T2 agent & MCP

T3 on-page & citability

T4 measurement

T5 hygiene

The 12 repo-side checks apply to the new build only, because the incumbent's source is not ours to scan. All 12 pass. The incumbent's GA4 and GTM show green because they are live there today.

12 of 13

the minimum bar · unchanged since 2026-09-24

The one unmet item is GA4, held for cutover. The incumbent futurumgroup.com meets 7 of 13.

Conformance

100%

the must-pass checks: 30.5 of 30.5 weighted · unchanged since 2026-09-24 · incumbent 75.8%

Adoption

9 of 11

optional extras: shipped, +2 partial · incumbent 4 of 11, +4 partial

Soft-404 host

No

a bogus path 404s

Open fails

0

and no conformance warnings · incumbent 8

Why the soft-404 check comes first

Seven of the eighteen hosts this probe has been run against answer HTTP 200 for paths that cannot exist, which makes every other reading on them fiction — robots.txt, llms.txt and sitemap.xml all “exist” because the CDN serves the homepage for any path. Trial is clean, so every number on this page is a real measurement.

In plain English

What the new site can do that the current one can't

A site now has three kinds of visitor: people, search engines and AI assistants like ChatGPT and Claude. The current site was built for the first two; the new one is built for all three. Tap any card to see the proof.

AI assistants can quote a whole article, not a scrap of it

When someone asks an AI “what does Futurum think about this?”, the AI can read the full article text directly, clearly labelled, and quote it accurately.

Todaythe article text isn't labelled for machines, and the homepage is heavy enough (414 KB) that AI readers cut it off before the end.

New siteevery article carries its full text for machines; the homepage is less than half the weight (219 KB).

Show the proof

Run live against both sites, 2026-11-19

New site: the article text, labelled for machines

$ curl -s https://trial.futurumgroup.com/insights/opswat-at-gisec-2026-can-you-secure-what-you-cant-detect/ | grep -o '"articleBody":"[^"]\{0,110\}' "articleBody":"OPSWAT debuted its AI Content Inspector at GISEC Global 2026 in Dubai, targeting a new class of file-borne ris

(1,020 words in full)

futurumgroup.com: the same article

$ curl -s https://futurumgroup.com/insights/opswat-at-gisec-2026-can-you-secure-what-you-cant-detect/ | grep -o '"articleBody":"[^"]\{0,110\}' (no output: the page describes itself to machines as a web page, an image and breadcrumbs, never as article text)

Homepage weight

$ curl -s -o /dev/null -w '%{size_download}' https://<site>/ futurumgroup.com 414,444 bytes trial.futurumgroup.com 219,156 bytes

AI assistants get a reading guide to Futurum

A short guide tells an AI what Futurum is, what it covers and where to look, plus a complete text edition of the library it can read in one go.

Todaythe guide starts with an invisible stray character, so its title isn't recognised, and the complete edition is missing.

New siteboth present and correct.

Show the proof

Run live against both sites, 2026-11-19

futurumgroup.com: the first four bytes of its AI guide

$ curl -s https://futurumgroup.com/llms.txt | head -c 4 | xxd 00000000: efbb bf23 ...#

(an invisible byte-order mark sits before the "#", so readers expecting a title on line one don't find one)

The complete edition

$ curl -s -o /dev/null -w '%{http_code} %{size_download}' https://<site>/llms-full.txt futurumgroup.com 404 (missing) trial.futurumgroup.com 200 2,301,514 bytes

New site: the guide opens cleanly

$ curl -s https://trial.futurumgroup.com/llms.txt | head -3 # Futurum

> AI decision intelligence: research, benchmarks and live market signal for the people who have to choose.

AI agents can ask Futurum questions directly

Instead of guessing from search results, an AI agent can connect to the site and ask: search the research, list the analysts, show coverage of a company, fetch a report or the methodology. Think of it as a front desk for software.

Todaythere is no front desk. An agent can only scrape pages.

New site16 ready-made questions an agent can ask, using MCP, the open standard the major AI labs have adopted.

Show the proof

Run live against both sites, 2026-11-19

An AI agent asks: "What has Futurum published on quantum computing?"

$ curl -s https://trial.futurumgroup.com/api/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "search_posts", "arguments": {"query": "quantum computing", "limit": 3}}}' { "count": 332, "posts": [ { "title": "Quantum in Context: Infleqtion’s Quantum Computer Live at UK Testbed", "path": "/insights/quantum-in-context-infleqtions-quantum-computer-live-at-uk-testbed/", "publishedAt": "2024-07-31" }, { "title": "Quantum in Context: Rigetti Computing’s Q1 2024 Earnings and 9 Qubits", "path": "/insights/quantum-in-context-rigetti-computings-q1-2024-earnings-and-9-qubits/", "publishedAt": "2024-05-22" }, { "title": "Quantum in Context: Quantum Companies Rotate in New Leaders", "path": "/insights/quantum-in-context-quantum-companies-rotate-in-new-leaders/", "publishedAt": "2024-07-10" } ] }

The same question to futurumgroup.com

$ curl -s -o /dev/null -w '%{http_code}' -X POST https://futurumgroup.com/api/mcp -d '{...}' 404 (no front desk: nothing answers)

The count is live and moves as posts are added; trial syncs its content from futurumgroup.com on a schedule. The tool returns more fields than shown (summary, snippet, score, url); the proof keeps title, path and date.

A quote can be checked, and cited properly

An AI that wants to be careful can confirm that a quote attributed to Futurum appears in its research, and get a proper citation with a link back.

Todayno way to check. A misquote looks the same as a real one.

New site&ldquo;verify quote&rdquo; and &ldquo;get citation&rdquo; are two of the 16 questions.

Show the proof

Run live against both sites, 2026-11-19

An AI checks a real quote before using it

$ curl -s https://trial.futurumgroup.com/api/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "verify_quote", "arguments": {"quote": "Quantum computing is not new. The scientists Paul Benioff, Yuri Manin, and Richard Feynman proposed the"}}}' { "found": true, "title": "Is Quantum Computing Languishing? – Report Summary", "url": "https://trial.futurumgroup.com/press-release/is-quantum-computing-languishing-report-summary/" }

...and a quote Futurum never published

$ curl -s https://trial.futurumgroup.com/api/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "verify_quote", "arguments": {"quote": "this is a quote Futurum never published about quantum"}}}' { "found": false }

...then asks how to cite it

$ curl -s https://trial.futurumgroup.com/api/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "get_citation", "arguments": {"path": "/press-release/is-quantum-computing-languishing-report-summary/"}}}' APA: Sutor, D. B. (2024, December 19). Is Quantum Computing Languishing? – Report Summary. The Futurum Group. https://trial.futurumgroup.com/press-release/is-quantum-computing-languishing-report-summary/ plain: Dr. Bob Sutor, The Futurum Group, "Is Quantum Computing Languishing? – Report Summary," December 19, 2024. https://trial.futurumgroup.com/press-release/is-quantum-computing-languishing-report-summary/

Partners and developers can plug in without a meeting

The site publishes a machine-readable description of what it offers and how to use it, so another company's software can connect to Futurum's research on its own.

Todaynone published.

New sitefour: an API description, an agent &ldquo;business card&rdquo;, a capabilities file, and a page for agent builders.

Show the proof

Run live against both sites, 2026-11-19

New site: the API description

$ curl -s https://trial.futurumgroup.com/openapi.json | jq -r '.info.title, (.paths | keys[])' Futurum Public Read API /api/content/companies /api/content/companies/{slug} /api/content/pages /api/content/pages/{slug} /api/content/people /api/content/people/{slug} /api/content/posts /api/content/posts/{slug} /api/content/practice-areas /api/search

The four machine-readable descriptions

$ for p in /openapi.json /.well-known/agent-card.json /agents.json /for-agents/; do curl -s -o /dev/null -w "$p %{http_code}\n" https://<site>$p; done futurumgroup.com new site /openapi.json 404 200 /.well-known/agent-card.json 404 200 /agents.json 404 200 /for-agents/ 404 200

Google finds every page, and old links still work

The site tells Google where its full page list is. Every one of the 36,533 addresses Google knows about today gets a clear answer: here it is, it moved (and where), or it was retired on purpose.

Todaythe page list exists, but the first file every crawler reads never mentions it.

New siteit does. Every old address is being mapped before the switch, so none fails without an explanation, and links other sites made years ago keep their value.

Show the proof

Run live against both sites, 2026-11-19

Does robots.txt, the first file every crawler reads, point to the page list?

$ curl -s https://<site>/robots.txt | grep -i '^sitemap' futurumgroup.com (nothing) trial.futurumgroup.com Sitemap: https://trial.futurumgroup.com/sitemap.xml

An old address that moved

$ curl -s -o /dev/null -w '%{http_code} %{redirect_url}' https://trial.futurumgroup.com/analyst/donald-jin/ 308 https://trial.futurumgroup.com/donald-jin/ (moved for good; Google carries the link value across)

An old address retired on purpose

$ curl -s -o /dev/null -w '%{http_code}' https://trial.futurumgroup.com/tag/creative-stack/ 410 ("gone, deliberately": Google drops it cleanly instead of retrying a broken link)

Every one of the 36,533 old URLs, checked

From the September 2026 inventory (not re-run for this update): 1,199 served directly, 132 redirected, 25,290 retired on purpose, the rest 404 for a tracked reason (import still landing, pending the content owner, or dropped on purpose). No unexplained 404s at the time of that run.

Security researchers know who to tell

A standard file tells anyone who finds a security flaw exactly where to report it privately, instead of guessing, giving up, or posting it in public.

Todayno such file.

New sitepresent, with a contact address and an expiry date.

Show the proof

Run live against both sites, 2026-11-19

New site

$ curl -s https://trial.futurumgroup.com/.well-known/security.txt Contact: mailto:security@futurumgroup.com Expires: 2027-08-23T00:00:00Z Preferred-Languages: en Canonical: https://trial.futurumgroup.com/.well-known/security.txt

futurumgroup.com

$ curl -s -o /dev/null -w '%{http_code}' https://futurumgroup.com/.well-known/security.txt 404

It stays fixed, because it can't quietly break

Every item on this list is generated by the site's own code and tested on every change. An editor changing a page can't silently remove one, the way a plugin update can on WordPress.

Todaynobody can check, because WordPress's internals aren't open to inspection.

New site12 extra checks prove it: the &ldquo;72 vs 84&rdquo; above.

Show the proof

Run against the code, 2026-11-19

Where each item lives in the new site's code

$ pnpm audit:mechanicals --repo . # the 12 repo checks, summarised llms.txt generated route app/llms.txt/route.ts llms-full.txt generated route app/.../llms-full.txt/route.ts openapi.json generated route app/openapi.json/route.ts feed.xml generated route app/feed.xml/route.ts sitemap route handlers app/sitemap.xml/route.ts, app/sitemap/[shard]/... robots app/robots.ts MCP server app/api/mcp/route.ts .well-known app/.well-known/agent-card.json/route.ts, ...

Tested on every change

$ pnpm pre-deploy # the gate every pull request must pass type-check ok lint ok test 6,656 tests passed (CI on main, 2026-11-19) build ok

A guard test fails any pull request that makes a page read the whole library, so the site stays fast as it grows. WordPress's equivalents live in plugins and theme settings, which nobody outside can inspect.

Nothing is lost at the switch. Analytics, Search Console and the ad pixels switch on the day the new site goes live, so marketing keeps every number it has today.

What this doesn't promise. These are capabilities, not guaranteed traffic. Whether Google ranks a page, or an AI chooses to quote it, still depends on the research itself and on time. What changes is that nothing technical stands in the way, and after the switch we can measure the result.

Latest update, 2026-11-19 10:49 UTC (probe 1.0.3, re-run on trial.futurumgroup.com)

All 12 repo checks pass. The analytics env slot is now wired, so 71 mechanicals work today and 7 switch on at cutover (was 70 and 8).

Trial still scores 100% on conformance, 12 of 13 on the bar, with 0 open failures. The one bar item left is GA4, held for cutover.

www moved from 72.7% to 75.8% and still has 8 failing conformance checks.

What changed since 2026-09-30 about 180 merged PRs, by theme

&#10003;

Trial is the new site, on its own address

The build moved from the interim preview host to trial.futurumgroup.com, the stage that becomes futurumgroup.com at cutover. Content syncs from www on a schedule, so trial carries the live corpus.

&#10003;

The pages follow the approved marketing wireframe

Home, About, the three audience pages, Research, Media, Testing, Leadership, Newsroom and Insights were rebuilt from the November wireframe, with a three-menu header and a www-style footer (#257, #260, #264, #268, #269, #274, #275, #290, #292, #301, #315, #343 and this update).

&#10003;

Accessibility passes

A skip link, clear focus, correct heading levels, captioned tables, form error summaries and 44 px touch targets; CI now fails the build on any serious or critical axe violation (#259, #266, #270, #291, #302, #304).

&#10003;

Faster and steadier pages

Lighthouse runs against the guide's performance budgets in CI, the font-swap layout shift is gone, and the homepage no longer downloads the Ask Futurum widget (#277, #281, #284, #303). Median response time on trial is 86 ms.

&#10003;

Memory stays flat as the corpus grows

Every request reads the content store by key or a bounded query; whole-corpus reads happen only at build time, and a test fails any route that regresses (#230, #233, #285, #287, #288, #311, #322, #324, #326, #328, #333).

&#10003;

Publishing through Polaris

Polaris (app.futurumgroup.com) can now publish to this site through the keyed API lane, with per-key edit rights and a reconcile pass for posts that go live from WordPress (#312, #316, #317, #320, #321, #323, #327, #329, #330, #331, #336, #342).

&#10003;

HubSpot forms

Contact, newsletter and other forms submit to HubSpot from the server, with the same form names www uses (#187, #190, #197, #202, #296, #310, #341).

&#10003;

Security follow-ups

The fixes from the September review shipped, including the hashed script policy on static pages (#198, #222, #224, #227, #229, #235, #240, #335). See the Security tab.

&#10003;

AI crawler visits are counted

A daily rollup counts visits from GPTBot, ClaudeBot, PerplexityBot and the other AI crawlers, behind a switch (#189).

&#10003;

Content and SEO parity with www

Feeds (RSS, Google News sitemap), redirects, careers, news, Labs tools and analyst profiles now match www (#148, #166, #234, #293, #295, #340, #344, #345).

Shipped and working the mechanicals that are done

The new build matches or leads on every tier, and ships four capabilities the incumbent has none of.

trial (new build) futurumgroup.com (incumbent)

T0 crawl & index

100%

100%

T1 answer-engine files

100%

33%

T2 agent & MCP surfaces

100%

30%

T3 on-page & citability

100%

90%

T4 measurement

n/m

n/m

T5 hygiene

100%

94%

Per-tier only — these are never averaged into one grade. T4 reads &ldquo;n/m&rdquo;, not 0%: the tier holds no conformance checks, so there is nothing there to score.

What the new build ships that the incumbent does not

&#10003; Answer-engine files

llms.txt — 15,743 bytes, H1 + blockquote, MCP in the first KB (incumbent: no H1, no MCP)

llms-full.txt — 2,292,894 bytes (404)

agents.json — valid, 6,541 bytes (404)

agent card — valid, 8,872 bytes (404)

openapi.json — OpenAPI 3.1.0, 10 paths (404)

/for-agents — 20,662 chars server-rendered (404)

/ai4me — 4,834 chars (404)

feed.xml — 50 items (incumbent: RSS at /feed/, discovered via the homepage's advertised <link rel=alternate>; the probe now follows that link, so it passes on its own)

Markdown mirror of every page, edge-negotiated (none)

&#10003; A live, discoverable MCP server

/.well-known/mcp.json → /api/mcp

initialize → futurum-web-mcp 1.0.0, protocol 2025-06-18, open (no auth)

16 tools: search_posts, get_post, list_pages, get_page, verify_quote, list_analysts, get_analyst, list_companies, get_company_coverage, list_practice_areas, get_site_info, get_citation, get_practice_area, get_methodology, get_taxonomy, list_research_reports

Five more tools for a caller holding a publishing token: draft, update, attach an image, submit for review, and diff revisions. None of them publishes; the furthest a post goes is the review queue.

Incumbent: no MCP endpoint (404 on /api/mcp and /mcp), though it does publish OAuth metadata.

&#10003; Citability — the crown jewel

articleBody in the deep-page JSON-LD: 7,353 chars / 1,020 words, plus SpeakableSpecification

4 JSON-LD blocks on the article, 3 on the homepage

Incumbent: no articleBody at all. Non-JS crawlers quote this, not the DOM. Checked on its real OPSWAT article, not just the auto-sampled careers page — same result.

&#10003; Crawl, index & hygiene

robots.txt 200, 8 groups, Sitemap: line present (incumbent has none — its only T0 miss)

Sharded sitemap index → 11,675 URLs across the sampled shards (incumbent 734)

One canonical host; http 301s to https; bogus paths 404; redirects under 0.5 s

Homepage 219,177 bytes (incumbent 414,444 — over the truncation line)

security.txt and a web app manifest (incumbent: neither)

In the repo, as generated routes rather than static files

Every surface below is a real route that renders at request time, so it cannot drift from the content the way a hand-maintained file does. Repo checks: conformance 2 of 2, adoption 3 of 3.

Show the 9 routes

Surface Source State

llms.txt app/llms.txt/route.ts &#10003;pass

llms-full.txt app/llms-full.txt + app/practice-areas/[slug]/llms-full.txt &#10003;pass

openapi.json app/openapi.json/route.ts &#10003;pass

feed.xml app/feed.xml/route.ts &#10003;pass

robots app/robots.ts &#10003;pass

MCP app/api/mcp/route.ts &#10003;pass

sitemap app/sitemap.xml/route.ts + app/sitemap/[shard]/route.ts &#10003;pass

.well-known app/.well-known/*/route.ts (mcp.json, agent-card.json, agents.md, security.txt) &#10003;pass

markdown mirrors app/api/md/[...segments]/route.ts + lib/seo/mirror/edge.ts &#10003;live

Left to go nothing that can close before cutover

! Held for cutover, by decision: analytics and pixels

Trial carries no GA4, GTM, Ads, Reddit or Meta tag yet, by decision: the pixels go in at cutover, not on a noindex trial site where they would pollute production data. The incumbent is measured today — GA4 G-ES8BSET5RC and GTM containers GTM-KM6XDZR6 and GTM-W4999QMH. This is a cutover gate: measurement must not switch off on the day the before/after matters most.

The one unmet bar item

!

13. GA4 or a named alternative, browser-verified

The cutover hold above. The code is ready: the analytics slot is wired in the repo, and GA4 switches on when its measurement id is set at cutover.

t4.ga4 — GA4 measurement id: not in server HTML repo.ga_env_slots — pass: the GA4 slot (NEXT_PUBLIC_GA4_MEASUREMENT_ID) is wired in app/components/analytics/

Cutover checklist items that ride with it

!

GTM, Google Ads, Reddit and Meta pixels

Same hold, same moment. Adoption warns only; none is scored.

t4.gtm · t4.google_ads · t4.reddit · t4.meta_pixel — not in server HTML

!

Google Search Console verification

Likely verified by DNS TXT, which carries over automatically. Confirm before cutover.

t4.gsc_verification — no google-site-verification meta (may be verified by DNS TXT or file)

!

Flip noindex off

Automatic: SITE_INDEXABLE is true only on futurum-web-prod.

Response time

&#10003;

t5.ttfb passes: 86 ms median of five (74&ndash;198 ms; the live site 94 ms) on trial, not production

How response time is scoredProbe 1.0.3 (PR #71) discards one warm-up request and scores the median of five, so one cold sample cannot fail the check. Production response time is measured at cutover, on the warm production path.

Security the September 2026 review

A white-hat security review ran on 2026-09-26: automated static analysis plus five independent, read-only reviews across the codebase, followed by two further pre-cutover passes. Every fix shipped as its own reviewed pull request, verified on a preview stage before merging. Nothing was deployed to production mid-review. There were no Critical findings.

Findings

28

2 High &middot; 12 Medium &middot; 14 Low

Fixed

28 of 28

every finding fixed; operational items are listed under Still open

Review passes

3

the initial review, plus two pre-cutover follow-ups

Prod deploys mid-review

0

every change verified on a preview stage first

Severity Found Fixed Open

High 2 2 0

Medium 12 12 0

Low 14 14 0

Total 28 28 0

Findings and fixes, by severity

All 28 findings (severity, what was found, what changed, and where)

Severity Finding Fix Where

High A patched Next.js image-processing vulnerability (remote code execution) plus a related cache-poisoning issue were present, and the image pipeline accepted more source hosts than it needed to. Fixed &mdash; upgraded Next.js and narrowed the accepted image hosts, with a test that forbids a wildcard host from being reintroduced. PR #100

High The image-rendering function bundled an image-processing library with known vulnerabilities. Fixed &mdash; pinned to a patched version, confirmed in the deployed build. PR #106

Medium The backend functions behind the site and its image pipeline could be reached directly, bypassing the CDN, its cache and its edge protections. Fixed &mdash; direct access now returns a clean rejection; all traffic must come through the CDN, which carries the protections below. PR #106

Medium The public site's backend held broader database and storage permissions than the code uses. Fixed &mdash; scoped to least privilege, matched to the commands the code sends. PR #106

Medium Scanning a publish request for credentials and unsafe content could take several seconds on a large request, before it was even rate-limited. Fixed &mdash; rewritten to run in linear time; the same requests now complete in well under a second. PR #108

Medium A publishing credential could edit, delete or reassign another author's posts. Fixed &mdash; ownership is enforced; only an editor-level credential can act on someone else's content. PR #101

Medium Content stored outside the normal git-reviewed path was not re-checked against the site's safety rules at render time. Fixed &mdash; re-checked against the same rules on every render; anything that fails renders as plain text and is logged. PR #104

Medium Search and the AI-agent interface (MCP) shared no rate limit, and a single agent request could trigger many expensive lookups at once. Fixed &mdash; results are briefly cached, batch size is capped, and both surfaces are rate-limited at the edge. PR #105, #110

Medium A deleted or unpublished item could still appear in search results for a while. Fixed &mdash; search now checks against what is published, and the cache expires in minutes rather than persisting until the next restart. PR #105

Medium The site's script policy (CSP) allows inline scripts on most routes by default, which would widen the impact if HTML injection ever occurred. Fixed &mdash; canvas documents (like this one) render in a fully isolated sandbox, on their own web address, under their own tighter policy. The two most dynamic non-canvas routes use a per-request policy, and static routes now allow only the site's own inline scripts, by hash. Production enforces it. PR #111, #116, #131

Medium A number of previously published articles still linked to a hostname associated with a past incident on the site's former hosting provider. Fixed &mdash; those links were rewritten to point at this site instead, with a test that blocks a recurrence. PR #109

Medium A now-unused legacy publishing path, and the shared access key that could use it, were still live. Fixed &mdash; retired entirely; the old key is now rejected outright. PR #128

Medium The edge network had no broad protection against common attack patterns beyond the site's own request checks. Fixed &mdash; managed protection rules and a site-wide request-rate limit were added, tuned in a monitor-only mode first to confirm no legitimate traffic was affected. PR #129

Medium Stored content had no point-in-time recovery or version history, so a bad delete or a bug could be permanent. Fixed &mdash; both enabled; a mistaken delete or cleanup is now recoverable. PR #129

Low Error responses from the AI-agent interface could include internal technical detail. Fixed &mdash; a generic message is returned; the detail is logged privately instead. PR #105

Low A markdown-format submission could slip an unsafe link scheme past the safety check, and a few text fields were not scanned at all. Fixed &mdash; the check was hardened and extended to cover those fields. PR #108

Low The standalone-document viewer used on pages like this one did not check where a document came from before rendering it. Fixed &mdash; it now only renders reviewed, git-committed documents; verified against every such document currently on the site. PR #104

Low The deployed server bundle included some source, documentation and test files it did not need. Fixed &mdash; excluded from the deployed package. PR #107

Low Automated build steps referenced third-party tooling by a movable label rather than a fixed, verifiable version, and dependency updates were not automated. Fixed &mdash; pinned to exact, verified versions; automatic dependency-update proposals turned on. PR #99

Low A strict, hard-to-reverse browser security header was being sent on every environment, including ones still under test. Fixed &mdash; scoped to when it is the right call. PR #107

Low Some links carried marketing tracking parameters, or routed through an old link-redirect service. Fixed &mdash; parameters stripped and links normalized across the affected content. PR #109

Low Content-import tooling followed a redirect without checking where it led. Fixed &mdash; every redirect hop is now checked against an approved list of hosts. PR #109

Low Deleted content bodies were never cleaned up in storage. Fixed &mdash; an operator-run cleanup tool was added, off by default, with a safety grace period before anything is removed. PR #117

Low A testing-only dependency carried a known low-severity advisory. Fixed &mdash; upgraded. PR #118

Low The build pipeline did not scan for accidentally committed secrets or run a dependency audit. Fixed &mdash; both added to the automated build. PR #127

Low There was no structured logging or alerting for security-relevant events, such as a spike in blocked or unauthorized requests. Fixed &mdash; dedicated logs and four automated alarms were added. Choosing the production alert recipient is still open &mdash; see below. PR #129

Low Publishing credentials had no expiry or rotation, and no simple way to see which ones existed. Fixed &mdash; optional expiry and rotation added, plus a listing an operator can audit without ever seeing the credential itself. PR #133

Low The site depended on a third-party font-hosting service. Fixed &mdash; fonts are now self-hosted, and the dependency was dropped from the site's own security policy. (The standalone documents on this canvas lane still use it, deliberately, per this project's authoring rules.) PR #135

Checked and found clean

Data and history

Full git history, scanned for secrets, keys and account credentials &mdash; none found

Published content and static assets &mdash; no credentials, tokens, private IPs or personal data

Credential storage &mdash; modern password hashing with constant-time comparison, and safe, closed failure if a secret is ever missing

Surfaces and output

The published/draft visibility gate &mdash; holds identically across every read surface: the JSON APIs, the AI-agent interface, search, feeds, sitemaps and the plain-text AI-reading files

Structured data, feed output, redirect handling and file-path handling &mdash; checked for injection and traversal; clean

The backend's outbound network access and storage permissions, and the safeguards on its automated replication and cleanup tooling

Still open (as of 2026-11-19)

&#10003;

Static pages no longer allow inline scripts on production

The site's own inline scripts are allowed by hash, and production enforces it. A non-production stage may still run in report mode.

!

Who receives the security alarms

Staging subscribes an address set in the repo, and production refuses to deploy without one. Still to do: confirm the staging subscription was accepted and choose a Futurum-owned address for production.

!

Confirm the security-contact mailbox

security.txt names security@futurumgroup.com. A Futurum mail administrator must confirm it receives outside mail.

!

Automated dependency-review scanning

Wired up, and waits on GitHub Advanced Security being enabled for the repository. That is an org-admin decision.

!

This page's exhibit links

Inside its sandbox this page cannot read the site's address, so its copy-paste blocks fall back to a fixed address, now https://trial.futurumgroup.com. That is right while the page is served from trial. The page is removed before launch.

&#10003;

Infrastructure cleanups

The region pin and the move to the current infrastructure tooling are done (issue #121).

Publish to this site one core behind every door, live in seconds

Everything above measures whether machines can read this site. This is what lets Futurum (or an AI acting for Futurum) write to it: one checked, safe call that gets a new post live in seconds, with no rebuild and no deploy.

Two exhibits were made through this pipeline on the interim preview host, before the site moved to trial. They are not on trial.futurumgroup.com (both answer 404 there), and they still load on the interim host as of 2026-11-19, so the links below point at it: a sample insight created exactly the way the curl example below creates one, preview.erikbethke.com/insights/sample-insight-publishing-pipeline/, and a research report about agentic research reports, written and published by an agent through the same pipeline: preview.erikbethke.com/research-reports/agentic-research-reports/. The interim host is retired later, and the links go with it.

Where publishing stands, 2026-11-19. The day-to-day path is Polaris (app.futurumgroup.com): analysts write there, and Polaris publishes to this site through the keyed API below. Each Polaris user's keys share that user's posts, and a post published from WordPress is picked up by a reconcile pass. The exhibits linked above were made on the old interim preview host, not on trial.

For developers: the publishing API (endpoints, curl, CLI and the AI system prompt)

Measured on the interim preview host, 2026-09-24 (not re-measured on trial) &mdash; the sample insight above, no cache-busting

Step Time

Create answers 201 2.7 s

Article live at its own URL 9.9 s

/insights/ lists it 10.6 s

feed.xml carries it 11.3 s

Replaying the same request &mdash; same Idempotency-Key, same body &mdash; came back byte-identical with Idempotent-Replayed: true: no second revision, no duplicate post. No rebuild and no deploy anywhere in this; the whole round trip is HTTP.

Copy-paste for whichever AI you use

Four blocks, each complete on its own. Tap Copy and the exact text &mdash; with this site's own address filled in &mdash; is on your clipboard.

a. Give this to your AI a self-contained prompt any agent can follow

Paste this whole block into Claude, ChatGPT, Gemini or any coding agent, along with your token, and tell it what you want published.

Copy You can publish directly to this site over HTTP. Read this whole block before you write any code, then follow it exactly &mdash; every rule below is enforced server-side, not a suggestion.

ENDPOINT Create POST https://trial.futurumgroup.com/api/posts Update PUT https://trial.futurumgroup.com/api/posts/<slug> (the body must carry the same slug; send If-Match: "<rev>" to refuse a stale edit) Read GET https://trial.futurumgroup.com/api/posts/<slug>?kind=<kind> (your own posts only: status and a signed preview link) Delete DELETE https://trial.futurumgroup.com/api/posts/<slug>?kind=<kind> (soft delete; append &force=true to hard-delete) Images POST https://trial.futurumgroup.com/api/media (raw PNG, JPEG or WebP as the body; see IMAGES below)

AUTH Authorization: Bearer <YOUR_TOKEN> A token looks like fxp_<id>.<secret>. You do not mint your own &mdash; it is issued by the site owner (see "For operators" below) and handed to you, usually as an environment variable. It may carry an expiry. The retired shared X-API-Key header authenticates nobody.

IDEMPOTENCY Send an Idempotency-Key header on every write. Derive it from the request's own content &mdash; e.g. the slug plus a hash of the body &mdash; rather than a random value, so retrying after a timeout or a 5xx is always safe: the same key and the same body replay the original response with an Idempotent-Replayed: true header instead of creating a duplicate. The same key with a DIFFERENT body is refused outright (422 idempotency_key_reused) &mdash; mint a new key if the request is meant to change.

SUBMISSION BODY (POST and PUT), as JSON: { "kind": "insight", // insight | news | press-release | research-report &mdash; "page" is not a post; pages stay in the git lane "slug": "your-post-slug", // lowercase-kebab-case; fixed at creation, PUT cannot move it "title": "&hellip;", // <= 300 characters "dek": "&hellip;", // <= 1000 characters; the one- or two-sentence summary "body": { "format": "html", "source": "<p>&hellip;</p>" }, // format is "html" or "markdown" &mdash; "canvas" is refused, see below "authors": ["a-person-slug", { "guest": "A Guest Name" }], // at least one person slug is REQUIRED on a new post; a guest is a name only, never a profile page "taxonomy": { "companies": ["nvidia"], // slugs &mdash; REQUIRED (at least one) for insight and news; an unknown company is rejected, not invented "practiceAreas": ["ai"], // codes or slugs &mdash; unknown ones are rejected "featuredPeople": [], // person slugs &mdash; must resolve "insightType": "&hellip;", // optional, free text; research-report posts may also set "researchType" "verticals": [], "tags": ["free-text-tag"] // created on first use }, "seo": { "title": "&hellip;", "description": "&hellip;" }, // optional overrides only &mdash; there is no canonical override; the URL is derived from kind + slug "featuredImage": "&hellip;", // optional; an uploaded media id, or an https image URL on an allowlisted host "publishAt": "2026-12-01T09:00:00Z", // optional; see SCHEDULING "status": "draft" // draft | pending | publish }

A key held for review turns "publish" into pending: the post waits in the review queue for an editor. A key that holds neither publish nor review-hold gets 403 for "publish".

HTML RULES (format: "html") Only these survive a server-side sanitizer; everything else is stripped (with its contents, for script/style/iframe/object/form and the like) or unwrapped: p, br, hr, h2, h3, h4, ul, ol, li, blockquote, figure, figcaption, img, a, strong, em, b, i, u, s, sub, sup, code, pre, and the full table family (table, caption, colgroup, col, thead, tbody, tfoot, tr, th, td). h1/h5/h6 are demoted to h2/h4. <a> keeps only href/title/class; <img> keeps only src/alt/title/width/height &mdash; no onclick, no style, no target. Every href or src must be http(s), mailto:, tel:, a root-relative path, or a #fragment. A TABLE NEEDS REAL <table> MARKUP &mdash; there is no markdown-table support anywhere on this site.

MARKDOWN RULES (format: "markdown") No raw HTML tags and no { or } anywhere in the source &mdash; either one is refused outright. That also rules out a table in a markdown body (see above): use format: "html" instead.

IMAGES POST /api/media with the raw image as the body and Content-Type image/png, image/jpeg or image/webp. Needs the "media" capability. At most 960 KiB, each side 16-4096 px, one frame (no SVG, GIF or animated WebP). The answer is 201 with { id, url: "/media/<id>", ... }. Use it as "featuredImage": "<id>", or in the body as <img src="/media/<id>" alt="&hellip;"> (an unknown id is 422 unknown_media). An absolute https <img src> also works in an HTML body.

SCHEDULING status "publish" with a future publishAt, from a token that holds the "schedule" capability, stores the post as scheduled and it goes live at that time. At most 364 days ahead (422 publish_at_too_far). Without "schedule" a future publishAt is 403.

NOT ACCEPTED HERE format: "canvas" is refused (422 canvas_not_supported). A canvas document is a complete standalone HTML page and needs a sandboxed renderer this lane doesn't have yet &mdash; that stays a git-lane, reviewed-pull-request thing.

IF IT FAILS 400 validation the JSON doesn't match the body above (unknown field, too long, bad slug) &mdash; the issues are listed 401 unauthenticated the token is missing, malformed, expired or wrong &mdash; check Authorization 403 forbidden the token lacks the capability this needs (create but not publish, schedule, delete or media), or the post belongs to another key 409 duplicate_slug that slug already exists for this kind &mdash; pick another, or PUT to the existing one 409 stale_revision you sent If-Match and the post has moved on &mdash; read it again 422 missing_metadata a new post needs an author (a person slug) and, for insight and news, a company &mdash; data.missing says which 422 scan_blocked the body reads like a credential, an internal hostname, or similar &mdash; find it and remove it 422 unknown_taxonomy a company, practice-area or featured-person slug doesn't exist &mdash; drop it or fix it 422 idempotency_key_reused this key was already used with a different body &mdash; mint a new one 429 quota_exceeded over the daily quota (Retry-After: N) &mdash; wait N seconds, then retry with the SAME idempotency key

NEVER include a credential, an internal hostname, or an unreleased customer name in a submission &mdash; the server scans every field before it stores anything and blocks the request outright when it finds one.

b. curl, by hand create, replay, edit, delete

The same four calls, run straight from a terminal.

Copy export SITE="https://trial.futurumgroup.com" # or your own site export TOKEN="<YOUR_TOKEN>"

# Create a draft insight curl -sS -X POST "$SITE/api/posts" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: my-first-post-v1" \ -d @- <<'JSON' { "kind": "insight", "slug": "my-first-post", "title": "My first post", "dek": "A short summary of what this post covers.", "body": { "format": "html", "source": "<p>Hello from an AI-assisted publish.</p>" }, "authors": ["futurum-research"], "taxonomy": { "companies": ["nvidia"], "tags": ["hello-world"] }, "status": "draft" } JSON

# Replay: run the exact command above again, unchanged. The response comes back # byte-identical, plus an Idempotent-Replayed: true header &mdash; nothing is created twice.

# Edit the title and publish it (needs a token that holds the publish capability; # a draft-only or review-held token leaves it draft or pending) curl -sS -X PUT "$SITE/api/posts/my-first-post" \ -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \ -H "Idempotency-Key: my-first-post-edit-1" \ -d '{"kind":"insight","slug":"my-first-post","title":"My first post, now live","dek":"A short summary of what this post covers.","body":{"format":"html","source":"<p>Hello from an AI-assisted publish.</p>"},"authors":["futurum-research"],"taxonomy":{"companies":["nvidia"],"tags":["hello-world"]},"status":"publish"}'

# Soft-delete it (restorable; needs the delete capability); append &force=true to hard-delete instead curl -sS -X DELETE "$SITE/api/posts/my-first-post?kind=insight" \ -H "Authorization: Bearer $TOKEN" -H "Idempotency-Key: my-first-post-delete-1"

c. The CLI pnpm publish:post, for a file on disk

Frontmatter in, a live post out. A .html file sends as HTML; anything else sends as markdown. The idempotency key is derived from the file's path and content, so re-running after a timeout is always safe.

Copy export FUTURUM_SITE_URL="https://trial.futurumgroup.com" # or your own site export FUTURUM_PUBLISH_TOKEN="<YOUR_TOKEN>"

# Print the request and its Idempotency-Key without sending it pnpm publish:post content/drafts/my-post.md --dry-run

# Publish it for real &mdash; frontmatter (kind, slug, title, dek or summary, status, authors, companies, # practiceAreas, tags&hellip;) becomes the Submission pnpm publish:post content/drafts/my-post.md

# Edit the same file later, matched by its frontmatter kind + slug pnpm publish:post content/drafts/my-post.md --update

d. For operators only issuing and revoking a credential

Run by the site owner, never by the AI itself &mdash; this is the one place a credential is minted, and it needs infrastructure access the other three blocks don't (run it under npx sst shell --stage <stage> --). The token prints once, to stdout, and is never logged. Analysts mint their own draft-only keys from Polaris instead.

Copy # Issue a credential for a new agent, capped at 50 writes a day, expiring in 30 days npx sst shell --stage <stage> -- pnpm -s publishing:principal create my-agent --role agent --caps create,publish --quota 50 --expires-in-days 30

# Replace its secret, keeping its posts (the old secret stops at once, or after --overlap-minutes N) npx sst shell --stage <stage> -- pnpm -s publishing:principal rotate my-agent

# Revoke it npx sst shell --stage <stage> -- pnpm -s publishing:principal disable my-agent

Built since the first version of this page: scheduling (a future publishAt, for a key that holds the schedule capability), image upload (POST /api/media), the review queue for pending posts, and authenticated MCP write tools that draft and submit for review but never publish. Not built: the WordPress-compatible adapter (Polaris publishes through the keyed API above instead), and canvas documents on this API lane, which stay a git-lane, reviewed-pull-request thing until a sandboxed renderer exists.

Cutover to-do issue #121, the Polaris-account move

Issue #121: the security and infrastructure work for moving this site to Futurum's own AWS account. As of 2026-11-19 the account and infrastructure items are done; the email and DNS items are open, and they are changes on futurumgroup.com's DNS, not on this site.

Account and infrastructure

&#10003;

Region pinning

Done: stages are created in us-east-2, where staging and trial run.

&#10003;

Current major version of the infrastructure tooling

Done: stages deploy on sst 4.

&#10003;

security.txt contact

Done: it names security@futurumgroup.com. The mail-admin confirmation is still listed on the Security tab.

Email and DNS

checked 2026-10-21. The site sends no mail itself: alarms go through AWS and form mail through HubSpot.

!

Tighten the subdomain mail-spoofing policy

futurumgroup.com's policy covers the main domain but not subdomains; extend it once reports show every legitimate sender is aligned.

!

Review the approved mail-sender list

It uses 7 of its 10 DNS lookups. Drop senders no longer in use, and delete a stray second record that holds a bare HubSpot entry.

!

Give any new site mail its own signed sender

Only if the site ever sends mail as Futurum.

!

Retire or tighten the preview domain's mail policy

It goes away when the interim preview host is retired.

Homepage free-account signup

added 2026-10-07 and not part of issue #121; the Ask Futurum widget (now on /research/) ships with a mock signup first while stakeholders iterate; real account creation waits on every item here

!

Leadership decisions on the signup design

Approve creating the account only after the visitor clicks the emailed link; settle what a signup gets (trial length, starting credits, practice-area access), whether personal email domains are allowed, and the daily limits and spend ceiling.

!

Turn on credit metering for trial accounts

Starting credits only bound usage when metering is on. Switching it on also starts metering existing trial users, so it needs its own sign-off.

!

Build the platform-side signup endpoint

One purpose-built route on the Polaris platform, callable only by this site with its own narrowly scoped key. It never returns a login, and every new account starts in its own isolated workspace.

!

A daily spend ceiling for signup accounts

A new platform control that caps total AI spend across all self-serve signups per day; today's spend breaker covers only API-key traffic.

!

The site's own abuse layer

A CAPTCHA checked on the server, per-visitor throttling and disposable-email filtering in front of the endpoint, because the platform sees every request as coming from this site.

!

Consent text and retention for trial accounts

Signup terms and how long expired trial accounts are kept &mdash; needs legal review.

!

Protect mail reputation

Verification mail goes to addresses that have not yet proven they asked for it; it sends from its own signed sender identity (see Email and DNS above) so a complaint spike cannot suspend the platform's other mail.

!

Swap the mock for the live flow

Replace the widget's preview signup with the real call and remove the preview marker. Staging first behind a switch that defaults off; production only after leadership, security and cost review.

Live list. This tab summarizes issue #121 on GitHub as of 2026-11-19. The signup items are tracked separately.

packmechanicals@2026.09.0 (row probe_version 1.0.3, from PR #71)

probed_at2026-11-19T10:49:01Z — trial.futurumgroup.com · 10:49:24Z — futurumgroup.com

deep page/news/how-will-cisos-be-impacted-by-the-proliferation-of-ai-in-cybersecurity/ (incumbent: auto-selected /about-us/newsroom/)

reposite source @ main 2d5c3fb3 (repo checks) · trial deployed from main

denominator30.5 weighted conformance points, T0–T5 (incumbent 32)

rowsthe probe's JSON rows, one file per site

This scan reads only public surfaces. It never submits a form, signs up, or logs in. The pack rots — llms.txt, agents.json and MCP conventions move monthly; treat a suite older than a quarter as suspect.