01
Legal
Privilege is a design constraint.
Matter files, correspondence, and work product stay in the environment we design. The model comes to the records. Nothing is sent to a public trainer.
Who this is for
If the real files cannot leave.
This is for any practice that cannot put its actual work into a public model. The four below are where we start — examples, not a closed list.
The test
If you have privilege, client IP, confidential work product, or operational records that must stay inside an environment you control, you are in scope. Title of the firm is secondary. The constraint on the files is the brief.
Among them
02
Architecture
Drawings and client IP stay on the board.
Specifications, models, and correspondence are the firm’s and the client’s. Those files are not used to improve someone else’s weights.
03
Consulting
Client-confidential work product remains yours.
Decks, analyses, and working files do not leave the system. Agents and language modules are built to how the firm already writes.
04
Small business
Operations data is not a public prompt.
Customer lists, pricing, and internal documents stay data-resident — for owners who cannot put the real numbers into a consumer chatbot.
And others
Accounting, engineering, family offices, research shops, and firms we have not named yet — if the files cannot wander, the same system applies. We do not publish a catalog of verticals.
Describe the records. We will say whether we can keep them where they are.
If this is your constraint
You do not need to fit a label. Tell us what cannot leave.