Keep the contradiction alive.
System note · biomedical
Circuit Compass
Decision-support loop
Do not collapse the paradox.
Make it testable.
Compensation
Desensitization
Activity elevation
Network failure
Score directions; preserve cohort and modality limits.
Confounds · replication · statistics · alternative mechanisms
The handoff narrows what the wet lab should discriminate.
01
Start with competing explanations
The project began with a collaborator’s experiment where behavior and molecular readouts appeared to disagree. The pipeline organizes possible explanations rather than selecting one plausible story immediately.
My part was computational. I wanted the handoff to make the alternatives inspectable: what supports each explanation, what else could produce the same observation, and which measurement would distinguish them. Choosing a plausible mechanism too early would make the software look more decisive than the evidence allowed.
02
What I built
I built the data-ingestion, analysis, literature, figure, and handoff workflow. It uses public single-nucleus datasets and aggregates measurements at the mouse level when biological replication permits that analysis.
The output brings hypotheses, supporting evidence, limitations, and proposed follow-up measurements into one reviewable document. Synthetic installation checks are kept separate from real-data outputs.
03
Where interpretation remains uncertain
The existing critique identifies cohort and sex/strain confounding, limits of replication and cell annotation, and the distance between RNA measurements and protein or circuit behavior. Several mechanisms may fit the same signature.
Those limitations determine what needs checking next. The pipeline does not establish a biological mechanism or substitute for the collaborator’s experiment.
04
What is available here
The implementation is not currently public. This page explains the workflow and its limits; it is not a reproducible release of the analysis.
This is a practical reason I care about independent verification. A computational workflow can organize more explanations than a team could easily work through by hand, but the usefulness depends on what happens at the handoff. I want a collaborator to be able to challenge the explanation and choose a measurement that could prove it wrong.
Source material · availability checked 11 September 2026
What can be inspected publicly
The implementation is not currently public. This page describes the workflow; it does not release collaborator data or establish a biological mechanism.