Examples of
local AI tasks.
These written examples illustrate the document and project-file workflows we’re designing. They are reference examples for planning an evaluation.
Compare two versions of a report.
A revised report arrives, and you need to know what changed before passing it on.
A request to start with
Compare report-old.pdf and report-new.pdf. List the changed conclusions and cite the passages. Flag anything the new version removed.
Use the comparison to decide which changes deserve a closer read.
Follow up on a particular passage
The first answer may leave you with a question. Ask why two passages differ, or request a short summary you can edit for a colleague.
Open the referenced passages when a conclusion matters.
Understand code you didn't write.
You've inherited a repository and need to change how it handles labels.
Ask for an explanation first
Find where labels are normalized. Explain how the value moves through the code, then propose a change that makes labels lowercase.
The explanation helps you find the relevant files before working on the patch.
Work from the proposed diff
A diff gives you specific lines to discuss. If the explanation doesn't fit what you see in the repository, ask about that file before changing it.
Treat proposed code as a draft and run the project's tests before using it.
Make a checklist from written instructions.
The launch plan lives in a project brief and meeting notes. You need a checklist someone can edit.
Ask for a checklist draft
Turn Project brief.pdf and meeting-notes.md into a checklist. Cite the source for each step. Add the owner when one is named, and mark missing owners or dates as unknown.
The proposed file could be launch-checklist.md.
Use the draft to fill in the gaps
A checklist can expose what the source never said. If a step has no owner or date, leave it unresolved until someone supplies that detail.
The draft still needs to fit your team's procedure before people use it.
Continue from the draft.
Ask a follow-up
You can narrow the question to a passage or file, or ask for another version of the draft.
Save or apply the result
If the task proposes a file write or command, you decide whether to allow it before it runs.
These written examples describe planned workflows on Apple Silicon Macs, with separate approval intended for optional external providers.
Tell us what you'd like to try.
DEFENSE FIRST. PRIVATE WORK ACROSS SECTORS.
Start with your team's work.
Technical knowledge, even when disconnected.
Evaluate approved manuals, document versions and source-linked answers on your actual Macs.
Defense workflows →02 / GOVERNMENTFind the policy behind an answer.
Work through approved policies and administrative records with a clear source and review trail.
Government workflows →03 / LEGALWork from your own matter documents.
Evaluate supplied-file questions and contract-playbook comparisons with professional review.
Legal workflows →