SureThink/Product/Pillar 03
Pillar 03 · Structured output, graded
A confidence percentage tells you how sure a model is. It does not tell you what to check. So every figure we extract records how it got into the file — and that is something an underwriter, a credit committee and an auditor can each act on.
Ordered by how much of the pipeline’s own judgment went into the answer. The first two pass on their own. The last two are the whole reason a person is still in this process.
Lifted off a page, character for character, and cited to where it sat: document, page, and for a spreadsheet the sheet and cell. No interpretation happened.
work_in_progress
$1,284,900
FS_2025_audited.pdf, p.14
✓ passes without review
Computed from figures that were read, with the formula recorded beside it. If you disagree, you are disagreeing with arithmetic, not with a model.
working_capital
$612,400
Computed: current assets − liabilities
✓ passes, arithmetic visible
The figure was never stated. The pipeline read prose and formed a view it cannot cite to a line. This is where extraction tools quietly guess, and where this one stops.
contingent_liability
~$184,000
Low confidence · note 9, prose
⚑ routed to a named signer
Not in the file at all. The memo prints the gap where the figure should be, rather than leaving a blank that reads like a zero.
surety_history_3y
[not found: surety history]
listed in Gaps · asked for
⚑ completeness gate fires
A worked example
Every figure is a link back to the page it came from, and every memo ends with a Sources appendix listing them. Here is one case with the appendix opened out: the structured summary on the left, the page it was read from on the right.
7 read · 2 derived · 1 inferred · 1 absent — file held at station 03 for a named signer
Costs incurred on uncompleted contracts to the reporting date totalled $1,284,900, against progress billings of $1,102,300. Retentions receivable at year end were $214,700.
The Company has provided indemnity in respect of two subcontractor performance obligations on the Site B contract. No provision has been recognised as the directors consider the likelihood of call remote.
pipeline · note 9 states no figure
inferred ~$184,000 from the Site B
contract value in the same file
⚑ cannot be read — held for a person
What happens at the threshold
This is one setting on one station, and it decides how much of your day the pipeline gives back. Most teams start strict and loosen it once the record earns it.
| Grade | What the pipeline does with it | Who sees it |
|---|---|---|
| read | Passes straight through. The figure and its citation go into the file. | nobody — it’s evidence |
| derived | Passes, with the arithmetic recorded so a reviewer can check it later. | nobody — it’s arithmetic |
| inferred | Stops the file. The case parks in the tray of whoever’s authority covers it, with the prose the pipeline read attached. | a named signer |
| absent | Fires the completeness gate — the broker is asked for it before the file goes any further. | back to source |
Set it the other way and inferred fields pass with a flag instead of a stop. Set it stricter and derived fields need a second pair of eyes too. What you cannot do is make the grade disappear — it travels with the figure into the decision record, so the auditor sees the same thing your underwriter saw.
What comes out
The moment the last signature lands, the downstream work happens without anyone remembering to do it.
credit_summary.json
Every field, its value, its grade and its citation — as data your systems can read, not a PDF someone has to re-key.
“work_in_progress”: {
“value”: 1284900,
“grade”: “read”,
“cite”: “FS_2025#p14”
}
memo.pdf
Drafted from the structured file, citing the rules that drove each finding. It starts written instead of blank, and the citations survive into the final version.
8 sections drafted
11 figures cited
1 flagged for the author
ready to edit
POST /webhook
Pushed to your policy admin or core system the moment the second signature lands — with the grades attached, so downstream knows what was inferred.
POST /bonds/4471
202 accepted
✓ obligations set
✓ calendar updated
Start with one workflow
Thirty minutes, one real submission, redacted however you need it. You'll see which fields it reads, which it derives, and which it will not stand behind.