Field notes
Documents and workflow automation
Document work can support a decision or complete a task, from filling a form to preparing an invoice. These guides cover source records, access boundaries, exceptions and the review needed before the next action.
Start with the guides below on preparing documents for retrieval, preserving access permissions, and deciding how much human review a workflow needs.
Reading
Guides in this collection.
How enterprise RAG works across two pipelinesEnterprise RAG is two pipelines running on different clocks, an ingestion pipeline that builds and refreshes the index and a query pipeline that serves. Most failures live in the gap between them, and treating retrieval as one request path hides all of them.8 min readRead
How much of my team's time will checking the AI take?Compare preparation, review, correction and sign-off time with the manual baseline. Mandatory review can still save time; unattended processing needs its own evidence and approval policy.6 min readRead
How to evaluate AI invoice processing before ERP integrationJudge invoice automation by correctly accepted records, a usable exception queue and reliable ERP posting.6 min readRead
How to preserve RAG access controls end to endEnforce access rules across indexes, embeddings, caches, logs and evaluation data. Test permission changes at every retained copy, not only the user-facing query.9 min readRead
Related systems
What we build here
Working on this
Putting this into practice with your team?
Send your name and work email. We will come back with what we would check first and whether it is worth building at all.
or email us directly athello@calquity.com
