Repository navigation
docs(roadmap): motivation and end state; the detail moves to issues - #474
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 55 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe PR replaces the detailed roadmap with a concise project-direction document, adds deliberate non-primitives guidance, and updates roadmap references across documentation, source comments, validation messages, and tests. No runtime behavior changes. ChangesRoadmap and capability-boundary governance
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Merging this PR will not alter performance
Comparing Footnotes
|
…anchor Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
docs/ROADMAP.mdgoes from 203 lines to 88: why the project exists and whereit is going. No work items. Those are issues now, grouped under three parents
— #470, #471, #472 — with 21 sub-issues between them.
Why the index had to go
The page carried a table per track, and it lost to the tracker it duplicated.
Found while triaging:
defined(v), defined(v): component-aware where over variables (Track 1 item 5) #219) andDegree 2: what "reachable" would actually require #84 in Track 3 are both closed/completed, still listed as open.
would have dropped them silently, so they are filed first as Window sum: sum_next_n(x, over=dim, n=N) — the bounded-halo member of the window family #468 and A where predicate cannot reduce over a dimension the foreach does not span #469.
chunking.pyandtests/oracle.pycite ROADMAP Track 5;test_api.pycites ROADMAP 2c;
test_validation.pycites ROADMAP 5c;degree.pycites "The degree axis" — in two user-facing error messages. There is
no Track 5, no lettered subsection and no degree-axis section.
That last one is the sharp end: a
LanguageErrora user actually reads wassending them to a heading that does not exist. All four are fixed here.
Where the content went
docs/design/ceiling.md, which already owns what may enter the language; the refusals are its negative halfceiling.mdwith a pointer to itMoving the refusals also removes a two-hop answer: CLAUDE.md sent feature triage
to
ceiling.mdfor the admissibility test and toROADMAP.mdfor the refusals.One question, one page. Both pointers repointed.
References repointed
Every deep
ROADMAP.md#track-Nanchor —benchmarks.md,ARCHITECTURE.md(x2),SPEC.md,ceiling.md(x2),sinks/README.md— now links the parent issue.grep -rn "ROADMAP.md#track"returns nothing.Verified
mkdocs build --strictclean (it validates every internal anchor, which is whatwould have caught a bad repoint).
ruff check/format --checkclean,pyrefly0 errors, 764 passed.One golden moved:
examples/walkthrough.outcaptures the degree-2 error textverbatim, so changing the pointer inside it failed
test_walkthrough_matches_goldenuntil regenerated — the test working as designed on a user-facing string.
Summary by CodeRabbit