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

Multi-tenant SaaS in productionSport and recreationLive

Document and drawing intelligenceManufacturing and fit-outProof of concept

Adoption across a very wide user baseMembership and hospitalityIn build

Confidential records — isolation and auditHealthcarePrototype

Grounded retrievalEducationLive

Sheet W-01 · Multi-tenant SaaS in production · Sport and recreation

Live

One codebase serving several fully branded tenants with isolated data and role-based access, running in production.

Goes in
One codebase, one deployment, one owner console
What we built
The host decides which tenant you are, and every query is scoped to it
Comes out
Four branded sites, each with its own content, roles and members
The line it does not cross
No tenant can read another tenant’s data

Note 1 · The constraint

An operator running more than one site, brand or franchise usually ends up with a separate installation per customer. Every change then has to be made several times, and the copies drift apart within a year.

Note 2 · What transfers

This is the engineering that lets one system serve many customers, branches or franchisees without forking it per customer. A vendor portal, a dealer network or a multi-site operations tool is the same problem wearing different clothes.

Tenants live
Four
Automated tests
~1,290
Hosting
Oracle Cloud, Hyderabad
Tenant isolation
Per-tenant data scoping

Sheet W-02 · Document and drawing intelligence · Manufacturing and fit-out

Proof of concept

A multi-sheet drawing set becomes a priced bill of quantities in the format the tender already asks for, with unreadable lines flagged rather than guessed.

Goes in
A multi-sheet drawing set, exactly as the client sent it
What we built
Layout-aware extraction for the structured sheets, vision for the drawn ones
Comes out
A hierarchical bill of quantities in the manufacturer’s own tender spreadsheet
The line it does not cross
A line it cannot read is marked and left blank, never guessed

Note 1 · The constraint

A commercial estimator at a luxury interior fit-out manufacturer spends days reading client drawings before pricing can begin. Rushed bids lose margin. Slow bids lose the job. The company cannot install new hardware in the factory and cannot expose its ERP, so anything we build has to work from the files themselves.

Note 2 · What transfers

Any business that quotes from documents it did not author has this problem — tenders, specifications, schedules of work, supplier price lists. The reading is the bottleneck, not the arithmetic.

Stage
Proof of concept, in progress
Client
Anonymised
Inputs
PDF, DWG, DXF, XLSX
Integration
File in, file out. No ERP coupling.

Sheet W-03 · Adoption across a very wide user base · Membership and hospitality

In build

Court booking, dining, guests, directory and committee governance, built for a membership whose youngest user is nine and oldest is ninety.

Goes in
A noticeboard, a phone call, and a secretary who remembers everything
What we built
Booking, announcements, an open-play partner board, a directory and guest passes
Comes out
A member does it on their own phone — in large-text mode or kids mode if they need it
The line it does not cross
Each club is isolated by Postgres row-level security, not by application code alone

Note 1 · The constraint

A heritage private members’ club in Goa with more than 2,500 members runs on a noticeboard, a phone call and a secretary who remembers everything. Existing club software is priced for the United States and assumes members who will happily learn a new app. Most of this membership will not.

Note 2 · What transfers

The discipline that decides whether a shop floor, a depot or a field team actually uses what you commissioned. Most systems in this bracket fail on adoption rather than on features.

Members at launch club
2,500+
Client
Anonymised
Isolation
Postgres row-level security
Interactive demo
Available

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

Sheet W-05 · Grounded retrieval · Education

Live

A model held to a defined corpus, so it answers from the syllabus rather than inventing, and says so when the answer is not there.

Goes in
A student’s question, and one ingested, versioned syllabus corpus
What we built
Retrieval restricted to that corpus, so the answer comes from the chapter
Comes out
An answer out of the syllabus, on an installable web app
The line it does not cross
A question outside the corpus gets a refusal rather than an improvisation

Note 1 · The constraint

Students already use general chatbots for homework. Those tools do not know which syllabus a child is on, wander outside the chapter, and answer a Class 8 question at undergraduate level. On a shared family phone with a patchy connection they are worse than nothing.

Note 2 · What transfers

The control you need before a model is allowed to speak about your products, your policies or your prices. The mechanism that makes it refuse is the same one that keeps it inside your documentation.

Status
Live and public
Corpus
Defined and versioned
Out-of-corpus behaviour
Refuses
Delivery
Installable web app

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.