FIG. 1 - ROADMAP Shipping next / dated
Answer-first roadmap

Shipping-next claims live here, labeled.

The roadmap is the only place Answer Engine describes shipping-next product work: reranking and a measured accuracy number, always-fresh scheduling, org-shared mode, and the real inspector asset. Every item is marked with a Roadmap chip so future claims cannot be mistaken for available product behavior.

CLAIM LEDGER

Available-now product claims belong on product pages. Future work stays here until implementation and verification move it out of the roadmap ledger.

Available now Tenant-isolated grounded Q&AMCP server over stdio and HTTPFirecrawl web, Atlassian, CSV, and document ingestInspectable source lineage
Shipping next Reranker + measured accuracy number Always-fresh scheduler Org-shared mode with per-doc ACL Real inspector screenshot
Fig. 2 all future items use Roadmap chips
FIG. 2

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.

2026-07 Reranker + measured accuracy number

Planned scope: shared reranker, retrieval log, golden set, and a reproducible scorecard before any measured result appears elsewhere.

2026-07 Real inspector screenshot

Planned scope: replace the labeled Product C.2 placeholder with a real inspector asset after the product view is ready.

2026-08 Always-fresh scheduler

Planned scope: continuous source-sync scheduling for supported connectors, with freshness status visible instead of implied.

2026-08 Org-shared mode with per-doc ACL

Planned scope: shared team memory controls after access inheritance and document-level restrictions are ready for review.

2026-08 Self-driving evals + reproducible scorecard

Planned scope: evaluation runs and a scorecard that can be reproduced before any claim is promoted to product or compare pages.

2026-09 One-click MCP config injection

Planned scope: generated client config with key and library scope inserted so setup moves from manual paste to guided install.

Fig. 3 from roadmap to available
FIG. 3

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.

STAYS ROADMAP Claims with planned scope, target dates, placeholder assets, or evaluation work that has not produced a reproducible result.
CAN MOVE OUT Shipped behavior with working code, server-rendered copy, verified screenshots, and no dependency on future product work.
FIG. 4 - NEXT

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.

Now: MCP / source ingest / lineage
Next: reranker / scheduler / org mode
Rule: Roadmap chip before shipped copy
Date: 2026-06-20