Skip to content

CollectiveX v1: isolated EP results explorer#497

Draft
Oseltamivir wants to merge 1 commit into
masterfrom
collectivex
Draft

CollectiveX v1: isolated EP results explorer#497
Oseltamivir wants to merge 1 commit into
masterfrom
collectivex

Conversation

@Oseltamivir

@Oseltamivir Oseltamivir commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds an isolated /collectivex EP results explorer for sanitized CollectiveX datasets.

What changed

  • adds latency, effective logical payload-rate, overview, scaling, heatmap, sensitivity, coverage,
    failure, and provenance views using the shared D3 chart stack
  • separates measured dispatch, combine, and round-trip values from the derived isolated sum
  • keeps [cl], [rv], LL, and legacy schemas available only when diagnostic data is explicitly loaded
  • defaults to the official-headline publication view
  • permits headline/ranking evidence only for native collectivex.ep.v1 rows that are official,
    decision-grade, workload-attributed, and on the fixed sampling contract
  • keeps scaling lines within one evidence tier, backend/build, workflow run, phase, sampling profile,
    and source SHA; unknown provenance and cross-EP configuration splices fail closed
  • prevents legacy or diagnostic rows from winning scaling or fastest-cell heatmap projections
  • warns when selected series differ in workload, timing, or sampling identity instead of presenting an
    unsafe cross-hardware comparison
  • adds focused API/data/axis/D3 tests and Cypress coverage for the page and navigation

Data boundary

The page reads /data/collectivex.json with no-store. The dataset is intentionally not tracked.
This PR adds no raw GitHub-artifact discovery, snapshot carry-forward, repository dispatch, database,
or managed storage integration. A later self-hosted publisher will project a validated local channel
dataset into this boundary.

Until native v1 data passes coverage and stability gates, the UI exposes evidence but does not emit a
best-stack recommendation from legacy or diagnostic rows.

Validation

  • TypeScript typecheck
  • 96 focused Vitest tests in six files
  • 7 CollectiveX Cypress end-to-end tests
  • 9 TabNav Cypress component tests
  • targeted Oxlint and formatting checks
  • GitHub CodeQL

@vercel

vercel Bot commented Jun 25, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
inferencemax-app Ready Ready Preview, Comment Jul 3, 2026 5:35pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant