Drawing register

Proof, framed by what it demonstrates

A club platform is multi-tenant SaaS engineering. A drawing set becoming a priced bill is document intelligence. Read these for the engineering underneath rather than the industry on top, because the industry on top is the part least likely to be yours.

Five pieces of work: two live, one in build, one a prototype and one a proof of concept. Nothing here is described as more finished than it is. What each word means.

Sheet: A-01
Title: Work
Issued for: Information
Drawn by: Snilld

W-04Clinical practice prototype

Confidential records — isolation and auditHealthcarePrototype

Sheet W-04 · Confidential records — isolation and audit · Healthcare

Prototype

A working prototype of the isolation and audit design needed where confidentiality is contractual rather than optional.

Goes in: A session note, in a practice that cannot treat records casually
What we built: Per-tenant scoping, encrypted notes, and an append-only audit trail
Comes out: A record whose history can be shown rather than asserted
The line it does not cross: A correction is a new entry. Nothing is overwritten.

Note 1 · The constraint

An independent practice carries a documentation burden but cannot accept a tool that treats patient records casually. The interesting question is not whether a model can draft a note. It is whether the surrounding system can prove who saw what, and when.

Note 2 · What transfers

The same design applies wherever confidentiality is a contractual obligation — legal files, HR records, financial casework, anything covered by a data processing agreement.

Stage: Prototype. Storage simulated.
Audit model: Append-only
Isolation: Per-tenant scoping
Not claimed: Production security

The full write-up →

Legend

How to read this register

Four status words and two rules. The words are load-bearing: each one is a claim about how finished something is, and we use them literally.

Live: Running in production and used by people who are not us. If it says live, you can look at it.
In build: Being built now, with a client, against a date. Some of what is described is working and some of it is not finished.
Prototype: Demonstrates a design rather than carrying real load. Where the stored state is simulated instead of a production database, the facts panel says so.
Proof of concept: Proves the hard part works on real inputs. It is not a product and it is not in production.
Clients: Anonymised. No client is named unless they have given written permission, so most entries describe the organisation rather than naming it. The constraint and the engineering are described exactly as they are.
Numbers: No accuracy or confidence figure appears anywhere on this page, because none has been measured under conditions we would be willing to publish.

W-04Clinical practice prototype

Note 1 · The constraint

Note 2 · What transfers

How to read this register

Two of these are platforms we operate