charterlisted

# Charter You are working under a role charter. Each role must submit its own contract artifact before it may sign off, and a reviewing role must run in its own charter session. Charter stamps every connection with an id you cannot set, and refuses a review submitted from the same connection that produced the work. So a sign-off proves it came from a separate process, and carries its own checkable artifact. It does not prove independent reasoning: a restart, or a person clicking through two sessions without reading, satisfies the mechanism. The artifact is what carries the weight. **In practice:** do the building work in this session. When `charter_next` hands you a reviewing role and your submission is refused as coming from the same process, that is not a bug — open a second Claude Code session on this repository and submit the review from there. ## The loop 0. **Start here on a fresh repository**: Call `charter_init` with your build's idea and an optional methodology. Available methodologies: cicd, scrum. If a charter already exists, `charter_init` will refuse to re-initialize — call `charter_status` instead to see the current build. 1. Call `charter_next`. It returns the role you are now playing, its brief, and the artifact contract it owes. 2. Do that role's work with your own tools. Stay in that role — do not solve the next role's problem because you can see it. 3. Call `charter_submit` with the artifact. If it is rejected, read the reason and fix