05 · Ethics, review, and the rules of use
A governance project names what the model may do.
Adoption fails when nobody knows which tools are allowed, what may be pasted into them, or who answers when an output is wrong.
The problem we are hired to fix
Staff are already using public tools with client and patient material. A policy PDF that nobody follows does not change that.
What the project builds
- A short rule set. Allowed tools, banned inputs, and the review a human owes before something leaves the building.
- A register of systems. What you run, what it touches, and who owns the outcome.
- Review gates on the work itself. The rule shows up in the workflow, a required approver, not only in a handbook.
How the project runs
Four phases. You approve the shape before we build it.
- 01 · Listen
Where material is already leaking
We interview the teams using AI today and list the data types that must never enter a public tool.
- 02 · Shape
Rules people can remember
A few pages, with examples from your work, written with counsel or compliance if you have them.
- 03 · Build
The gate
We place one approval step on the riskiest workflow so the policy is visible in the work.
- 04 · Hand off
An owner
A named person reviews new tools. We leave the register and the questions they should ask.
The line we do not cross
- We do not replace your counsel or your compliance officer.
- A policy is not a certification.
- We will not write rules that pretend a model is accountable. A person is.
If this is the work, schedule a consultation.
Discovery is free. Website scoping is a paid hour and is credited if the build starts within 30 days.