Working notesGuides
Not product notes. These are the questions we end up answering in evaluations and handover meetings — record-level access control, what owning generated code actually means, and the tools nobody approved — written out properly so we can point at them.
What row-level security is, the three places teams put record-level rules, why the ones written in application code eventually leak, and the checks that tell you whether yours actually holds.
Ownership, readability and portability are three separate questions hiding inside “do we own it”. What the law is unsettled about, what the contract decides, and the exit test that answers it in practice.
Read itWhy departments build their own systems, which risks are real and which are theatre, how to find what exists without starting a witch hunt, and how to make the sanctioned path faster than the unsanctioned one.
Comms
These are written from what we run into, not from a keyword list. If your experience says otherwise, we would genuinely like to hear it — and if you have a question none of them answer, ask a person.
