2025–2026 Roadmap

From first proof to proof-native MVP

A high-level view of how CueCrux moves from initial setup in July 2025 to an MVP in Q1 2026.

  1. 1Planned

    July 2025

    Phase 0 — Make trust the hero from day one

    Ship cited answers and the rails beneath them.

    What users feel

    From day one, answers arrive with sources and mode badges, not just friendly text.

    What we focus on internally

    Stand up WebCrux Alpha, evidence pipeline v0, InfraCrux dev stack, and WatchCrux in shadow mode.

    • • WebCrux Alpha: ask, answer, citations, mode badges
    • • Evidence pipeline v0: Quorum (MiSES) + CROWN receipts wired
    • • InfraCrux dev stack: Postgres, ClickHouse, Prometheus, Grafana
    • • WatchCrux operator watching health and audits separately
    • • Current status: no external users yet (pre-launch)
  2. 2Planned

    Aug–Sep 2025

    Phase 1 — Turn early users into co-authors

    Let people feed the machine and earn for it.

    What users feel

    You can choose what we index, see the cost, and earn Crux when your sources help others.

    What we focus on internally

    Crux Economy v1.0, FactoryCrux “Index a Site” flow, SDKCrux alignment, ATAM baseline.

    • • Crux balances and impact panel in WebCrux
    • • Index-a-site wizard with CRUX + £ quotes
    • • Robots/licence-aware ingestion pipeline
    • • Shared SDK contracts across Engine/Web/Watch
  3. 3Planned

    Oct–Nov 2025

    Phase 2 — Support that proves its answers

    Customer service with footnotes.

    What users feel

    Support replies with citations, clear triage, and a visible audit trail.

    What we focus on internally

    SupportCrux integrated into WebCrux, AgentCrux mesh online, OpsCrux Alpha as control tower.

    • • In-app support desk with AI triage and receipts
    • • Researcher & Support Triage agents with C³ budgets
    • • OpsCrux dashboard for p95, errors, and spend
  4. 4Planned

    Jan–Mar 2026

    Phase 3 · MVP — The proof-native AI console

    Wrap the story: ask, support, contribute, operate.

    What users feel

    One console for provable answers, rewarded contributions, accountable support, and visible ops.

    What we focus on internally

    WebCrux MVP, Crux Economy production, evidence backbone hardened, InfraCrux + WatchCrux + OpsCrux in prod.

    • • WebCrux MVP: ask, history, saved, workspaces, SupportCrux
    • • Crux rewards & spend for verified/audit and storage
    • • Evidence backbone with Quorum (MiSES), CROWN receipts, and SLOs
    • • InfraCrux, WatchCrux, OpsCrux wired as the ops plane
  5. 5Planned

    Apr–May 2026

    Phase 4 — Prove it with design partners

    From MVP to real-world proof with early customers.

    What users feel

    Design partners see receipts on every critical answer; onboarding shows “no hidden magic” with auditable history.

    What we focus on internally

    Zero-to-one customer onboarding, guarded production rollout, support playbooks, and stability hardening before GA.

    • • Select design partners; controlled production access (still zero GA users today)
    • • Replayable audit trails for every answer served to partners
    • • SupportCrux playbooks + ops runbooks for incidents
    • • Stabilise perf budgets and cost guards in OpsCrux
  6. 6Planned

    Jun–Jul 2026

    Phase 5 — Performance & data plane swap

    Upgrade the evidence store for hyper-fast artefact handling.

    What users feel

    Faster verified answers and larger corpora without losing receipts; latency and scale feel production-ready.

    What we focus on internally

    Replace Postgres artefact store with proprietary high-performance evidence DB; benchmark Quorum (MiSES) retrieval and receipts; migrate with dual-write/safe cutover.

    • • Design + implement proprietary artefact DB for high-throughput ingestion
    • • Dual-write/dual-read migration plan with rollback
    • • Perf SLOs: verified p95 < 2s on design-partner corpora
    • • Backfill receipts and Quorum (MiSES) sets to new store with checksums
  7. 7Planned

    Aug–Sep 2026

    Phase 6 — Ecosystem rollout & GA prep

    Open the platform while keeping proof-first guardrails.

    What users feel

    Public launch with clear pricing, Crux economy, and connectors; still defaulting to receipts and audits.

    What we focus on internally

    GA hardening, ecosystem connectors, SDKCrux maturity, compliance attestation, and scaling ops/support.

    • • GA readiness checklist: security posture, SLOs, incident drills
    • • Connector rollout (Docs, Drive, Slack) with receipts preserved
    • • Crux economy polished (earn/spend UX, exports)
    • • OpsCrux + WatchCrux dashboards for public SLOs and budget guardrails