Planned scope: shared reranker, retrieval log, golden set, and a reproducible scorecard before any measured result appears elsewhere.
Dated shipping-next ledger
These entries are not available-now claims. Each item is dated, phrased as planned scope, and labeled with the same Roadmap chip used across the site.
Planned scope: replace the labeled Product C.2 placeholder with a real inspector asset after the product view is ready.
Planned scope: continuous source-sync scheduling for supported connectors, with freshness status visible instead of implied.
Planned scope: shared team memory controls after access inheritance and document-level restrictions are ready for review.
Planned scope: evaluation runs and a scorecard that can be reproduced before any claim is promoted to product or compare pages.
Planned scope: generated client config with key and library scope inserted so setup moves from manual paste to guided install.
Promotion rule
A roadmap item can move into available-now copy only after the product implementation is merged, verified, and represented without future-tense language.
Evaluate what exists today, then watch this ledger.
The current product surfaces are linked from the overview. Future claims stay dated here until they are ready to become available-now copy.