Skip to content
ThinkWork ThinkWork

Inheritance Rules

Workspace composition resolves files by walking from the most specific folder back to broader layers.

For workspaces/expenses/workspaces/escalation/GUARDRAILS.md, ThinkWork checks:

  1. Agent override at workspaces/expenses/workspaces/escalation/GUARDRAILS.md
  2. Agent override at workspaces/expenses/GUARDRAILS.md
  3. Agent override at GUARDRAILS.md
  4. Template file at workspaces/expenses/workspaces/escalation/GUARDRAILS.md
  5. Template file at workspaces/expenses/GUARDRAILS.md
  6. Template root file at GUARDRAILS.md
  7. Default workspace file at GUARDRAILS.md

Pinned files use path-qualified keys:

GUARDRAILS.md
workspaces/expenses/GUARDRAILS.md
workspaces/expenses/workspaces/escalation/GUARDRAILS.md

Root keys stay short because the path is unambiguous. Nested keys include the folder path so a template update badge can appear on the exact file that needs review.

Only GUARDRAILS.md is currently pinned. Most other files are live and resolve from the first matching layer.

When AGENTS.md changes, ThinkWork refreshes the generated routing and folder sections. The running container picks up the new map on the next turn; no restart is needed.