The typed-number check
No figure in a MonoBridge report may be typed in by hand. A check traces every one to the engine and fails the build if one can’t be traced.
No number typed by hand
Every dollar figure, percentage, multiple and large number in a MonoBridge report has to come from the engine. None may be typed in by a person, not even a well-meaning one. A check runs every time a report is built and fails the build if a single figure can’t be traced.
Try it
Below is a sentence built the way the report builds sentences. Every figure in it is highlighted green because the check found where it came from. Now type a number in by hand and watch what happens.
The concluded value is $3.93M, inside a range of $3.48M to $4.31M. Normalized EBITDA is $530,150 on $2,650,000 of revenue, and the discount rate is 15.4%.
That’s the same thing the report does to itself: it plants one typed figure, $1,234,567, and prints the result. The check finds it every time, which proves the check can fail.
What counts as a source
A figure traces if it came from one of these, and only these:
- The report’s own number formatters, fed by the engine’s output
- Strings the engine writes, such as the notes on each lens and the diagnostics
- The industry dossier’s landscape data and the driver trees
- The plan’s content: its steps, titles and the starting points and targets of each measure
The plan’s reasoning prose is held to a stricter rule: it may not contain a literal figure at all. Its numbers are placeholders that the engine fills in when the report is built, so the words and the arithmetic can never drift apart.
Why it matters to you
A report that someone can edit by hand is a report someone can shade. This check means the number on the page is the number the method produced from your inputs, every time, and anyone with the same inputs gets the same page.
- Pattern. Dollar amounts, percentages, multiples and comma-grouped numbers are tokenized from the page text and the chart annotations
- Allowed set. Everything emitted by the report formatters plus engine, scorecard, diligence, landscape and tree strings, plus the plan’s content fields; quotations of the input file are not a source
- Failure. Any token outside the allowed set fails the build; so does an unresolved placeholder
- Proof it can fail. A render with $1,234,567 injected into the prose must be caught by the lint and by the in-page count
See it on a real report, or see it on yours.Download a sample reportSchedule demo