An estate pack is the schema, the field definitions, the confidence gates, the validation rules, the steward routing and a reference ground-truth set for one document estate — data and configuration, never code. It is added to any Forge licence, versioned separately from the runtime, and updated when the forms and the rules change.
Two ship today, each with a published field list and a version number. We would rather show you depth on two than maturity labels on seven.
The master fields for the industry's document families, mapped to your systems of record during onboarding.
Extractors already fitted to the document families in the pack; onboarding tunes them on your ground-truth set rather than starting cold.
Per-field confidence starting points your risk function adjusts, with the steward routing already wired.
Cross-field checks, party resolution against your masters, PII and PHI masking defaults for the industry.
When a form revision, a regulatory schema or a custodian layout changes, the pack ships an update.
Your tuned weights, your rules, your schema mappings and your records stay yours under the ownership guarantee.
Both packs are at v1.0.0 and both are on the changelog. Everything below is the specification you would receive — the schema, the fields, the gate defaults and the reference ground-truth set. Ask for the full field list and you will get the file, not a call.
Trust deeds, ACAT packs, held-away statements and onboarding packs, typed onto the household master — including the held-away positions that never got structured.
Broker submissions, SOVs, loss runs and FNOL packs typed onto your policy and claims master. The SOV that arrives as a spreadsheet inside an email inside a PDF is the normal case, not the edge case.
The five layers are sector-neutral — the runtime does not know or care what industry a document came from. What a pack adds is a schema someone has argued about, gate defaults a risk function has signed off, and a ground-truth set somebody labelled. Listing five more as “available” when none of that exists would be the kind of claim this site is trying to stop making.
| Estate | Document families | Status |
|---|---|---|
| Asset Management | LPAs, side letters, capital accounts, PCAPs, K-1s, credit agreements | On request |
| Real Estate | Leases, rent rolls, draw packages, diligence packs | On request |
| Banking & Payments | Account packs, loan files, KYB packs, remittances, disputes | On request |
| SMB Finance & Underwriting | Bank statements, ISO/MCA applications, merchant statements, tax returns — with governed cashflow analytics and credit decisioning | On request |
| Prime Brokerage | PBAs, ISDA schedules, lock-ups, give-ups, stock loan | On request |
| Private Banking | Onboarding packs, structures, source of wealth, Lombard credit, CRS | On request |
The underwriting engine behind the SMB Finance & Underwriting estate — transaction categorization, governed cashflow (revenue, ADB, holdback and advance detection), credit-policy decisioning with auditable reasons, and business-identity enrichment — already runs on the runtime, with every derived number traceable to its source transactions.
Schema mapping, gate setting and ground-truth labelling are already the three weeks of onboarding. For an estate without a shipping pack, that work produces the pack — same fixed price, same fixed end date.
The schema mapping, thresholds and eval set built for you are yours to keep, as data files, whatever happens to the commercial relationship.
Anything that generalises beyond your estate is promoted into a versioned pack for everyone, and appears on the changelog. Nothing becomes a branch of the runtime. The third and fourth shipping packs will be chosen by demand rather than by ambition.
A pack is added to a Forge licence as an annual line and co-terms with it. For an estate without a shipping pack, the three weeks of Fitting produce one — at the same fixed price, with the same fixed end date.
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.