Mistakes: what went wrong before, and why

Each entry: what happened, why, what fixed it, what it teaches, and the source. Read 16 November 2026. People other than Dinis are not named; agents are named by role.

1. The push to main: a rule that failed because it was only a rule

2. Every policy ran in observe mode, with no end date

3. Two emails signed "Dinis"

4. A policy that lagged the work

5. Agents with no policy at all

6. The keeper is also the auditor

7. A check that runs only where the agent chooses

8. Policies written, never agreed

9. Written the same way? Not yet

10. A gate that disagreed with our own names

11. Smaller ones, with the same shape

DateWhatWhyFixSource
3 NovA vault key printed into a transcripta guide recommended a command that prints itvault replaced; rule never to print a vault keyABP in action
4 NovAn agent overwrote another agent's key entry from a stale copyany agent could change any entryseal.mjs refuses cross-account changes, within about three hoursAn inbox only your agents can write to
2 to 6 NovThree agents' prompts were copies of the conductor's, and committed as the conductorcopied promptsfixed in two stepsABP in action
3 NovAn agent sent calendar invitations itself"never send" was unclear about invitationsopen: a person decides what counts as sendingABP in action
7 NovModel keys and a send token in a shared cloud environment reached every sessionenvironment variables are sharedopen; one environment per agentABP in action
16 NovThe site factory's pipeline holds organisation-wide repository admin, including deletea token cannot name a repository that does not exist yetproposed: brokers and narrow tokensCI behaviour policies

This page is generated from index.md, its Markdown twin.