This guidebook is a textbook-style manual for the AgentCures ecosystem. It teaches both the science and the system design, so readers can move from "I have a drug discovery objective" to "I have an executable, auditable campaign."
- Research engineers learning discovery workflows
- Computational scientists building model pipelines
- Platform engineers operating campaign infrastructure
- Wet-lab and preclinical teams integrating operational evidence
- Clinical strategy teams planning trial simulations
- QA, governance, and regulatory stakeholders reviewing readiness
Pick a reading track:
- Fast onboarding track: Chapters 1, 2, 4, 8
- Science depth track: Chapters 1, 3, 5, 9, 10
- Operations track: Chapters 2, 5, 7, 8
- Governance track: Chapters 5, 6, 8, Appendix B
If you read straight through, the guidebook follows one continuous story:
- understand how discovery decisions are actually made under uncertainty
- learn how the platform turns intent into typed, executable workflows
- run an end-to-end campaign with evidence and gate controls
- deepen into medicinal chemistry and development-stage decision science
- Chapter 1: Drug Discovery For Builders
- Chapter 2: Platform Architecture
- Chapter 3: Refua Core Science Engine
- Chapter 4: ClawCures Campaign Orchestrator
- Chapter 5: Program Lifecycle Modules
- Chapter 6: Quality, Governance, and Evidence
- Chapter 7: Deployment and Runtime Operations
- Chapter 8: End-to-End Walkthrough
- Chapter 9: Medicinal Chemistry and Molecular Optimization
- Chapter 10: Drug Discovery and Development Science
- Appendix A: Glossary
- Appendix B: Artifacts and Schemas
Use these artifacts while reading:
- Campaign lifecycle data (CSV)
- Traceability matrix (CSV)
- Tool call examples (JSON)
- Medicinal chemistry property guide (CSV)
- Development stage-gate map (CSV)
flowchart TD
U[Team Objective] --> C[ClawCures Planning]
C --> M[refua-mcp Typed Tools]
M --> R[refua Modeling]
M --> D[refua-data]
M --> W[refua-wetlab]
M --> P[refua-preclinical]
M --> L[refua-clinical]
C --> H[refua-schema Portfolio Model]
C --> S[clawcures-ui]
S --> B[refua-bench]
S --> G[refua-regulatory]
X[refua-deploy] --> C
X --> M
X --> S
Each chapter follows a consistent layout:
- learning goals
- conceptual model
- concrete package mapping
- practical checklists
- common failure modes
- chapter handoff to next topics
- "Campaign" means one executable objective with traceable artifacts.
- "Tool call" means a typed JSON request handled through
refua-mcp. - "Gate" means a formal quality or policy checkpoint.
- "Evidence" means reproducible and integrity-verifiable outputs.
This guidebook describes software, simulation, and operational workflows. It does not claim therapeutic efficacy or regulatory approval outcomes.