Every customer runs the same Forge runtime at the same version. This page is the whole history of that artifact — what shipped, when, and what changed. It exists partly so you can verify the claim underneath it: it is very hard to maintain a per-customer branch and a public changelog at the same time.
Released 6 September 2026. This is the first publicly versioned build. The pipeline underneath it has been running for longer than the version number suggests — what changed on this date is that it became one tagged, released artifact with notes attached, rather than a deployment.
Because inventing a version history would be the first dishonest thing on this site. The engineering predates the tag. The tag does not predate itself. Everything from here forward carries a date and a diff, and the number in your control plane will match the number on this page.
Ingest, clean, classify, govern and serve ship together in a single signed container image. There is no configuration in which a layer is a separate purchase or a separate upgrade.
Per-field thresholds, the exception queue, named-approver routing and the full audit trace. Thresholds are set per deployment as configuration; the mechanism is identical everywhere.
Score any release against a ground-truth set your own experts labelled. Exposed as a product surface in this version, which is what makes scoring us before you sign possible at all.
File, page and bounding region behind every extracted value, queryable through the API and clickable in the command centre.
gothink Cloud, customer VPC and air-gapped install from the same image with a different runbook. The offline update channel is part of this release, not a fork of it.
Per-page model routing bounded by your accuracy floor, realtime cloud and token metering attributed to document family and queue, and spend forecasting as a distribution. Ships in the runtime at every tier rather than as a licence. What it does →
Source, master and target connectors as released, versioned components. Which ones you point where is configuration set during Fitting.
Semantic versioning. A major version changes a schema contract or an API shape; a minor adds capability without breaking either; a patch fixes behaviour. Two major versions are supported at any time.
| Version | Date | What changed | Action needed |
|---|---|---|---|
| v1.0.0 Current |
6 Sep 2026 | First publicly versioned release of the Forge 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. It is never code, which is why a pack 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 turns out to be set wrong, the shape of that failure informs the next pack — a new validation rule, a revised gate default, an added field. Every customer gets it. No customer’s documents, values or weights 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 attached. Pack releases are timed to land ahead of the effective date, not after it — and each entry names the change that prompted it.
Known schema changes affecting the shipping packs, with their effective dates and the release each is targeted for. It is maintained whether or not you are a customer, because it is useful either way and 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, and they are 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 of the release that makes them.
On gothink Cloud we upgrade on a published schedule. In your VPC or air-gapped, the image is yours to promote when your change process says so.
Every release is scored against the eval set your experts labelled, on your estate, before you promote it. An upgrade that moves your accuracy is a fact you see rather than 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.
The weights, records and lineage 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.