adoptlisted

# Adopting the method into a project *Carries out rules A1, A2 and C1. The [catalogue](https://github.com/nanatsusaya/agent-driven-development/blob/main/method/rules.md) is the authority; this file is only the procedure.* Adoption is a proposal, not an installation. What the method looks like here is a decision about how this project will be worked, which puts it squarely in the human's domain. **Guardrails (do not violate):** - **Propose, do not impose.** Present the bindings and adaptations you intend and get a decision before writing anything. - **Do not invent roles the project does not have.** A project with no decision records should get an adaptation, not a new empty directory. - **Do not copy a rule you cannot justify here.** A rule applied where its reasoning does not hold costs the same and buys nothing, and the wasted effort teaches everyone that the method is bureaucracy. - **Never claim the check passed without running it.** ## 1. Read the project first Before proposing anything, find out what this project actually is: - What is it, who is it for, and what would make it a failure? Scale, correctness, legal exposure and longevity each pull the rules in a different direction. - Does it have code and a build chain, or is it a body of documents? - How long has it been running, and how many sessions has it seen? - What already exists: an operating-rules file, decision records, a status document, any kind of log? - Is there already a `method.json`?