Define the inputs
Use an agreed set of non-sensitive operational notes, not whatever happens to be available.
A team wants help preparing weekly operational briefs without losing the source trail or publishing unreviewed AI text.
FICTIONAL EXAMPLE · Northline Services
Open each fictional case to see the human gate and recovery response.
Input: Suitable notes with source IDs
Expected response: Draft cites each source; reviewer checks meaning; manager approves the exact version.
Input: A claim has no supporting measure
Expected response: Hold the claim and ask a question. Do not invent a figure.
Input: A sample contains a credential or identifiable record
Expected response: Stop, use the agreed handling path and resume only with a permitted source set.
Different staff were trying different prompts. No one could easily explain which source supported a statement, or who had reviewed the final brief.
Create a controlled sequence: collect suitable inputs, draft with source references, review uncertainty and approve the final version. Hold unsupported claims and retain the reason.
Use an agreed set of non-sensitive operational notes, not whatever happens to be available.
Assign a reviewer and require each material statement to point to its supporting source.
If a source is missing or contradictory, mark the item for review rather than filling the gap with plausible text.
The fictional download includes a use matrix, review checklist and three exercise cases for normal operation, missing evidence and an unsuitable input.
This is a fictional worked example. Any dates, decisions and outputs in the sample are illustrative.
Back to selected work & demonstrations
Tell us what you are trying to achieve. We can start with the next useful step.