# templates/role.template.md

> 40 lines of code and 0 definitions.

Tree: Coordination tree
Language: markdown
Canonical: https://banes-lab.com/anatomy/coordination#file-coordination-templates-role-template-md
Source text: https://banes-lab.com/assets/sources/source.f93e7ad82f73ca1369460f3ee9c713b510992f6b857bde91925ee13241c7d9f8.generated.txt

## Source

```markdown
---
name: <subject>.<letter>
type: ROLE
letter: <the indexed letter this document belongs to>
concern: <the one concern this seat owns, stated as a concern rather than a task list>
summary: <one line another seat reads to decide what may be routed here>
---

# HOW THIS TEMPLATE IS USED

**A seat writes its role document before its first edit**, from this file, at
`<roles>/<concern>.<letter>.role.md`. The filename carries the CONCERN and the letter takes the variant
slot, because a letter changes hands while the concern outlives the seat — and every citation that ever
named the letter resolves through the index rather than through a filename.

**The section set below IS the contract the role check reads.** It derives the headings and the
frontmatter keys from this file on every run, so the check cannot drift from the template a seat is
raised from. Adding a section here adds it to the obligation; nothing transcribes it a second time.

**A document listing only virtues is decoration.** A seat reads its own role document looking for the
trap it fell into last time, so the failure modes section carries the ones this seat actually exhibits,
stated as shapes rather than as resolutions to do better.

# Name

<the letter, the concern, and what a reader should call this seat>

# Role

<what this seat is FOR, in one paragraph — the concern it holds, not the work currently in front of it>

# Objective

<the state this seat is driving toward, and the observable that says it arrived>

# Behavior

| I author, and no other seat does |                 |
| -------------------------------- | --------------- |
| `<path or surface>`              | <what it holds> |

<how this seat writes: its record on the board, its anchored edits, what it hands over rather than runs,
and how it drains an item it has handled>

# Consideration

<the judgements this seat makes that no gate makes for it — the calls where two rules meet and the
architecture decides, stated so a resuming session can make the same call>

# Work Method

<the loop this seat runs: what it reads first, what it measures, what it proves before it believes a
green, and what it does when a gate and a document disagree>

# Principles

<the standing commitments that decide this seat's calls, one per line>

## Failure modes

<the shapes this seat exhibits, stated as constructs with their tells — never as intentions>
```