CollectiveX v1: isolated EP results explorer#497
Draft
Oseltamivir wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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
Adds an isolated
/collectivexEP results explorer for sanitized CollectiveX datasets.What changed
failure, and provenance views using the shared D3 chart stack
[cl],[rv], LL, and legacy schemas available only when diagnostic data is explicitly loadedofficial-headlinepublication viewcollectivex.ep.v1rows that are official,decision-grade, workload-attributed, and on the fixed sampling contract
and source SHA; unknown provenance and cross-EP configuration splices fail closed
unsafe cross-hardware comparison
Data boundary
The page reads
/data/collectivex.jsonwithno-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