Field coverage
Where each value goes in Conduit
Updated
The model only extracts facts into a fixed list of value kinds. A separate, hand-maintained mapping table decides where each kind goes for each request type. The model never decides where a value goes.
PR: purchase request. CR: change request (changes to an existing purchase order). SR: sourcing request (Procurement finds the vendor). ER: emergency request.
Pending aggregation
The coverage map is built after the last scored round, from every document in the corpus.
What is already decided
| Read from the document | PR | CR | SR | ER |
|---|---|---|---|---|
| Vendor name | Matched to the vendor list; "Vendor is not listed" starts vendor setup | Not used (vendor comes from the PO); flagged if different | Into the notes | Matched, as PR |
| Line items | Request lines | Change lines | Summarised into "What do you need?" | Not mapped in v1 |
| Subtotal | Check only | Check only | Available budget | Approximate spend |
| Tax and total | Check only; Conduit computes tax | Check only | Not used | Not used |
| Payment terms | Suggested terms, confirmed by the user | Not used | Not used | Not used |
| Quote or invoice number, date | No field yet (open question) | No field yet | Into the notes | No field yet |
Preview from the field map. Final counts and destinations replace this table once aggregation runs.
Coverage map
Units seen
Units printed on line items. Units that Conduit's list does not have yet are an open question for the client.
Currencies
Conduit budgets are in CAD. Documents in another currency will be flagged.