Skip to content

feat: make roadmap status reports theorem-first - #3

Merged
kim-em merged 1 commit into
mainfrom
feat/voyager-style-status
Aug 4, 2026
Merged

feat: make roadmap status reports theorem-first#3
kim-em merged 1 commit into
mainfrom
feat/voyager-style-status

Conversation

@kim-em

@kim-em kim-em commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Voyager's new results posts are readable because they are selective and theorem-first: small semantic sections, one mathematical idea per entry, plain-language significance before implementation names, references at the end, and a compact footer.

This change applies that presentation contract to generated roadmap status snapshots:

  • STATUS.md opens with an at-a-glance summary and selectively groups named results, notable definitions/infrastructure, roadmap coverage, and the nearest frontier;
  • named results and infrastructure are explicitly capped, and the whole snapshot targets 750 words with a 900-word validator backstop;
  • declaration inventories, per-layer mini-essays, and process narrative are explicitly excluded;
  • Zulip progress announcements now link both the full PROGRESS.md and current STATUS.md;
  • completed roadmaps retain correct /Completed/<area>/... links rather than being sent to the active-roadmap path.

Verification:

  • python3 -m compileall -q progress tests
  • ./tests/run — all suites passed
  • workflow YAML parsed successfully
  • active- and completed-roadmap announcement links covered by regression tests

Shape generated STATUS snapshots after Voyager’s selective named-results format, enforce a readable word cap, and link both PROGRESS.md and the current roadmap STATUS.md from Zulip announcements.
@kim-em
kim-em merged commit b18930c into main Aug 4, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant