Follow an answer back to its sources.
Choose a question, change the sample context and inspect the records behind the answer.
SYNTHETIC DATA · This illustrates the experience. It is not a live engine response or a customer result.
What could change if we remove the rounding exception?
Review both the calculation and reporting services. The v4 fallback preserves a recorded contractual behavior, and the reporting interface depends on its result. Removing it requires checking the affected contracts and consumers.
What is missing
Retain the legacy rounding exception
Decision record · document archive · 2019-02-28
The v4 calculation path retains line and document rounding to preserve existing contract behavior. Remove the fallback only after the affected customers have migrated.
We wrote this synthetic record so you can check the example against its source.
This example has no supporting source. The answer identifies what is missing.
Read the record behind each claim.
We wrote these examples to show how answers link to records and state their limits, gaps and review status. The confidence bands are illustrative; we have not measured them on a live system.
The release selector switches between these examples. A real integration needs to verify which historical queries work and how releases map to deployments.
How the platform creates and serves knowledgeTry the approach on your own product.
A pilot uses the actual engine and your records to test a task your team needs to complete.