Whitepaper · Foundations
The app is the easy part. The foundation is not.
An app can be generated in an afternoon. What it stands on cannot. This paper collects documented incidents where apps leaked data, overreached, stopped scaling or went unmaintained, and shows the layer each one was missing.
What it covers
The incidents happen in the foundation.
None of the incidents in this paper were failures of a model or an interface. They were missing foundations: an access check, a credential, a storage setting, a sync, a patch. Every app built from scratch has to get each of those right on its own. Build the foundation once and put every app on it.
- Layer 01
Your app
The easy part
- Layer 02
Models
Tools that act as the user
- Layer 03
Permissions
Checked per record
- Layer 04
Graph
One copy of the data
- Layer 05
Connectors
Synced from your systems
- Layer 06
Hosting
Servers, keys, backups
Chapters
Seven chapters, from leaks to the supply chain
01 · Page 03Chapter 01
The app is the easy part
What every app built from scratch has to rebuild.
02 · Page 06Chapter 02
Where data leaks
Open buckets, default passwords, keys in the browser.
03 · Page 09Chapter 03
Where assistants overreach
Prompt injection, oversharing, agents in production.
04 · Page 12Chapter 04
Where it stops scaling
Dual writes, stale permissions, throttled connectors.
05 · Page 15Chapters 05 · 06
Maintenance and the supply chain
Retired models, aging dependencies, hijacked packages.
06 · Page 21Chapter 07
Build the foundation once
What it must give every app, and how to test it.
Your data. Your infrastructure.