docs: replace calendar roadmap with current v0.1 capability status - #246
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe PR adds the WS-DOCS-001 documentation initiative and replaces calendar-based status guidance with a capability-based v0.1 documentation path. It labels superseded roadmaps and specifications as historical records. ChangesCurrent v0.1 documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/DECISIONS.md:
- Around line 5-6: Update the status-category wording in DECISIONS.md to use the
exact labels defined by docs/roadmap_status.md, replacing “remaining” with
“Planned” and “in-progress” with “In progress”; preserve the other existing
categories unless the ledger specifies their exact equivalents.
In `@docs/checker_trial_failure_catalog.md`:
- Around line 3-5: Update the purpose text in checker_trial_failure_catalog.md
to remove the claim that the catalog proves current backend contracts. Describe
it only as historical evidence, and direct readers to docs/roadmap_status.md
plus merged code and tests for current capability and behavior.
In `@docs/diagrams/backend_v01_components.md`:
- Line 25: Update the introductory sentence describing the v0.1 backend
dependency order to explicitly say it follows the Workstream product lifecycle,
distinguishing it from the engineering loop. Preserve the existing
dependency-order meaning and do not conflate it with the documented engineering
loop.
In `@docs/historical_planning.md`:
- Around line 8-9: Update the current-work guidance in historical_planning.md to
include CONTRIBUTING.md as the canonical entry path and direct readers to follow
the engineering loop defined there, while preserving the existing references to
the status ledger, main code and tests, accepted ADRs, and subsystem
specifications.
In `@docs/roadmap_status.md`:
- Around line 23-24: Resolve the v0.1 scope inconsistency around “Reputation
Signals” in docs/roadmap_status.md by making it explicitly a deferred signal
input for a later reputation consumer, consistent with the
ContributionRecorded/contribution-evidence boundary, or remove it if that input
is not supported; do not imply runtime reputation projection or integration in
the locked scope.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: e36a5d94-6127-4d45-8510-05a21e101f91
⛔ Files ignored due to path filters (1)
docs/architecture_brief/workstream_architecture_brief.pdfis excluded by!**/*.pdf
📒 Files selected for processing (33)
.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/CHUNK_MAP.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/DECISIONS.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/DISCOVERY.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/INTENT.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/PLAN.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/REVIEW.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/RISKS.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/STATUS.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/chunks/WS-DOCS-001-01-current-v01-entry-path.mdAGENTS.mdCONTRIBUTING.mdREADME.mddocs/architecture_brief/workstream_architecture_brief.mddocs/architecture_system_architecture.mddocs/checker_trial_failure_catalog.mddocs/diagrams/README.mddocs/diagrams/backend_v01_components.mddocs/diagrams/workstream_v01_container.mddocs/historical_planning.mddocs/operations_reviewer_workflow.mddocs/product_brief.mddocs/roadmap_30_day_master_plan.mddocs/roadmap_day_by_day_execution_plan.mddocs/roadmap_implementation_backlog.mddocs/roadmap_status.mddocs/roadmap_week1_backend_plan.mddocs/spec_chunk_10_checker_trial.mddocs/spec_chunk_5_submission_packet_foundation.mddocs/spec_chunk_6_checker_contract_records.mddocs/spec_chunk_7_checker_runner_registry.mddocs/spec_chunk_8_submission_artifact_policy_checkers.mddocs/spec_chunk_9_pre_review_gate.mddocs/spec_week2_checker_framework.md
abiorh-claw
self-requested a review
August 2, 2026 15:39
abiorh-claw
previously approved these changes
Aug 2, 2026
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
@.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/reviews/WS-DOCS-001-01-external-review-response.md:
- Around line 32-36: Update the “Remaining Risks” statement to avoid claiming
that archive notices and current-evidence links prevent misuse; describe their
effect as reducing the risk that historical checker records are used as current
implementation authority.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: b6bc6448-e50e-47d2-aa6f-52f8ff933e72
📒 Files selected for processing (6)
.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/DECISIONS.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/reviews/WS-DOCS-001-01-external-review-response.mddocs/checker_trial_failure_catalog.mddocs/diagrams/backend_v01_components.mddocs/historical_planning.mddocs/roadmap_status.md
🚧 Files skipped from review as they are similar to previous changes (5)
- docs/historical_planning.md
- docs/diagrams/backend_v01_components.md
- docs/checker_trial_failure_catalog.md
- docs/roadmap_status.md
- .agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/DECISIONS.md
abiorh-claw
self-requested a review
August 2, 2026 15:56
abiorh-claw
approved these changes
Aug 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Workstream PR Trust Bundle
Chunk
WS-DOCS-001-01- Current v0.1 documentation entry pathGoal
Replace expired calendar guidance with a current, evidence-backed v0.1 capability view for humans and agents.
Intent And Planning Context
.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/INTENT.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/chunks/WS-DOCS-001-01-current-v01-entry-path.mdWhat Changed
docs/roadmap_status.mdaround exact capability categories.Why It Changed
Expired week/day plans obscured current v0.1 capability state and made historical evidence look authoritative.
Design Chosen
Use one capability ledger with
Implemented,In progress,Planned, andHistorical. Keep README as summary, CONTRIBUTING as the canonical entry path, AGENTS as agent guidance, and old plans as indexed history.Alternatives Rejected
Scope Control
Allowed Files Changed
Files Outside Stated Scope
Product Behavior
Evidence
Commands Run
Result Summary
Acceptance Criteria Proof
Test Delta
Tests Added
Tests Modified
Tests Removed Or Skipped
Internal Reviewer Results
Reviewed code SHA:
c2f67572e8ac9fee4d90aa788852bd638b559848Reviewed at: 2026-08-02
Reviewer run IDs: recorded in
.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/REVIEW.md.External Review
c2f67572; response recorded in the initiative.CI And Gate Integrity
Remaining Risks
The capability ledger must be maintained as integrations merge. Historical records retain original terminology but are explicitly non-authoritative.
Follow-Up Work
Update the capability ledger when an integration becomes implemented on
main; do not revive calendar plans.Human Review Focus
Please inspect:
Human Merge Ownership
Summary by CodeRabbit