Durable documents still link back into agile content

The link between durable documents and agile content runs one way in the rule and two ways in the tree. About 180 id links run from doc/knowledge/, doc/recipes/, doc/meta/ and doc/llm/ into stories, tasks, captures and plans. The bulk is the journey documents' * Prototype sections, which link the task that built each prototype; the rest is spread thinly across recipes, hubs and knowledge pages that name the work that produced them.

A durable document that links a task pins itself to a sprint. When the task closes and the sprint recedes, the link leads to a record of work rather than to knowledge, and a reader who follows it learns what somebody did rather than what is true. The rule is already encoded and already measured: compass lint counts these links and reports them as an advisory, so the number is visible and nothing fails. Making it fail without first clearing the backlog would block every unrelated change, which is why it is advisory today.

The questions this capture has to settle before it becomes a task: whether the prototype links are worth keeping in some other form — a prototype branch or a prototype page is itself durable, so the record may move rather than disappear — and whether the advisory becomes a gate in the same change or a later one.

• The rule as the lint encodes it: the durable directories are doc/llm/, doc/meta/, doc/knowledge/ and doc/recipes/, and the agile types are story, task, sprint, design, capture, version, plan and retrospective. investigation is deliberately not among them, so a durable page may cite the survey it answers.
• The measurement is the line compass lint prints: at the time of writing, 180 links across 89 files.

• Knowledge — the hub the durable pages hang from.