Repository navigation
Conversation
Restructure the proposal into Problem Definition (motivation, design requirements) and ASAPPlanner Design (design intuition, assumptions, stages), and update the Contents and reading guide to match. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… figure Link only each stage's name in the overview figure, lay the three inputs out side by side, and keep the figure's text identical to the original text figure. Point Contents and the Assumption 2 link at the renamed headings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ts side by side Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GitHub renders Mermaid in a sandboxed iframe, so in-page #anchors resolve inside the iframe. Use absolute URLs opened in a new tab instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
How an end user starts the viewer, reads each part of the page (queries, deployment inputs, the Stage 3 ranking, the three stage lanes, details), plans their own PromQL queries from the editor or stage_pipeline, and fixes common problems. Linked from docs/README.md and the user-guide index. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rename Pass 1 to per-computation candidate generation and add Algorithms 1, 1.1, 2 and 3 with a worked example and figure for each, the window-composition rule's window-summary enumeration, the materialization steps, and an appendix defining windows, sliding and tumbling windows and Exponential Histograms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Summary
Updates
docs/design_docs/proposals/planner-layering.mdwith new writing:--> VS:review comments are kept for discussion.The stage sections, end-to-end examples and scenarios are unchanged apart from minor wording in the stages table and diagram.
docs/user_guide_docs/stage-viewer.md, linked fromdocs/README.mdand the user-guide index): how to start the viewer, read each part of the page (queries, deployment inputs, the Stage 3 ranking, the three stage lanes, details), plan your own PromQL queries from the editor orstage_pipeline, and fix common problems. It describes the redesigned viewer in feat(dag-viewer): redesign the viewer around the stage pipeline #574, which is not onmainyet, so merge it with or after feat(dag-viewer): redesign the viewer around the stage pipeline #574.🤖 Generated with Claude Code