UDT Insights
Practical perspectives on technology, engineering, and delivery.
Applied AI
Readable OCR text can still misstate an invoice amount or detach a table value from its label. Select checks around business-critical fields, document layouts, and review queues before allowing extracted information into downstream decisions.
Read article
Applied AI
Updating a source file does not finish an answer update. Define how revisions, withdrawals, and access changes move through extraction, indexing, and answer caches, then test that obsolete material can no longer support a response.
Read article
Applied AI
A review button is not an approval process by itself. Specify who authorizes each consequential action, what they inspect, and how the system prevents a changed proposal from using an earlier approval.
Read article
Applied AI
Retrieved files can contain instructions that conflict with a user’s request. Treat those files as untrusted evidence, restrict connected capabilities, and test what happens when hostile text appears inside otherwise useful business material.
Read article
Applied AI
A useful answer test starts with the work employees must complete. Build reference cases that specify evidence, permitted variations, and required refusals, then use them to compare changes without rewarding fluent but unsupported responses.
Read article
Applied AI
Semantic search cannot settle disagreements between outdated procedures. Prepare a small, accountable document collection first, then test whether retrieved passages preserve the conditions employees need to answer real business questions.
Read article
Security and Privacy
A shared platform needs evidence that one customer organization cannot receive another’s records through ordinary features or operational shortcuts. Test tenant context across queries, files, jobs, caches, and support access before widening access.
Read article
Security and Privacy
Privacy controls should not depend on every browser script loading successfully. Review the initial response, embedded resources, consent defaults, and server behavior so a failed script does not expose content or activate avoidable collection.
Read article
Security and Privacy
Session expiry should reflect the sensitivity of the task and the way customers work. Define idle and absolute limits, protect unfinished work deliberately, and verify that the server refuses an expired session even when browser scripts fail.
Read article