binder-design-campaign

# Gated protein design campaign Three branches, one core. Pick the branch at G0; the gates, evidence rules and deliverable discipline below hold for all three. | Branch | Read | For | |---|---|---| | binder design | `workflows/binder-design.md` | miniprotein binders against a protein target | | structure prediction | `workflows/structure-prediction.md` | folds or complexes with calibrated confidence | | protein engineering | `workflows/protein-design-general.md` | stability, enzyme, interface, scaffold redesign | Provenance and rationale: `docs/` and `NOTICE.md`, relative to this skill. ## Non-negotiables These hold at every depth, including inside sub-agents, and bind hardest on the steps nobody is watching. 1. **State only what you established.** Every claim in a report, update or manifest traces to an executed computation or a saved artifact you can point at. *Verified* means you ran the check and hold its output. 2. **Every external identifier is fetched.** DOIs, PMIDs, PDB IDs, UniProt accessions, residue ranges and URLs in any deliverable are the literal output of a lookup executed in this session. 3. **Anomalies are bugs until investigated.** A score of exactly zero, a gate that passes everything, a gate that fails everything, a constant metric, a perfect metric, an impossible runtime, zero variance across seeds: halt that stage, diagnose, then proceed. 4. **Cheapest falsifying check first.** Run the seconds-scale check that could kill a p...