Documentation System

The documentation system section exists so maintainers can review how the repository describes itself in public without mixing product behavior, evidence status, and maintainer-only policy into one blurry surface.

flowchart LR
    A[Runtime change] --> B[README surfaces]
    A --> C[Public handbook pages]
    A --> D[Maintainer documentation rules]
    B --> E[Consistent public story]
    C --> E
    D --> E

Why This Section Matters

The runtime is now broad enough that weak public language becomes misleading quickly. A page that sounds small, generic, or overly internal can make the package look less capable than the code and tests already show.

Section Scope

• Documentation ownership explains which documentation layer owns which question
• Native surface documentation explains how flagship native work stays visible across reference, workflow, and quality pages

Start With

• Open Documentation ownership when the question is where a new claim belongs.
• Open Native surface documentation when the question is whether a new native surface is documented deeply enough to be part of the public release story.