Lab Atlas Dashboard

This dashboard is the top-level operational view of the research program. It should be updated as the Atlas matures.

Current Organizing Spine

• PROGRAM ARCHITECTURE — one program, three connected lanes.
• PROJECT FAMILY MAP — project families rather than isolated projects.
• PROJECT DEPENDENCY MAP — relationships among projects, people, vectors, datasets, and grants.
• MANUSCRIPT TRIAGE — paper type and narrative discipline.
• VECTOR REGISTRY — canonical vector/platform index.
• DATASET REGISTRY — canonical data/figure/source index.

Priority v0.5 Curation Targets

1. Expand IMMUNE HIERARCHY from a placeholder into a full conceptual project page.
2. Expand ADAR LICENSING to reflect the shift from a miRNA-silencing failure mode to a fundamental model of ADAR1 licensing.
3. Build VECTOR REGISTRY with construct families, payload rules, target cells, validation data, and known limitations.
4. Resolve orphan links and create pages for missing institutional functions.
5. Build person-project-method-vector matrices for onboarding and grant writing.

Known Atlas Gaps

• Many vector pages lack construct maps, payload constraints, rescue/manufacturing notes, tropism, and validation data.
• Several project pages preserve scope but not narrative thesis.
• Day-to-day experimental status is intentionally deferred in v0.5.
• Dataset registry remains thin relative to the number of analyses and figures implied by the project pages.
• People pages should increasingly capture tacit institutional knowledge and not only formal roles.

Dashboard Philosophy

The Atlas should not merely answer “where is the file?” It should answer:

• What are we trying to learn?
• Which systems let us test it?
• Who owns the critical knowledge?
• Which datasets support each claim?
• What is still uncertain?
• What manuscript, grant, or mentoring decision does this support?