@algora-pbc /claim #18

Summary

• Add a self-contained Scientific Bounty System module focused on sponsor-side challenge intake before publication.
• Validate sponsor verification, problem statement completeness, deliverables, rubric weights, milestones, prize escrow, NDA/data-room setup, prequalification, IP policy, and timeline.
• Expose local API endpoints for dashboard, validation, publish decisions, participant prequalification, and sponsor audit packets.

Differentiation

• This is intentionally earlier in the bounty lifecycle than arbitration, scoring, reward routing, or payout ledgers.
• It catches incomplete challenge setup and unsafe sponsor-side terms before solvers start work.

Validation

• npm run check
• npm test
• git diff –check
• PORT=4364 npm start
• curl -fsS http://localhost:4364/api/health
• curl -fsS http://localhost:4364/api/dashboard
• curl -fsS “http://localhost:4364/api/validate?id=challenge-biomarker-rna”
• curl -fsS “http://localhost:4364/api/publish-decision?id=challenge-climate-forecast”
• curl -fsS “http://localhost:4364/api/prequalification?challenge=challenge-biomarker-rna&application=app-immune-lab”
• curl -fsS “http://localhost:4364/api/audit-packet?id=challenge-biomarker-rna”

Demo notes are in bounty-intake-compliance-gate/demo/demo-text.txt; requirement coverage is mapped in bounty-intake-compliance-gate/docs/requirement-map.md.