# Connect documentation blocks with unique anchors, one authority and lineage

> When an AI reads many prompts, policies, skills, guides and notes, it no longer sees one document at a time; it receives a large context forest. A small but…

Canonical: https://optionos.app/guide/en/context-forest
Published: 2026-07-13
Source: optionos-product:r19

When an AI reads many prompts, policies, skills, guides and notes, it no longer sees one document at a time; it receives a large context forest. A small but important block can disappear when its larger parent idea is not visible.

This page is a prediction, not a proven result: if every decision-bearing documentation block carries an objective `[namespace:key]`, parent/root relation, relation, authority, projection boundary and judge, humans and agents can rebuild the big picture more reliably.

A correct node name is not subjective. Value words like `good-lineage`, `clean-docs` or `obvious-tree` are not names; they must compile into observable axes first. A good access key names the observed subject: `context-forest`, `prediction-lineage`, `node-index`, `file-policy`.

A correct node does not overlap. Source truth lives in one place; Guide, HTML and generated graphs are projections. If similar information repeats, it must carry a different lineage and a different reader decision; otherwise it is merged, split or demoted to projection.

Minimum shape: unique id → parent/root → relation → receiver decision → authority → projection boundary → judge.

Example: `[base:1]` reads like a parent node, and `[base:1.1]` is its child block. `[file:source-file-policy]` is the file authority, and `[file:1]` is its meaning block. The reader answers “where does this block belong?” from lineage instead of line numbers or memory.

![base-prompt.md showing base namespace anchors](https://optionos.app/guide/context-forest-base-prompt-anchors.png)
*`[base:1]` reads as parent scope; `[base:1.1]` reads as child block.*
1. `[base:1]` — parent scope / main node
2. `[base:1.1]` — child block / sub-node

![file.policy.md showing file namespace anchors](https://optionos.app/guide/context-forest-file-policy-anchors.png)
*`[file:source-file-policy]` reads as authority root; `[file:1]` reads as meaning section.*
1. `[file:source-file-policy]` — file authority / source root
2. `[file:1]` — meaning section / child block

Falsifier: if anchors and lineage do not help agents recover the right parent/authority, do not reduce duplicate/orphan decisions, or only add scan noise, the prediction gets weaker.