vaultspec-documentationlisted

# Documentation Pipeline Produce one user-facing document grounded in its sources. For creation or substantial rewriting, use the pipeline below. For focused maintenance, inspect the affected claims, edit within the established structure, and verify technical accuracy and readability; do not restart the full pipeline. The system's approval contract applies throughout. Reuse supplied scope and audience; ask only for material missing choices. Explicit prior authorization can cover a wireframe and final delivery within that scope. These document stages are not plan Phases and do not create additional framework review gates. ## The Pipeline ``` Phase 1: Wireframe -> Phase 2: Refinement -> Phase 3: User Approval -> Phase 4: Context Gathering -> Phase 5: Drafting -> Phase 6: Technical Review -> Phase 7: Editorial Review -> Phase 8: User Approval ``` For the full pipeline, complete each stage's purpose before the next. If delegation is unavailable, perform the passes sequentially and state that review was not independent. Section-level passes feed a cohesive whole-document review. ______________________________________________________________________ ## Phase 1: Wireframe The wireframe is a human-readable outline that defines the document's skeleton. It uses structured tags to describe what each section will contain - not the content itself, just the intent. ### Content tags The wireframe uses two types of human-readable tags: - `<Title: ...>` - A major heading that frame