save this prompt/ Repository goal: - [let codex fill in] Daily task: Review the current repository state and update the documentation so it remains accurate, useful, and increasingly stable over time. Primary objectives: 1. Document how the system actually works today. 2. Keep architecture docs aligned with implementation. 3. Explain technical systems in simple product language. 4. Map technical capabilities to marketing/user-facing features. 5. Preserve important implementation details that future agents, engineers, and product reviewers need. 6. Avoid speculative claims unless clearly marked as planned or proposed. Documentation areas to maintain: - Architecture overview Include simple explanations and technical examples: - Small JSON examples for input/output payloads - Plain-English explanations of fields - Notes on whether fields are clip-intrinsic or edit-plan-specific Architecture diagrams: Create or update Mermaid diagrams where useful Database documentation: Inspect schema files and migrations. Keep an ERD-style section updated with: - app_users - projects - assets - snapshots - command_batches - command_events - jobs/runtime jobs Explain ownership, key relationships, and what each table is responsible for. Marketing feature mapping: Maintain a table with columns: - Marketing feature - User-facing claim - Technical systems behind it - Current proof/evidence - Limitations or caveats - Next validation needed Validation: Before editing docs, inspect the relevant source. Do not document assumptions as facts. After editing docs: - Run a focused docs/source consistency check if one exists. - Run `git diff --check` on changed docs. - Summarize exactly what changed and what remains uncertain. Output expectations: - Make minimal, scoped documentation edits. - Prefer improving existing docs over creating scattered new files. - If creating a new doc, link it from docs/README.md. - Keep docs practical and readable. - Include dated notes only in docs/product/changes.md or context updates; stable docs should describe current behavior, not daily history. Do not: - [let codex fill in] Final response: Provide: - Summary - Files changed - Key architecture/product mapping updates - Validation run - Open questions or docs gaps - Recommended next documentation task