Example Spaces
Plain-language building blocks to discuss with Pat. These examples are not live tool access.
Document intake and OCR
Availability: blueprint example. This article describes a possible workflow. It does not provide a live upload tool or promise that a specific document format is supported. The job Turn scanned pages or document files into text and a small set of fields that a person can review. | Part | Example | | --- | --- | | Input | A synthetic scanned form or document file. | | Output | Extracted text, selected fields and a link back to the source. | | Human review | Check uncertain text, field values and missing pages before accepting the result. | | Possible next step | Add the reviewed record to an approved system or make the text searchable. | Where it can help The useful part is reducing repetitive copying and making the source easier to work with. OCR reads visible text; it does not by itself decide whether a document is correct, complete or suitable for a particular decision. Questions to settle Which file types and languages matter? Are pages handwritten? Do you need tables or only a few fields? How long should the source be retained? Who can open it? How will duplicates and failed jobs be handled? Ask for a preview with a synthetic sample before treating the workflow as available for your own material. Follow the intake walkthrough or bring this building block into your solution brief.
Search your own knowledge
Availability: blueprint example. This article describes a possible tool, not a connected search service. The job Find useful information in an approved collection and show the source behind an answer. | Part | Example | | --- | --- | | Input | A question and a collection you are allowed to search. | | Output | Relevant passages, source links and an optional draft answer. | | Human review | Open the source and check whether it supports the answer. | | Possible next step | Use the reviewed result in a report, procedure or draft response. | What makes the result useful The collection needs clear ownership, access permissions and a process for updates or deletion. Search should respect those permissions. An answer should say when the available sources do not support a confident response. Questions to settle Where do the files live? Who should see each collection? How fresh must the result be? Can the source be linked directly? What should happen after a source changes or is removed? You can combine this idea with document intake, but extraction and search solve different steps. Agree on the contract between them using the connection walkthrough.
An everyday planning assistant
Availability: blueprint example. This article is a planning example, not access to a hosted assistant. The job Turn a collection of notes into an organized draft you can use and change. | Part | Example | | --- | --- | | Input | Your notes, constraints and a description of the result you want. | | Output | A checklist, comparison, outline or draft plan. | | Human review | Check facts, priorities and whether the plan fits your circumstances. | | Possible next step | Copy the reviewed result into the calendar, document or task system you already use. | Work, personal productivity and leisure The same pattern can help prepare a weekly planning outline, organize a home project, structure research for a hobby, or compare options for a creative project. Start with drafting and organization. Taking an external action—such as sending a message, making a booking or spending money—needs its own connected tool and explicit decision. Questions to settle What information should the assistant remember? What should it forget? Which sources does it need? What is a helpful output format? Which actions should always remain with you? Use the first-workflow guide to keep the initial version focused.