The working environment

A place every AI session runs inside.

Memory that loads itself, rules the agents must follow, hooks that make it happen without me remembering, and verification before anything touches a customer or a dollar. It exists so nothing has to be explained twice and every session compounds on the last.

It is not only mine. The people with product context, not engineers, do the roof labeling that trains our model, and the website copy was written in house by the people who own the message; both work inside the same rulebook. The same pattern runs a second, smaller vault for a family business.

How it is built Walk the vault

The same method, in a small business

A rental business runs on software I built and operate.

A family member manages about 50 rental properties. The app I built runs the business end of it: rent expected against rent received, leases, bills, tenant history, and collections flags, from a phone. AI does two jobs inside it, both fenced: it reads a messy spreadsheet and proposes rows a person approves one by one, and it answers questions over the ledger without ever inventing a number. Access is scoped by organization, vendor costs are capped in code, and every automated job writes to an audit table.

It is the enterprise rollout in miniature: identity, data governance, cost control, and a human in the loop, on a system a real business depends on every day. A household finance assistant with a local model that cannot see real account data, and a second memory vault, use the same approach.

See the builds