Scott Morris

Privacy as architecture.

If your project touches payroll, medical or payment records, this is how that data gets handled. It is the part of the work that does not show up in a demo.

Local inference only

Retrieval and generation on hardware you own. No third-party model calls, no documents leaving your network, no API key to leak.

Read-only by default

Analysis runs against read-only mirrors. Write access is a deliberate, separately authorised exception, never ambient and never blanket-approved.

Suppression at the source

Sensitive columns are withheld server-side, so the client cannot render what it was never sent. Enforced in the query, not requested in a prompt.

Grounded or silent

Answers cite the record they came from, or the assistant says it doesn't know. No confident invention over a company's own data.

Secrets stay out of reach

Credentials read from the environment, never written to disk, never committed, never echoed into a log or a working file.

Verified, not reported

Vendor consoles report what they were told. An estate audit turned up a whole class of hardware running with no endpoint protection, because the dashboard said "not applicable" instead of "failed".

Less surface, not more

A hosted asset platform replaced with a self-hosted one and the internet-facing service decommissioned, removing its credential surface along with it.

Knowing when not to

Some capabilities get declined. Rooting a vehicle head unit would have unlocked a feature and risked an unrecoverable device; the feature wasn't worth it. Restraint is a security position.

Nothing exposed

Private-mesh networking instead of public endpoints. If a service has no reachable front door, it has no front door to attack.

Tell me what you need

Back to the work