Emit & Compound

What exactly is "the leak"?

Every business running on AI is learning things constantly — and losing almost all of it.

Someone corrects a bad AI draft. Someone works out the phrasing that gets replies. Someone catches the claim that would have caused a compliance headache. Each lesson lives in one person's chat history, one closed conversation, one head — and the next person, the next tool, the next week starts from zero. You're paying for the same lesson over and over. That's the leak.

The fix isn't a smarter model. It's a small process: one shared ledger where lessons land, a ten-minute weekly review where the owner approves the ones that matter, and a rules page every AI tool in the business reads before it works. Set it up once — with a spreadsheet and a doc, no code — and a correction made on a Tuesday binds every seat, every tool, permanently.

I run the fully-automated version of this every day (my rules file grew from three rules to six in a single working session, with nothing carried by hand). The pattern that makes it work is free below. If you'd rather have it wired into your business by Friday, that's a call.

One ledger row, so you can picture it

Jul 9 · AI draft review · claim · "Never quote a market stat without a named source — AI invented one that nearly shipped" · marketing · approved

Who this is for.

You run the business: founder, CTO, COO, owner, GM. You don't need AI that's smarter. You need AI that knows how you do things, does them your way, and still does them your way next quarter, in every seat, without anyone carrying the rules by hand. If you still see every rule your people give a customer, this is yours, whatever stage you're at with the tools.

Before letting AI near a customer, owners ask seven things: will my people use it, does it talk to our systems, does it sound like us and does a correction stick, can I trust it, is our data ours, what's the number, and who do I call. The home page answers each one with what runs today. The seven answers

Pick your leak

Sales
Your best rep's objection-handling line — the one that actually lands — lives in their head, and it leaves when they do. With the loop running: the line gets proposed to the ledger the week it's discovered, approved once, and every AI-drafted follow-up from every seat uses it from then on.
Support
A rep figures out the workaround for the billing glitch. The next rep rediscovers it from scratch — on a customer's time. With the loop running: the workaround is a status row the day it's found, and the AI answering support drafts already knows it.
Marketing
Your AI invents a statistic that sounds right. Someone catches it — this time. The rule that would stop the next one dies in that chat. With the loop running: "cite it or cut it" becomes a house rule every drafting session loads automatically. The catch happens once; the protection is permanent.
Operations
First-touch emails keep promising delivery dates ops can't always honor — because the person drafting them changed and nobody told the new one. With the loop running: the rule is in the rules page, the rules page is in every tool, and the promise stops going out — no matter who's drafting.

If it's a lesson someone learned and someone else will need, it belongs in the ledger. The full pattern — ledger, ritual, rules page, and the setup for your exact tools — is free.

Take the kit

The three artifacts the pattern needs, ready to copy. The ledger template as a Google Sheet (File → Make a copy and it's yours) or as markdown / CSV. The house-rules page template, with the loading instructions for ChatGPT, Claude, or a mixed shop built in. And the ten-minute weekly review checklist. No signup required — the kit is the pattern, not the paywall.

The gadgets

The pattern also runs as live software: small, sandboxed apps hosted at tools.edandhelen.com and handed out as Blueprints, not shared logins. You get the drawing and make your own copy; you never get our data and we never get yours. The instance is behind a gate while the first copies are finished, and the first Blueprint links arrive with the next post.

The ledger

The Emit & Compound ledger as an app instead of a spreadsheet: one six-column table (date, source, type, what we learned, tag, status), a weekly review where the owner approves, edits, or rejects each proposed claim, and a house-rules view that lists everything approved so every tool can read it. Built by describing it to the platform in one paragraph. A Blueprint copy is frozen the moment you make it: nothing flows from our copy into yours, and you change yours by asking.

StockSense

An inventory tool for a small operation: an append-only ledger of movements, stock computed from it rather than typed over, structured locations, first-expiry-first-out views for anything with a date, and a read-only assistant you can ask questions of. Writes go through a proposals panel, so approval is by design and by instruction: proposed, then approved, never assumed. Export is CSV. Same frozen-copy rule as the ledger.

Three cards explain what you will and will not get from a Blueprint copy.

Flow card one of three introducing the Emit & Compound gadget instance. Three doors on a hosted gadget instance: the gate decides who can reach the building; sharing lets someone work inside my copy, with my data; a Blueprint hands you the drawing so you build your own. Readers get the Blueprint door.
1/3 — Three doors. The gate is about who can reach the building at all. Sharing lets someone work inside my copy, with my data. A Blueprint hands you the drawing. Readers get the Blueprint door.
Flow card two of three: the frozen-copy rule. You make your own copy from the Blueprint and it runs as your own copy. When something is fixed in the original, your copy stays exactly as you have it; only the next copy carries the fix. No update ever flows from a Blueprint to an existing copy, which is why it has to be right before anyone copies it.
2/3 — The frozen copy. Nothing ever flows from the Blueprint into a copy you already have. That is a feature: nobody can change your tool under you, and you can change it as much as you like. It is also why the core has to be right before anyone copies it.
Flow card three of three: the designed return path, untested until the first stranger has a copy. A Blueprint is one-way with no telemetry, so lessons can only come back through a reader who copies the inventory tool, runs the ledger copy beside it, notes what did not work, and hits reply. The next Blueprint version would carry it forward.
3/3 — The return path. A Blueprint is one-way and I get no telemetry. The only way a lesson gets back is you running the ledger beside the tool, noting what did not work, and hitting reply. Your records never move; only the lesson does. This is the design; it is untested until the first stranger has a copy.

How I work with businesses: /work

The Library: /library