by hypothesis debate

Other Community v1.0

Skill notes

When to Use This Skill

✅ Use this skill when: Starting a campaign against a novel target (0–1 PDB structures, no SAbDab antibodies, <10 papers) Research findings have CONTRADICTED confidence (sources disagree on epitope, modality, or scaffold) Multiple viable modalities are on the table (VHH vs scFv vs de novo binder) and the user has not pinned one The user explicitly says "compare approaches", "explore options", "which strategy would you pick"

Quick Start

Invoke from the orchestrator (main session) after by-research has written research.md and recommended_hotspots.json to the campaign directory: Expected runtime: 4–8 minutes (3 hypothesis agents run in parallel ~3 min each, reflection agent runs sequentially ~2 min). Expected output: debate/proposals/ with three strategy_proposal.json files, debate/ranking.json, and an

Inputs

Required: Research report directory — must contain research.md, recommended_hotspots.json, design_recommendation.json, and validated_findings.json from by-research (8-phase pipeline) Campaign config skeleton — a YAML file with target, pdb_id, compute block, but modality, scaffolds, tier are TBD Alternative inputs: campaign_context.json — if present (from /by:plan-campaign), the user's preferences seed the agents but do NOT override the debate. Agents see the preference as a prior, not a constraint

Outputs

All outputs land under <campaign_dir>/debate/: File · Description · Written By proposals/conservative.json · Strategy proposal from Conservative agent · hypothesis agent 1 proposals/aggressive.json · Strategy proposal from Aggressive agent · hypothesis agent 2 proposals/diverse.json · Strategy proposal from Diverse agent · hypothesis agent 3

strategyproposal.json Schema

Every hypothesis agent writes one of these. Validation: scripts/validate_proposal.py.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@001TMF · v1.0 · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Verify Research Inputs

✅ VERIFICATION: All four files exist and `validated_findings.json` has at least 1 finding with confidence `HIGH` or `MEDIUM`. ❌ DON'T: Start the debate if research is incomplete — agents will hallucinate.

02
Step 2: Run the Orchestrator

Expected stdout:

03
Step 3: Validate Proposals (Automatic)

The orchestrator calls `scripts/validate_proposal.py` on each proposal before passing to the reflection agent. If a proposal fails validation, it is dropped and reported. The reflection agent never sees malformed proposals.

04
Step 4: Review the Decision

Read `<campaign_dir>/debate/decision_summary.md`. Present the winner to the user with the dissenting notes from runners-up.

05
Step 5: Hand Off to by-campaign-manager

Once the user approves the winner, the updated `campaign_config.yaml` flows directly into `by-campaign-manager` for execution. No re-planning needed.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.