English | 中文

A disease-focused medical research workspace for turning data, study questions, and evidence into manuscript-ready work

Disease Studies · Evidence Organization · Manuscript Delivery

Med Auto Science is for teams already doing real medical research. It keeps topic framing, data preparation, evidence progression, progress reporting, and manuscript-facing delivery on the same line.

You can start with prompts like:

• "Help me find a paper-worthy question from this colorectal cancer dataset, tell me what evidence is still missing, and propose the next step."
• "I already have preliminary results. Turn them into one manuscript line and tell me what validation to do next."
• "Keep pushing this disease study toward a publishable paper, and keep the progress plus files organized as we go."

• Finding a study question worth continuing from a disease-specific dataset, registry, or cohort.
• Turning existing analyses and early results into one manuscript line with clear next evidence steps.
• Keeping long-running work organized when files, figures, notes, and drafts would otherwise drift apart.
• Managing validation, subgroup analysis, calibration, clinical utility analysis, and other supporting evidence in the same workspace.
• Delivering manuscript-facing outputs as files that stay tied to the study they belong to.

• Researchers provide the clinical question, dataset, constraints, and final judgment.
• The AI operator moves the study forward through data preparation, analysis, evidence organization, and progress reporting.
• The workspace keeps tasks, files, progress, and delivery artifacts together so the whole line stays reviewable.

• Med Auto Science is the medical research workflow inside the broader OPL workspace.
• It owns study intake, workspace context, evidence progression, progress reporting, and manuscript-facing delivery.
• Clinical framing, claim acceptance, and submission decisions stay with researchers and PIs.
• Journal submission and external system interaction stay under human supervision.

1. Potential users and medical experts should start here, then continue to the Docs Guide.
2. Technical readers and planners should read Project, Status, Architecture, Invariants, and Decisions.
3. Developers and maintainers should continue from the Docs Guide into docs/runtime/, docs/program/, docs/capabilities/, docs/references/, and docs/policies/.

• Docs Guide
• Project
• Status
• Architecture
• Invariants
• Decisions