How this was built

The rules this system runs on had been in the owner’s head for years: how storage gets billed, how costs are split when several people own the goods, how consignment is settled, which items actually move, what happens to the exceptions. He could state the rules. He could not turn them into something an outside software vendor could build.

The blocker was never budget. The vendors did not understand how pet retail and warehouse accounting actually run, and after a few rounds what came back was unusable. Domain knowledge does not transfer.

What changed in 2026 was not the idea. It was the tooling. The owner does not write software. What he can do is explain one thing clearly — and that turns out to be the skill this kind of work needs.

The specification had been ready the whole time. From the first line of code to launch: three days.

The two squads do opposite jobs. One makes the thing stand up. The other makes it possible to see.

• The two squads work apart. Neither can see the other’s files.
• They meet at exactly one point — going live — and only one side can do it. That is not rank. Going live cannot be taken back, so it has to pass someone who can see the whole.

These are not obedient tools. They say “you are wrong”, and they bring the evidence. All three of these are on the record.

• A member was told which file to edit. It made the edit, then insisted on opening the actual page and reading it back. Its report: “That layer is dead for this case. If I had not read the page back, this round would have shipped a result that passed every check and was invisible online.”
• A member read a line the lead had written and pointed out that it broke the honesty rule the lead had set one paragraph later. It then split the two facts into separate fields — every fact kept, the implication cut.
• The lead scheduled six jobs and said they could all run at once. The other squad checked and came back: four of the six sit on the same file, so that is one after another, not six in parallel. The lead had it wrong. He changed it.

The same mistake both times: could not see it, so said it did not exist.

First, he said the warehouse contract set no limit on items and no liability terms. He had read only the summary. The contract itself had been there all along.

Second, he said none of the four suppliers had signed a storage agreement, because the folder held only price lists. The owner ended it in one sentence: a price list is an attachment to a contract.

Both times he reasoned about the whole from whatever happened to be in front of him. That lesson is now a working rule: before saying something does not exist, ask where it would be if it did.

It is the first thing people ask before handing over stock. The answer cannot be “we take data security seriously”. That sentence has no opposite — nobody labels themselves careless.

There are 81 checks that test this and nothing else, and every one of them is a pair: your own account finds your rows, and another account has to find zero. Drop either half and “cannot see it” starts passing for “safe”.

It is enforced where the data is kept, not by hiding the screen. Hiding the screen is one address away from not being enforced at all.

On 24 September 2026 someone who had taken no part in building it signed in to the live site on a guest account and went screen by screen through the workbench, the product list and the file cabinet. No real customer or supplier name appeared anywhere.