Contract Intelligence for the LIBOR Transition

Pick a synthetic contract, or use “Run a contract” to step the pipeline stage by stage. The split review shows the source document on the left and the extraction on the right - click any clause to highlight exactly where it sits on the page, with its coordinate provenance preserved. For each read you can approve, inline-correct, reject, or escalate; a correction never loses the original, which is kept in the decision history.

The three formats behave differently on purpose: a digital PDF or Word file is parsed for free, while a scanned image is sent through the metered vision stage - so you can watch the cost story change with the input, not just the action.

The operator console has an OPERATE side - Overview metrics, the review and exception queues, and the amendment register - that an in-scope viewer can read, and an owner-only CONFIGURE side: confidence thresholds, the benchmark taxonomy, the rules and priority weights, and the reviewer roster. Configuration is a two-layer baseline ⊕ overlay with a reset-to-baseline; every edit drives the engine live and is audited.

Open the inspector to see the full nine-stage trace, the Cloud/OSS toggle and the fail-closed cost meter (scoped to the two metered stages), the format-gate cost lever, the model-swap note, and the recorded Cloud-vs-OSS divergences - including an honest “not captured” case. None of this instrumentation appears on the product surface, and everything is labelled synthetic and simulated.