Changelog

What shipped, when.

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

This log covers the marketing site. Platform release notes — clinical app and API changes — are published per edition at CDS release notes and OM release notes.

  1. August 30, 2026OM

    The AI capability floor comes down, 160+ to 75+

    • Itemising OM’s AI layer as data made the number re-derivable. It did not make it customer-facing, and nobody had asked the second question. Of the 165 anchored entries, 87 are the Foundry client, retry and backoff, embedding calls, OCR, prompt-version constants, streaming-versus-blocking transports of one analysis, queue job types and controller surfaces. 78 are things a customer gets. 160+ was an overclaim for two days and the floor is now 75+, with the total moving 800+ to 700+.
    • Every registry entry now carries a customerFacing decision and, where it is excluded, a one-line reason — judged against the same four rules used for CDS, so the two products are comparable. The build refuses an entry that has not been classified, so the next capability cannot be added without someone deciding on the record which side of the line it is on.
    • The reachability rule found ten entries with no production call path, four of which would have been published as capability had the classification been done from their names. The starkest: a section-summariser whose prompt is imported only by a test, in a code path that returns “no summary” unconditionally. Nothing about the product changed this week. The instrument did.
  2. August 29, 2026Platform-wide

    Two published figures corrected against their own instruments

    • The MindHYVE family card said ArthurAI has four editions in market. It has five. The card was written before the fifth shipped and nothing recomputed it, which is the shape of error a hand-maintained figure produces even when every individual page is right.
    • The exact behind OM’s “160+ AI capabilities” moved from 166 to 165 — and it went DOWN because the instrument got stricter, not because the product lost anything. The anchored registry that backs the figure grew two rules: it now rejects anchors that resolve in any file and therefore prove nothing, and it rejects two entries citing the same evidence. Sixty vacuous anchors were re-anchored and one double-counted prompt asset was removed. The published floor is unchanged.
  3. August 28, 2026OM

    The AI capability figure became re-derivable, and the floor moved to 160+

    • OM’s AI capability count had been the one published figure no command could reproduce. It came from a prose itemisation in a full read — named behaviours like ex-parte taint propagation — and reading the code back gave 1,748, or 14, or 54, or 98 depending on the lens, none of them the published number. It is now itemised as data, every entry anchored to a file and a pattern that must exist, behind a blocking gate whose self-test perturbs all of them to prove the matcher is live. The number is the length of that list rather than an assertion about it, and the floor moves 130+ to 160+.
    • The OM release-notes page was missing the August releases. They are published.
  4. August 27, 2026CDS

    The capabilities page showed a human half of what the machine feed carried

    • /cds/capabilities rendered 37 named capabilities from a page-local narrative arranged as a clinician’s day, while /cds/llms.txt rendered 82 from the capability index. Same product, same site, two inventories — and the one a human reads was less than half the one an AI crawler ingests, under a headline claiming 275+. The full inventory now renders above the workflow walkthrough from the same constant the machine feed uses. The narrative stays; it is the better way to meet the product, but it is no longer the only thing a visitor can see.
    • Five capabilities were added that had been shipping unmentioned: automated-decision preferences under California consumer-rights law, in-product help that checks the service before answering, monthly usage visibility, subscription and billing administration, and the clinician credential profile.
    • Two routes were deliberately not marketed, both because reading the code contradicted what the route name suggested. One is compiled out of production entirely and is not a customer capability at all; the other is operator payment configuration rather than a customer surface.
  5. August 27, 2026OM

    The site caught up with the product: four figures and a whole subsystem

    • Forty-five feature commits had landed since the last full read, including the DWC reporting workflow, the QME med-legal surfaces and the entire records-disclosure subsystem. The published floors had stopped being conservative and started being wrong in the understating direction. Features move 570+ to 600+, and the records-disclosure surfaces are published as a thirteenth capability group — a document library, production packets with Bates numbering, an honest manifest of superseded and duplicate pages, a withheld log, and productions that can be voided without destroying the record that they happened.
    • Seventeen shipped capabilities that no page mentioned were added to the index.
    • One page was publishing two different numbers for background automations, because two surfaces each restated the figure instead of reading it. Both now read the same constant.
    • A confidence band claimed a re-derivation date that four of its numbers had not earned. The date now describes only what was actually re-derived on it.
  6. August 27, 2026Platform-wide

    Corpus and disclosure corrections

    • The machine-readable corpus told every model that a generally-available product was pre-launch. An engineering file had become the thing contradicting the site, and a crawler reading it would have propagated the contradiction rather than the correction.
    • The MindHYVE family card carried IPSC figures from the March v3.0 build and published them as current.
    • Foundation-model disclosure scoping was synced from the ArthurAI canon, so the rule about where a model name may appear is stated identically across the family rather than drifting per site.
    • Independent coverage is now cited beside the California Northstate claim rather than the claim standing alone, because a wire release and independent editorial are different kinds of evidence and a reader should be able to tell which one is being offered.
  7. August 22, 2026OM

    Four California clinical pilot evaluations published

    • Four California practices treating workers’-compensation patients have executed Clinical Pilot Evaluation Packages for ChironAI OM — thirty-day, no-fee evaluations in live clinical operation, each with a HIPAA business-associate agreement in force before any patient record is entered. None of it appeared anywhere on the site. They are published on the deployments page as a third category, kept distinct from institutional partnerships because the warrant is different: the institutional partners are named under a press release issued against a signed MOU, while these four are named solely because each gave the written publicity consent their agreement requires.
    • The content-security policy allowlist dropped a host this site does not use.
  8. August 20, 2026Platform-wide

    Edition status reconciled, partnership language throughout

    • OM is stated as generally available since August 12, 2026, and the edition page now carries that date the way the CDS page always has. The status had been published three different ways — the nav said one thing, the site metadata another, and body copy on the gallery a third — because two separate fields held the same fact. The nav badge is now derived from a single source, so the three cannot drift apart again.
    • The footer now reads “In strategic partnership across three regions,” matching the Trust Center and the three-regions page rather than asserting a harder verb than they do. Dated press-release descriptions of specific engagements are unchanged; they name their own instrument.
    • The OM capability corpus no longer describes the product as pre-launch — a line that had become the engineering file contradicting the site. It now states, as the CDS corpus already did, that it describes capability only and that availability is stated on the site.
    • This log gained edition tags and a filter, and the twelve entries below it were backfilled from the shipping history between June and August.
  9. August 19, 2026OM

    OM landing page rebuilt

    • The /om landing page was rebuilt around the five jobs a California workers’-comp visit actually asks of one physician, bringing the edition to the same depth as the CDS lane.
  10. August 19, 2026Platform-wide

    Guardrail hardening

    • A pull request that carries commits from a do-not-merge pull request now fails the guardrails gate rather than quietly inheriting them.
    • The canonical copyright notice is checked by the carry gate.
  11. August 17, 2026Platform-wide

    Instrument-accurate claims, full sitemap, Eve widget

    • Deployment claims on /about/three-regions and /about/founding rewritten to name the instrument behind each engagement rather than flattening MOUs, alliances and collaborations into one verb.
    • Foundation-model names across /insights and /resources rewritten to the customer-facing Eve-Healthcare F5/reasoner label.
    • Sitemap coverage restored — twenty-six pages were missing from it, so they were not being offered to crawlers at all.
    • The Eve Digital Employee widget now loads from chat.eve.mindhyve.ai, one Eve across every MindHYVE site.
    • A single NUL byte could switch the guardrails check off. It no longer can.
  12. August 16, 2026OM

    OM capability corpus published

    • The OM capabilities page now publishes the full customer-facing capability count, re-derived from the live codebase rather than restated, and the figures are read from one source so the page, the machine-readable corpus and Eve cannot diverge.
    • Counts are published as floors against exact census figures. A floor survives diligence; an exact number invites a line-by-line audit of every item.
    • A machine-readable corpus is served at /om/llms.txt for AI crawlers, with a groups-at-a-glance list and a canonical page URL.
  13. August 16, 2026CDS

    CDS capability corpus published

    • A machine-readable CDS capability corpus is served at /cds/llms.txt, matching the OM corpus in structure.
    • The corpus states plainly that it describes capability only and makes no deployment, adoption or customer-count claim — availability is stated on the site, not asserted in the corpus.
  14. August 12–14, 2026Platform-wide

    Naming discipline and a mobile layout canary

    • Third-party foundation-model names scoped to approved surfaces only, and language overstating the generality of the system removed from customer copy.
    • The brand gate is now route-aware and understands which surfaces may name Microsoft, Phi and Azure.
    • A mobile layout canary was added and immediately found four live defects on narrow viewports. All four are closed and the ledger is empty.
  15. July 31, 2026Platform-wide

    Consent model, share cards, narrow viewports

    • Analytics moved to a CCPA opt-out consent model.
    • Brand-forward social share cards generated per page.
    • The editorial rule no longer overflows on narrow viewports.
    • A format check was added to PR validation so unformatted edits cannot reach a deploy.
  16. July 29, 2026Platform-wide

    Privacy and legal accuracy

    • Contact-form input is redacted from session replay. Free-text on a healthcare contact form can contain health information, and session replay is not a place for it.
    • Legal pages corrected to describe what we actually do: the terms no longer promise a fourteen-day refund we do not give, and the billing contact is an address that can receive mail.
    • First-touch attribution captured on contact leads.
    • A PR-validation pipeline was added so branch protection could be enabled at all.
  17. July 19, 2026Platform-wide

    Lead handling made durable

    • Transactional email standardised on one provider, removing a second delivery path that could fail independently.
    • Dead-letter capture added, so a lead that fails every delivery attempt is retained rather than lost.
    • Contact and waitlist notifications moved to a branded renderer, and leads land against discrete fields rather than a free-text blob.
  18. July 3–6, 2026Platform-wide

    Agentic operating system repositioning, product gallery

    • The home, how-it-works, CDS and OM lanes were rewritten to lead with the agentic clinical operating system rather than a feature list — Chiron drives the encounter and shows its reasoning; the physician reviews and attests.
    • Residual lab-trending feature claims purged from the site: they described something the product does not do.
    • A public product gallery was added for both editions, on synthetic demonstration data and labelled as such.
  19. July 2, 2026Platform-wide

    Trust Center build-out

    • Trust Center gained SOC 2 Trust Services Criteria controls, a subprocessor list, incident response and availability sections.
    • The frontier-model data-handling statement was reworded to match the controls actually in place, removing an unbacked de-identification claim.
    • A secret-scanning gate was added to the production deploy pipeline.
  20. June 21–27, 2026Platform-wide

    Agentic showcases, brand canon corrections

    • Reasoning showcases published for both editions, so the agentic behaviour is shown rather than described.
    • Canonical Digital Employee spelling corrected across brand canon.
    • Substrate hero treatment on the home page.
    • Lead-API key comparison made timing-safe, and reliance on a long-lived directory secret reduced.
  21. June 19, 2026Platform-wide

    Bias architecture on the record, Africa region, edition parity

    • Trust Center now carries a “how we handle bias” section in the portfolio voice: 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.”
    • Africa region corrected: the region now hubs from Nairobi. Kadisco General Hospital — our customer — remains in Addis Ababa, Ethiopia, and its deployment content is unchanged.
    • CDS and OM edition framing equalized across the site so both editions read with the same depth and structure.
    • 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.”
    • Added this public changelog and wired it into the footer.
  22. June 18, 2026Platform-wide

    Single-typeface system

    • 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 MindHYVE marketing sites.
  23. June 17, 2026Platform-wide

    Frontier-component abstraction + format gate

    • Third-party frontier model names abstracted on customer surfaces; Microsoft, Phi, and Azure remain named, and customer copy uses the Eve-Healthcare F5/reasoner label.
    • Added a Prettier format:check stage to CI so unformatted edits can no longer reach a deploy.
  24. June 6–8, 2026Platform-wide

    Deploy hardening

    • Unknown routes now return a real 404 (removed the Static Web App navigation fallback that was producing soft-404s).
    • Single-hop trailing-slash redirects; hardened a handful of broken links and asset hrefs.
    • Contact routes for legal, privacy, and security moved to @mindhyve.ai role addresses.
  25. May 30, 2026Platform-wide

    Team, legal, Eve-Genesis

    • Added a /team page and retired /about/leadership; team data synced.
    • Standardized commerce policy pages under /legal/* (terms, privacy, refunds, cancellation, acceptable use, promotions).
    • Eve-Genesis page gained the cognitive-fingerprint and riddle-origin reveal.
  26. May 20, 2026Platform-wide

    Share-card coverage fix

    • An audit found 43 of 44 pages were shipping imageless share cards — only the apex emitted an og:image. A centralized social-metadata helper restored 100% Open Graph / Twitter card coverage across every page.
  27. May 13, 2026Platform-wide

    Initial production deploy

    • chirongrid.ai launched on Azure Static Web Apps behind Azure Front Door.
    • Two editions live: CDS — Clinical Decision Support (GA) — and OM — Occupational Medicine — built first for California workers’-compensation physicians.
    • Information architecture: Editions dropdown, six-column footer, Trust Center, Technology (Eve-Healthcare F5/reasoner), and the For-physicians lane.