# Documentation Guide

Updated: 2026-07-23

This index separates current operating guidance, dated evidence and working drafts. When
two documents conflict, use the authority and date rules below instead of combining them.

## Authority

1. [AGENTS.md](../AGENTS.md) defines engineering, security and workflow invariants.
2. [README.md](../README.md) defines the supported local setup and operating model.
3. [ROADMAP.md](../ROADMAP.md) defines current product status and ordered milestones.
4. The latest dated audit records evidence from its stated source snapshot.
5. [PRE_RELEASE_CHECKLIST.md](PRE_RELEASE_CHECKLIST.md) is the single active progress document. It
   contains the user-visible status, current bounded patch, open gates and ordered queue.

A dated audit is not a live repository-status report. Re-run its checks before relying on
the result.

## Current documents

| Document | Role | Status |
| --- | --- | --- |
| [2026-07-17 pre-release audit](audits/2026-07-17-pre-release-audit.md) | Evidence, risks and policy drafts from the stated audit snapshot | Historical evidence; not live approval |
| [Active pre-release status](PRE_RELEASE_CHECKLIST.md) | User status, current patch, open gates and required evidence | Single active execution document |
| [Store listing draft](STORE_LISTING.md) | Conditional copy and screenshot plan | Unapproved draft |
| [Async performance review](performance-async-actions.html) | Standalone local review snapshot | Supporting evidence; not an execution queue |

## Installer-distributed drafts

The installer build reads [PRIVACY.txt](../distribution/PRIVACY.txt),
[TERMS.txt](../distribution/TERMS.txt) and
[THIRD_PARTY_NOTICES.txt](../distribution/THIRD_PARTY_NOTICES.txt) directly. Keep them in
place. They are not release-approved legal documents or a complete license inventory.

## Maintenance rules

- Keep `PRE_RELEASE_CHECKLIST.md` as the only active execution document.
- Keep it compact and replace completed-task detail instead of appending logs.
- Do not create session handoffs, next-patch files, or duplicate active queues.
- Use Git history for superseded checklists, completed implementation plans and session history.
- Create a dated audit only when a new evidence snapshot is intentionally required.
- State the snapshot date and commit whenever recording build or verification evidence.
- Update links and status labels when archiving or superseding a document.
- Never record credentials, authentication data, private hostnames or absolute local paths.
