Repository navigation
Analysis results say where their data came from - #40
Merged
Merged
Conversation
Every analysis result now lists its sources: each database of this deployment and each peer reached over MCP, with the studies it answered for. Each view's participation records point into that list (`source`, an index). - A peer reports itself in every federated answer (`source`: its own name, the commit it runs, and when the study it answered for was last imported there; lib/provenance.ts). A remote resolver keeps the first such report and when it came; every call now goes through one method (`call`) so none is missed. - A source carries this deployment's label for it and, separately, what the peer calls itself, so a mislabelled setting shows rather than hides; the peer's MCP address; its build; when it first answered; each study's import date. A local database gives its import dates and this build. - The Analysis tab says it under the cohorts, when there is more than one source or a remote one: "Data from: primary (local) — MSK-CHORD, imported 2026-07-30 · GENIE (simulated peer) (via MCP, calls itself “GENIE”) — GENIE BPC NSCLC v2.0-public, imported 2026-07-27", with the address, build and time on hover. MCP's run_analysis text says the same. - test/provenance.test.ts: one source per database and per peer endpoint, the peer's report kept apart from the label, the views' indexes matching the list. Verified: scripts/gate.sh green (1262 unit, 253 e2e). On the dev server (GENIE over MCP) the demo analysis lists both sources with the peer's report and both import dates; the page shows the line, no page errors. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QLBVrkqBG7J7pqX6Qygx3z
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
Every analysis result now lists its sources: each database of this deployment and each peer reached over MCP, with the studies it answered for. Each view's
participationpoints into that list.run_analysistext says the same.Verified:
scripts/gate.shgreen, with 1262 unit tests (new:test/provenance.test.ts) and 253 e2e checks. Checked on a dev server with GENIE over MCP; the page showed the line and had no errors.🤖 Generated with Claude Code
https://claude.ai/code/session_01QLBVrkqBG7J7pqX6Qygx3z