Positioning tree

# Positioning tree

Each leaf owns a different kind of claim. This avoids the most dangerous form of documentation drift: reading a future-facing pitch as if it were shipped behavior.

| Leaf | Owns | Status discipline |
|---|---|---|
| [Promise](promise.md) | Product identity, methodology, and pillars | The enduring claim |
| [Delivery and worldview](delivery-and-worldview.md) | Shipped/building/direction boundary and category argument | Label capability precisely |
| [Human practice](human-practice.md) | Scenario, World, and the many-camera experience | Keep shipped Scenario distinct from World direction |
| [Strategy](strategy.md) | Growth path and defensibility | Direction, not implementation contract |
| [Continuity](continuity.md) | Promoted, recast, and retired framing | Migration record |

**Depends on:** [Values](../../foundations/VALUES.md) for the enduring why;
[World](../../../specs/world/README.md) for the stable concept and open mechanics;
[Vocabulary](../../vocabulary/README.md) for word definitions; [Product behaviours](../PRODUCT_BEHAVIOURS.md)
for interaction implications.

Raw Markdown source