Changelog

What shipped, when.

A public log of what we've added, expanded, or refined on the ArthurAI™ marketing site. The site evolves alongside the platform; the changelog makes the cadence visible.

This log covers the site. For the platform itself — what shipped across the editions and ArthurAI™ Studio — see the platform release notes. Deeper detail than either page carries comes through your engagement.

  1. August 29, 2026

    The AI capability figure is re-derivable, and the Dawn Directive count reads from one source

    • arthurgrid.ai publishes “50+ AI capabilities”. Thirty-three of them were counted from ArthurAI-V2-UnifiedSystem, a tree that is not deployed anywhere — verified three ways: no running container uses any image it builds, its image names do not exist in the registry, and its build project has no pipeline definitions at all. The figure was true and its evidence was not, so the evidence was replaced rather than the number lowered: the deployed backend now has 32 AI capabilities itemised and machine-verified behind a blocking gate, and ArthurAI Studio’s deployed backend carries 26 more. The right answer to weak evidence for a true claim is better evidence, not a quieter claim.
    • The Dawn Directive™ course and hour counts are now read from a single constant rather than restated in Studio page copy, so the programme figures cannot disagree between pages.
  2. August 27, 2026

    Foundation-model names removed from the home page, coverage cited beside the claims

    • Foundation-model names had leaked onto the ArthurAI home page. Naming the model underneath is barred on customer surfaces — the customer-facing label is the Eve engine, not the vendor model — and the home page is the most-read surface on the site. Removed, and the branding gate that should have caught it was widened so the same class of leak fails the build rather than reaching production.
    • Independent coverage is now cited beside the partnership claims rather than the claims standing alone. A wire release and independent editorial are different kinds of evidence, and a reader should be able to tell which one is being offered.
    • The MindHYVE family card carried IPSC figures from the March v3.0 build and published them as current.
  3. August 20, 2026

    Edition status reconciled, portfolio statement corrected

    • Edition status is now stated one way. Five editions carried “In market” while FLE carried “Generally available”, and /capabilities renders that field — so the same page showed six generally-available editions labelled two different ways. All six are generally available: CLE, SLE, VLE, ULE, FLE and PLE, alongside ArthurAI Studio. GLE, HLE and ALE remain on the roadmap. This completes the correction started on August 12, which noted “five, of six” still to go.
    • The shared portfolio statement said “four editions in production — ten across the roadmap”. That conflated editions with Digital Employees — the same sentence then says “four … Operating Systems” — and understated the portfolio, since ArthurAI alone has seven generally available. It now reads twelve generally available across four Operating Systems, with the arithmetic recorded in the canon file so it can be checked rather than trusted. Authored here and copied verbatim to the other three grid sites.
    • The /about/founding timeline’s “Today” entry was out of date on three of four products — it described four ArthurAI editions in market and JustineAI in field trial. It now matches the current status of each.
    • Two build gates added: one fails when page copy restates an edition status instead of reading it from the source of truth, the other warns when the published capability census or this changelog goes stale. The second one is why this backfill exists.
    • Added the canon:hash script. The canon drift check had always failed with “regenerate the manifest with pnpm run canon:hash” — and that script existed in none of the four grid repositories, so the one instruction the failure gave could not be followed.
  4. August 17–19, 2026

    Claim accuracy pass, capability census on the page, guardrail hardening

    • Every named-partner verb and published figure was checked against its source, and deploy claims on the home page and /about/deployments were rewritten to name the instrument behind each engagement rather than flattening different agreements into one word.
    • The /capabilities page now carries the capability census counts, read from a single source so the page, the machine-readable corpus and Eve cannot diverge.
    • A self-description as an “assistant” was removed from the ULE faculty-of-record copy. Arthur is a Digital Employee that reasons and drafts for an educator to review.
    • The Eve Digital Employee widget now loads from chat.eve.mindhyve.ai — one Eve across every MindHYVE site.
    • Guardrails: a pull request that carries commits from a do-not-merge pull request now fails; the canonical copyright notice is checked; and a single NUL byte could previously switch the guardrails check off, which it no longer can.
  5. August 16, 2026

    A WAF in front of the site, machine-readable capability corpus

    • A web application firewall now sits in front of the arthurgrid.ai Front Door, and its desired-state definition was reconciled with the live prevention posture so the two cannot silently diverge.
    • /llms.txt gained a Capabilities section carrying the exact census counts, so an AI crawler reads the same numbers a buyer sees.
  6. August 11–12, 2026

    FLE generally available, processing-entity rewrite, route-aware brand gate

    • ArthurAI FLE published as generally available rather than “in market” — the first of the six.
    • The /trust pages were rewritten to describe the processing entity accurately rather than as a SKU, and a press correction was landed alongside it.
    • The brand gate became route-aware, so it understands which surfaces may name a specific third-party platform component and which may not — customer copy uses the Eve-Education™ F5/reasoner label.
  7. July 31, 2026

    Share cards, contact-API storage posture

    • Brand-forward social share cards generated across the whole site.
    • The build now fails if the contact API’s storage is left publicly reachable — a posture guard rather than a one-time fix.
  8. June 19, 2026

    Bias architecture on the record, CIAI relationship corrected, one-typeface system

    • Responsible AI page expanded with a “how we handle bias” section grounded in the portfolio canon: you cannot train bias out of a model — you separate the reasoning from the knowledge from the jurisdiction, so the bias becomes something you can read, audit, and govern. We describe population-free reasoning plus runtime steering; we never claim the system is “unbiased.”
    • CIAI relationship corrected sitewide: CIAI is an independent customer of ArthurAI™ VLE, not a MindHYVE subsidiary, sister company, or family member. The Dawn Directive page, the home page, and the “Dawn Directive as vertical infrastructure” insight were all updated to remove the subsidiary/sister/family framing.
    • Typography unified to a single typeface — IBM Plex Sans across display, body, and italic — matching the MindHYVE Brand Bundle canon now shared across all five sites.
    • Shared portfolio canon refreshed: the cross-site “bias is architectural” sentence added, and the portfolio statement updated to “four editions in production — ten across the roadmap.”
  9. May 17, 2026

    Trust Center backbone, How-it-works depth, audience hubs, edition deeps

    • Trust Center expanded with 6 new pages: Security FAQ (30-question FAQPage with Schema.org markup), Subprocessors (counsel-grade list of every third party that touches institutional data), Responsible AI (pre-LLM and post-LLM guardrails, logging discipline, human-in-the-loop posture), Accessibility Conformance (WCAG 2.1 AA posture, VPAT availability), Data Processing Agreement summary, Incident Response (severity classification, notification cadence, runbook).
    • How-it-works trio added: the Learning Cognitive Profile deep dive with academic lineage (Felder-Silverman, Kolb, Sweller, Kirschner) and explicit calibration against the strong-form learning-styles hypothesis; the 6-step lesson flow anatomy; the AI tutor architecture; assessment architecture.
    • Edition deeps shipped: SLE safety-and-disclosure with parent communication kit and state-AI-disclosure-law landscape; ULE faculty-of-record posture with accreditation alignment; CLE SOC 2 readiness narrative.
    • New audience hubs: For Parents (plain-language coverage of what the platform does and what rights parents have), For Procurement (single landing page aggregating DPA, security FAQ, subprocessors, accessibility conformance, audit rights), For Press (boilerplate, fact sheet, founder bio, brand assets, story angles).
    • Brand and positioning: Why ArthurAI (the ten posture statements that define what the platform refuses to be), Student Data Rights (plain-language FERPA / COPPA / state-law / GDPR coverage), K-12 Funding Sources (Title I / III / IV-A / IDEA / ESSER / state / philanthropic landscape).
    • Footer cleaned: 9 dead-link footer entries from the original IA replaced with live pages. The footer now links to every published page.
  10. May 16, 2026

    Capability pages and audience-lane narratives

    • 4 capability pages shipped, one per shipping edition: SLE, ULE, VLE, CLE, each with 8 capability cards calibrated to the audience and grounded in the V1.7 product spec.
    • 4 audience-lane narratives: Your day with SLE (K-12 teacher), Your semester with ULE (university faculty), Your program with VLE (vocational instructor), Your quarter with CLE (corporate L&D leader).
    • First-month onboarding playbook for educators new to the platform.
    • Per-edition partner evidence cards added to /sle, /ule, /vle, /cle drawing from the verified institutional-partner roster.
  11. May 17, 2026 (earlier)

    Brand system, font swap, icon refinement

    • Body font swapped to IBM Plex Sans (replacing Inter) for editorial character; restricted to 400 and 500 weights to preserve the editorial register.
    • Icon mark tight-cropped: created icon-mark.svg with viewBox bounded to the medallion (preserving the original icon.svg with safe-zone padding for lockup compositions). Icon at 56px in the nav reads at ~2.5x effective vs the original full-padded 40px.
    • Wordmark color system aligned to the v6.1 SVG colors: charcoal ‘Arthur’, gold ‘AI’, taxonomic-grey ‘TM’ superscript.
  12. May 17, 2026 (earlier still)

    Initial production deploy

    • Site provisioned on Azure: rg-arthurai-marketing-prod / swa-arthurai-marketing-prod (Standard tier) / appi-arthurai-marketing-prod (Application Insights) / law-arthurai-marketing-prod (Log Analytics).
    • Azure Front Door Premium fronting the Static Web App: afd-arthurai-marketing-prod with WAF, custom domains arthurgrid.ai (apex) and www.arthurgrid.ai (www) created and validated.
    • AFD endpoint live at ep-arthurai-marketing-prod-b7eqdwfwegg7fub2.z02.azurefd.net. DNS cutover from Wix to AFD pending founder go/no-go.
    • Initial 27-page IA shipped: home, 5 edition pages (sle / ule / vle / cle / ple), 4 trust pages (compliance, security, data-handling, disclosures), 4 technology pages, 3 about pages, contact, pricing, how-it-works, for-educators, resources, 3 legal pages.