How Wickline decides what to cite
Passages, support scores and the one rule that keeps unsupported sentences out of answers. Plus what changed when tables inside scans became citable.
How it reads, why it cites the way it does, and what changed this month. Written by the team, checked against the product.
Passages, support scores and the one rule that keeps unsupported sentences out of answers. Plus what changed when tables inside scans became citable.
Scanned tables rebuilt cell by cell, and a confidence note on faded pages.
A plain list of every record Wickline stores about you, and how long each one lives.
The checks our own support team runs when a customer says "that looks wrong".
How we split, queue and index files so the first answer doesn't wait for the last file.
Artifacts leave the app with headings, tables and citations as footnotes.
Tokens are our cost. Questions are what you actually do. The meter should match the work.
Release notes and the occasional long read. Nothing else, ever.
Part of the Design Systems Library