docs: ASAPPlanner and ASAPQuery-backend integration architecture - #512
Conversation
Review and pushed fixes — 2026-09-08Reviewed the 15 currently open PRs and their integration boundaries. This is self-review, not independent approval. No PR was merged; all code updates used normal commits/merges on existing PR branches.
Validation
#511 acceptance updateUser confirmed migration to the new contract. Commit CMS-with-heap and CountSketch-with-heap each return all three expected identities/counts (gamma=200, zeta=150, alpha=100), with timestamps, two range steps and Remote Write retry deduplication checked. Raw values are 17 to distinguish counts from weighted sums. Unregistered instantaneous TopK follows the configured exact fallback. All four canonical compatibility process tests passed; the remaining legacy test file compiles. This resolves the two-test contract-migration decision above, not all unrelated legacy OTLP serving acceptance. No independent approval or merge performed. |
# Conflicts: # docs/design_docs/README.md
Summary
Before / after
Before: architecture and migration ownership were implicit across the Planner pin, controller and serving paths.
After: an explicit shared semantic contract, system workflow, staged migration plan and implementation/acceptance tracker distinguish supported-profile implementation from review, merge and production rollout.
Scope
Documentation only; no runtime changes or repository rename in this PR. The runtime changes are separate sequential PRs and are not merged automatically.
Validation
git diff --check.95131d83972bb7a07d338e2a5af925a20c15ddce, historical Planner pincb50219c582d43f53ab77d3a595bd1ea4a9aa119.