Quickstart, deployment guide, architecture reference, schema and API reference, the connector library and the support policy. Full operator documentation ships inside every release bundle; this page is the public index. Docs are how you verify that software exists, so this page is public and does not sit behind a form.
This is the shape of a deployment, not a substitute for the operator guide in the release bundle. Steps one to four are the platform team’s work and take a day or two; steps five and six are what the three weeks of Fitting exist to do properly.
| Step | What you do | What you end up with |
|---|---|---|
| 01 Pull the image | Pull the signed runtime image for the version on the changelog and verify the signature locally. No call home is required, including on the offline channel. | verified image, v1.0.0 |
| 02 Install | Helm chart, containers with compose or OpenShift, or the offline bundle. Same artifact in every case; the install profile differs. | runtime and control plane up |
| 03 Apply the licence file | A signed file, checked locally. It carries your tier, your volume band and your entitled packs. | entitlements resolved |
| 04 Install the estate pack | The versioned pack for your estate: schema, field definitions, gate defaults, validation rules and the reference ground-truth set. | schema loaded, e.g. wm.v1.0.0 |
| 05 Point the connectors | Sources, masters and targets from the released connector library, under credentials you issue. Configuration, not code. | estate reachable |
| 06 Set gates and score | Your risk function sets per-field thresholds; your experts label a ground-truth set; the eval harness scores the run against it. | typed records, cited and scored |
EKS, AKS, GKE or self-managed. Namespaced install, your ingress, your secrets manager, your object store for the page cache.
The same images, pulled from a registry you mirror. GPU nodes optional; CPU-only extraction profiles are supported at lower throughput.
A signed tarball with images, charts, models, packs and a licence file. Applied with the bundled installer; verified against a public key you pin at first install.
The Kubernetes path with region and residency constraints enforced in the chart values, for regulated estates on a national or sector cloud.
A namespace or cluster, an identity provider integration, object storage, a database, network reach to your sources and targets, and a licence file.
Reference profiles for 10k, 100k and 1M pages a month are in the operator guide. The control plane reports throughput and queue depth so you can resize.
| Component | Runs | Stores | Talks to |
|---|---|---|---|
| Ingest connectors | In your boundary | Page IDs, source references | SharePoint, mailboxes, scan queues, object stores, APIs |
| Clean & classify workers | In your boundary, GPU optional | Canonical copies, candidate fields | Models deployed with the runtime |
| Govern service | In your boundary | Confidence, lineage, steward queue, corrections | Your identity provider, your party and product masters |
| Serve API | In your boundary | Typed records, audit trace | ERP, CRM, master data, RAG index, agent tool schemas |
| Control plane | In your boundary | Accuracy trend, drift, licence state, release inventory | Your monitoring stack via OpenTelemetry |
| Licence file | Read locally | Tier, expiry, packs, signature | Nothing — no outbound call |
Every connector is released, versioned and patched with the runtime. Missing one is a request under the Extend tier or an onboarding item.
New connectors are scheduled quarterly under Extend, or scoped into onboarding. Either way they join the library and are maintained under the licence.
Every value Forge asserts carries the evidence for itself. That is the whole shape of the contract: a field, a value, a confidence, and the file, page and region it came from. Full reference documentation ships in the release bundle; this is the part worth reading before you install anything.
Every extracted field carries a confidence score and a lineage reference to file · page · region. A field that could not be asserted above its gate is present and explicitly abstained, never silently absent and never guessed.
A pack ships a named, versioned schema — wm.v1.0.0, ins.v1.0.0. Breaking schema changes are a major version and are announced twelve months ahead.
Fields your systems of record need but the pack does not carry are added as schema entries during Fitting. They are configuration in your deployment, and they do not fork the pack.
Read typed records, resolve the lineage behind any field to its source page, list and act on the exception queue, and submit a steward decision. Authenticated under your own IAM.
Fire on abstention, on steward decision and on record promotion, so your workflow systems react to a gate rather than polling for one.
Submit a labelled ground-truth set and score any release against it — the same surface the evaluation uses. Regression-test an upgrade before you promote it.
Both receive security patches. Feature releases land on the current major only.
Dates appear on this page and in the control plane. Sovereign-tier licensees receive a named upgrade window.
Pack updates ship on their own cadence, driven by form and rule changes in the industry.
Included in every licence. Severity-based response targets are in the licence agreement.
Priority response on Enterprise; 24×7 for severity 1 with a named security contact on Sovereign.
No patches, packs or support — but nothing switches off. That is the ownership guarantee.
Onboarding is where the reference architecture meets your estate.
Twenty-five documents from your own estate, labelled by your own experts. Free, no contract, and you keep the report either way.
Schema mapping, confidence gates and a ground-truth set, at a fixed price with a fixed end date. Exit at the pilot gate having paid the first milestone only.
Go live on the licence with the tuned weights handed over. Releases, packs and support carry on from there.