docs: spec MVP v6 — controller-driven multi-stage demo (issue #46) - #293
Merged
Merged
Conversation
Issue #46's MVP scope was substantially expanded by the user. This spec captures the new requirements: - 3 query classes: window-per-series, label-aggregation-at-instant, combined window+label - Controller drives sketch + stage placement based on input query workload (one-shot static plan, no dynamic replanning in MVP) - Multi-stage topology: 10 SDK / 2 agents / 1 gateway / 1 backend with 10K total cardinality split per production-pyramid pattern - 6 criteria: bandwidth, query latency, combined resource, accuracy, cold-fallback, freshness - Freshness measured by encoding emit timestamp in synthetic counter value (assumes single-host clock sync) Non-goals explicit: dynamic replan, OpAMP hot reconfig, production- scale cardinality, multi-host federation, full PromQL on archive. 6 phases (A=verify controller plumbing, B=config emitter, C=multi-stage overlay + gateway aggregation, D=workload + freshness wiring, E=driver + report v6, F=run + verify + comment). Total ~1-2 weeks contingent on Phase A. Builds on v4 (merged) and v5 (in flight). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 6, 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
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
Spec for the new MVP v6 covering the expanded #46 requirements:
Non-goals (explicit)
Phases
A: verify controller plumbing for plan→YAML emission (1 day)
B: config emitter (1-3 days, depends on A)
C: multi-stage overlay + gateway aggregation (2-3 days)
D: workload + freshness wiring (1 day)
E: driver + report v6 (1 day)
F: run + verify + comment (half day)
Total: 1-2 weeks contingent on Phase A.
Review please
This is an architecture spec — not auto-merging. Looking for sign-off on:
🤖 Generated with Claude Code