# Estate Agent

> The standard for AI agents working across your repo estate. An open standard for using AI coding agents across many repositories: one context file per repo that every assistant reads, a cross-repo service map built from API contracts rather than parsers, guardrails that block credential access at execution, and a repair loop that keeps it all true. Runs locally, zero dependencies, MIT licensed. Version 0.1.0.

## Documentation

- [The five levels](https://mutaaf.github.io/estate-agent/levels.md): How far you have adopted, from nothing to self-maintaining — in plain language, with what each level costs and what is still wrong at it.
- [Start here](https://mutaaf.github.io/estate-agent/start-here.md): Install Estate Agent and set one repository up in about fifteen minutes: detect the stack, write the deed, install the guardrails, generate the context files.
- [In plain English](https://mutaaf.github.io/estate-agent/plain-english.md): What Estate Agent does, with no jargon and no prior knowledge assumed.
- [The estate map](https://mutaaf.github.io/estate-agent/estate.md): How Estate Agent works out which service calls which, across ten languages that share no package manager.
- [Tiers](https://mutaaf.github.io/estate-agent/tiers.md): Deciding per repo how much autonomy an AI agent gets.
- [Self-healing](https://mutaaf.github.io/estate-agent/self-healing.md): Why these notes do not rot, and the four rules that stop self-repair becoming self-damage.
- [What data goes where](https://mutaaf.github.io/estate-agent/data-flow.md): Exactly what Estate Agent reads, writes, and sends. Written to be forwarded to a security reviewer unedited.
- [Monorepos](https://mutaaf.github.io/estate-agent/monorepo.md): Setting up a repository that contains many packages, plus the satellite repos around it, without the context files duplicating each other.
- [Should your team do this?](https://mutaaf.github.io/estate-agent/adoption.md): The costs, the benefits, and what failure looks like.
- [Adding a language](https://mutaaf.github.io/estate-agent/adding-a-stack.md): Teaching Estate Agent a new stack. One YAML file, no code.
- [Field-testing it](https://mutaaf.github.io/estate-agent/field-testing.md): Running Estate Agent against real repositories, finding what it gets wrong, and reporting that without leaking anything.
- [Inside an existing initiative](https://mutaaf.github.io/estate-agent/interop.md): What Estate Agent covers, what it deliberately leaves to humans, and how to use it as a component of a documentation or knowledge-graph project you already have.
- [Glossary](https://mutaaf.github.io/estate-agent/glossary.md): Every term defined, including the ones the industry uses carelessly.
- [Worked example: a cross-repo change](https://mutaaf.github.io/estate-agent/workflows/cross-repo-change.md): One realistic API change followed end to end across five consumers in five languages.
- [Specification v0.1.0](https://mutaaf.github.io/estate-agent/spec.md): the normative definition — deeds, tiers, the resolution ladder, evidence requirements, landing order, self-healing constraints.

## Source

- [Repository](https://github.com/mutaaf/estate-agent): MIT licensed, standard-library Python.
- [AGENT.md](https://github.com/mutaaf/estate-agent/blob/main/AGENT.md): installation instructions written for an AI agent to follow.

## Key concepts

- **Deed**: `.agent/estate.yaml`, the single source of truth per repo.
- **Estate**: all your repositories taken together.
- **Resolution ladder**: declared > dependency > env > host > path.
- **Blast radius**: everything that breaks if you change one thing.
- **Ship cost**: how many release cycles you must support an old API shape for; zero for a service, roughly two for a mobile or TV app.
- **Tiers**: 1 restricted, 2 reviewed, 3 autonomous.