Every customer runs the same Gothink AIR runtime at the same version — this page is the whole history of that artifact, kept public because it is very hard to maintain a per-customer branch and a public changelog at the same time.
Released 20 September 2026, extended 21 September — a stated accuracy contract, Gothink Witness, the self-evolving Business ontology, the MCP tool plane, the AIR Playground and a redesigned IMR.
Because inventing a version history would be the first dishonest thing on this site — the engineering predates the tag, but everything from 1.0.0 forward carries a date and a diff, and the number in your control plane matches the number on this page.
Semantic versioning — a major changes a schema contract or API shape, a minor adds capability, and a patch fixes behaviour; two majors are supported at any time.
| Version | Date | What changed | Action needed |
|---|---|---|---|
| v1.0.6 Current |
20–21 Sep 2026 | Accuracy contract: ≥ 99.5% precision on auto-published fields (α = 0.005), and no value publishes without a page reference; 13 new algorithms. Gothink Witness (formerly Hallmark): vendor reliability without ground truth, system autonomy from reviewed outcomes, examiner portal. Business ontology. MCP tool plane with a receipt on every call. 21 Sep: the AIR Playground — source agent, amendment detection, local MCP/RAG repository, internal/external labels, exports — IMR redesigned with export, and the self-evolving Business ontology — changes scored against the version in force, approved by a person, every version reversible. | none — drop-in |
| v1.0.5 Superseded |
15 Sep 2026 | Decision layer: per-vertical decision engines returning a decision, its reasons and its citations — credit, claims, trade, KYC, wealth, contracts and AP — with typed agent tool schemas and a decision benchmark leaderboard. Self-improvement flywheel (measure → detect drift → retrain → re-measure) with a dashboard. Partner/ISV JSON API, pack marketplace and shared update stream, OEM white-label profile. Operations admin with per-client service and action toggles. Security hardening: CSRF protection and per-client rate limiting on by default, TLS, encryption at rest, hashed client passwords, signed session tokens. Adds the ap_accounting estate pack. |
none — drop-in |
| v1.0.0 Superseded |
6 Sep 2026 | First publicly versioned release of the Gothink AIR runtime. Five-layer pipeline, confidence gates, steward routing, field-level lineage store, command centre, connector library, and the eval harness exposed as a product surface. Deployment profiles for gothink Cloud, customer VPC and air-gapped install from one image. | none — baseline |
A pack is data and configuration — schemas, field definitions, confidence-gate defaults, validation rules, steward routing and a reference ground-truth set — never code, so it can move without a runtime upgrade.
| Pack | Version | Date | Status |
|---|---|---|---|
| Wealth Management Trust deeds, ACAT packs, held-away statements | v1.0.0 | 6 Sep 2026 | Shipping |
| Insurance Submissions Submissions, SOVs, loss runs, FNOL packs | v1.0.0 | 6 Sep 2026 | Shipping |
| Other estates Asset management, real estate, banking, prime brokerage, private banking | — | — | On request |
When a layout defeats a classifier or a threshold is set wrong, the shape of that failure informs the next pack — and no customer’s documents, values or corrections are involved. How that works, and how to verify it →
Reporting requirements and standard forms change on published schedules, and a schema that lags one is an operational problem with a deadline — pack releases land ahead of the effective date, and each entry names the change.
Known schema changes affecting the shipping packs, with their effective dates and targeted releases — maintained whether or not you are a customer, because publishing a date is how you can hold us to one.
Get the change calendarFeature releases quarterly — security and correctness patches whenever they are ready, not held back for a release train.
Two major versions are supported at any time — breaking schema or API changes are announced twelve months ahead.
gothink Cloud upgrades on a published schedule; in your VPC or air-gapped, you promote the image when your change process says so.
Every release is scored against the eval set your experts labelled before you promote it — an upgrade that moves your accuracy is a fact you see, not one you discover.
Images and packs are signed — verification happens inside your boundary and does not require a call home, including on the offline channel.
Your configuration, records, lineage and corrections are yours permanently. What lapses is new versions of this page. The full answer →
Twenty-five documents, your labels, a number we did not generate. The runtime that scores them is the one on this page.