A behaviour policy for everybody the lead talks to

The lead's request of today (D18↗): after a conversation, hand a new agent a zip, a website and a sentence, and get back an Agent Behaviour Policy vault about that person's organisation, to send them as a demo they can correct and try. The objective this quarter is users, and a behaviour policy about them, sent the day after, is an invitation to the product's first action.

• The brief↗ sets out three vaults. The UI the lead asked for already exists: it is the app vault that every behaviour policy loads its renderer from, so a better UI reaches every person's vault at once. A private keys vault holds every person vault's write key and the lead's notes. One vault per person holds only what that organisation publishes about itself, dated, so that publishing one later is a decision rather than a clean-up. The brief also lists what the feedback loop is meant to learn.
• The pack is kept in the repository at packs/dist/, not on the site. It holds the agent's instructions, templates, a scaffolder and a gate that must pass before any push. The gate fails on another person's name, organisation or keys; anything shaped like a vault or write key; a run of seven words from the lead's private notes; an email address; or a personal LinkedIn link. It was proved against six planted leaks. The first version missed a paraphrased note, which is why it compares word runs rather than lines. The pack carries this site's own vault builder and every catalogue deployment's inputs, so the agent runs exactly what the site runs. It is deterministic, it refuses anything write-shaped, and CI fails if it goes stale.
• One fictional example inside the pack was built and checked end to end: a small analytics consultancy on the reserved example.org domain, with Claude's Gmail connector.

What was not done: no keys vault exists yet. The first session creates it and gives its key to the lead, so the steps are exercised once with the lead watching. No real person's vault has been made. A person corrects their vault by replying to the lead; a way to do it from inside the vault is a question for the app vault.