Use the current guides to operate or change the app. Use dated records to inspect the evidence available at a past checkpoint. A historical pass does not approve a later SDK or release.
| Guide | Contents |
|---|---|
| Product guide | Phone settings, pages and gestures |
| AI guide | Ask AI, Conversate, keys and history |
| Live data and navigation | Providers, cache states, languages and routing |
| Development setup | Local preview, checks and packaging |
| HUD transport | Image containers, update order and busy state |
| SDK compatibility | Candidate requirements and hardware evidence |
| Privacy and limitations | Data flow, attribution and verification limits |
| Add a language | Locale registry and feed requirements |
| Documentation writing rules | STE principles and evidence-preservation rules |
Complete the mandatory pre-deployment checklist before every upload.
Run npm run release:check. Do not bypass a failed origin audit.
- v0.2.8 candidate: submitted on November 10 and In review at the recorded checkpoint.
- v0.2.7 decision: rejected for undeclared bundled URL origins.
- API operations: deployed version, request limits and operational duties.
See the documentation review checkpoint for scope and preservation checks.
The record catalog links research, physical checks, maintenance audits, specifications and implementation plans. Each record retains its original date, configuration and evidence. Specifications and plans are not proof of completed work.
Paths under output/ identify local evidence. Those private files are not published with the repository.
Do not upload private evidence to repair a link in a historical record.