Lab Atlas v0.5

This is the canonical linked Markdown knowledge base for the tenOever lab as of v0.5.

v0.5 incorporates two organizing inputs:

1. The v0.4 Lab Atlas snapshot.
2. The strategic lab repositioning memo that frames the research program as programmable respiratory viral systems that dissect and direct host biology.

The Atlas should function as a laboratory operating system, not a static report. It preserves people, projects, methods, vectors, datasets, collaborations, infrastructure, grants, meetings, protocols, scientific rationale, abandoned ideas, and unresolved questions.

Start Here

• INDEX
• PROGRAM ARCHITECTURE
• DASHBOARD
• PROJECT FAMILY MAP
• PROJECT DEPENDENCY MAP
• CAPABILITY MAP
• DISCOVERY MAP
• MANUSCRIPT TRIAGE
• VECTOR REGISTRY
• DATASET REGISTRY
• OPEN QUESTIONS
• NEGATIVE RESULTS AND ABANDONED IDEAS
• ONBOARDING MAP
• Source Manifest

Core Identity

The lab builds programmable respiratory viral systems to reveal how infection, sensing, inflammation, antigen acquisition, and tissue context shape host biology, and to translate those principles into next-generation delivery and therapeutic platforms.

Three Connected Research Lanes

1. Mechanistic Pathogenesis
2. Programmable Immune Instruction
3. Respiratory Delivery and Therapy

These lanes are not silos. Most projects live at the interface of at least two lanes. The Atlas should therefore prioritize cross-links, dependency maps, and explicit project-family structure over isolated project descriptions.

Design Principles

• Lead with biological questions and principles, not methods.
• Treat miRNA silencing as mature enabling infrastructure unless a project is specifically about the logic itself.
• Treat influenza as a discovery engine, not the only public-facing container.
• Preserve uncertainty, negative results, pivots, and working models.
• Separate capabilities from discoveries.
• Make every project useful for planning, onboarding, grants, manuscripts, mentoring, and institutional memory.