Audit Pulse v0 public mission docs
Review and verify the Pulse v0 public dashboard mission against its settled status and evidence packet, creating a v1 paradoc for new work.
/goal Use Parallax on docs/mission-public-pulse-app-v0.md. Treat it as the settled v0 public usage-dashboard app mission opened before the Node B Nix-store retention paramission. Product name is Pulse / Choir Pulse, app id pulse , and product stance is radical transparency with public aggregate facts and no private surveillance data. Current status is settled for v0: public staging app/API shipped, classification/privacy invariants were tested, aggregate-only public-safe metrics rendered signed out, no private analytics store was introduced, and evidence shows content/email/IP/per-user behavior are not exposed. Do not reopen v0 unless auditing the evidence packet or correcting factual drift. For new work, create a successor Pulse v1 paradoc for cache/rate-limit policy, richer public reliability counters, or classification review workflow. Ledger: docs/mission-public-pulse-app-v0.ledger.md
claude-code
More docs loops
Changelog generation from commits
Turn the commit history since the last release tag into a human-readable, categorized CHANGELOG entry ready for the next version.
/goal CHANGELOG.md has a complete entry for the next release — read every commit since the last version tag, group changes into Added, Changed, Fixed, and Removed, write user-facing descriptions (not commit messages), link PR numbers, and flag anything that looks like a breaking change; stop after 5 turns
docslow risk
Close the gaps before you build
Fill documentation gaps until requirements, technical design, acceptance criteria, and test strategy describe one buildable system.
Prepare [project] for implementation. Ensure its documents cover requirements, technical design, tasks with acceptance criteria, and test strategy. Each round, fix the largest gap or contradiction that could make two competent engineers build different systems. Keep details traceable, record assumptions, and ask before product forks. Recheck consistency, then have two independent reviewers describe the components, data model, dependencies, and definition of done. Stop when they materially agree and every artifact is testable, or a decision needs the user.
docslow risk
Fix doc drift, ship a PR
Compare every doc against the current code, fix what's stale, verify commands and links, and open a reviewable PR.
Whenever a documentation pass is needed, review the codebase in full and make sure all documentation reflects the current implementation. Update stale documentation, verify the changes, then open a pull request.
docslow risk