first-tree-contextlisted

# First Tree — Context Read this skill when you need the Context Tree concept model or when a specific source artifact should be reflected into the tree. It is the operating guide for authorship: a few principles, a small set of hard rules, and the judgment guidelines that turn source material into correct edits. Use `first-tree-read` for task-scoped tree reads before acting. This skill explains the source-system boundary and the read discipline needed before writing; it does not own the operational reader workflow. ## What A Context Tree Is A Context Tree is a Git repository with a recursive `NODE.md` index that holds a team's **durable decisions, constraints, ownership, and cross-domain relationships**. It is the persistent counterpart to the in-the-moment context built in a chat: a chat goes away; the tree carries forward what the next agent needs to act correctly across many months and many repos. Three objects shape every tree task: - **source / workspace root** — where humans and agents do the work - **tree repo** — the Git repo that stores the durable record - **binding** — the metadata that links the workspace to the tree Tree files: - `NODE.md` at each directory describes the domain and indexes children - leaf `*.md` files capture one decision, constraint, or relationship - `members/<id>/NODE.md` is one member's responsibilities and review scope - frontmatter (`title`, `owners`, optional `soft_links`, `lastReviewed`, `decisionLocksCode`) plus the body — see