Required
Use OpenCoven
Show commands, sessions, workflow evidence, architecture, or integration code. A ceremonial mention is insufficient.
Public beta // 120.5-hour build window
Summon something
that stays.
Build a greenfield, MIT-licensed open-source project with OpenCoven. Use the beta materially, document what worked, fix what did not, and ship a frozen public GitHub artifact.
EVENT CLOCK
LOADING
01 // Challenge
One new project. One frozen public artifact.
The project must be greenfield, publicly available on GitHub at submission, and licensed under the standard MIT License without added restrictions. OpenCoven must be used materially during development, at runtime, or both.
Required
Start greenfield
Project-specific implementation begins only after August 2 at 11:30 PM EDT.
Required
Publish under MIT
Public GitHub repository, complete source, frozen tag, and standard unmodified MIT License.
Bonus
Add a capability
Earn up to 10 points for a working new OpenCoven feature, integration, skill, surface, or workflow.
Bonus
Earn adoption evidence
Earn up to 5 points when an authorized maintainer publicly confirms intended upstream adoption.
Beta ledger
Fix reproducible bugs
Merged, focused fixes can add up to 10 points. Security findings remain private.
02 // Prizes
Inference access for the next build.
Winners select an approved major inference provider. Expected choices include OpenAI, Anthropic, and Google. Fulfillment may be a subscription, credits, tokens, an approved gift card, or reimbursement.
First place
$100
USD value toward approved inference access.
Second place
$50
USD value toward approved inference access.
Third place
$25
USD value toward approved inference access.
03 // Score ledger
100 core. 25 bonus.
A project must earn at least 60 core points to be prize-eligible. Bonus points cannot cure an ineligible or nonfunctional entry.
| Core category | Points |
|---|---|
| OpenCoven use and evidence | 20 |
| Technical execution and reliability | 25 |
| Originality and usefulness | 20 |
| Reproducibility and documentation | 15 |
| Product experience and OpenCoven fit | 10 |
| Security, privacy, and responsible provider use | 5 |
| Demo clarity and completeness | 5 |
| Core total | 100 |
| Bonus category | Maximum |
|---|---|
| New OpenCoven capability | 10 |
| Documented upstream adoption intent | 5 |
| Merged reproducible-bug fixes | 10 |
| Maximum total | 125 |
04 // Submission gate
Midnight means Friday night.
The deadline is Saturday, August 8 at 12:00 AM EDT: midnight at the beginning of Saturday. Your public repository, frozen tag, and submission message must exist before 12:00:01 AM.
Final reference: push
july-hackathon-2026-final, record the full commit SHA,
and submit the public repository and demo through an issue in the event repository.
05 // Judges
Two scorecards. One frozen commit.
Judges score independently, reconcile factual differences, average valid totals, disclose conflicts, and apply the published tie-break order.
06 // Common questions
Before you commit.
These summaries do not replace the Official Rules.
Can the repository be private during the event?
Yes. It must be public, complete, and accessible before the deadline.
Must the project integrate OpenCoven at runtime?
No. Material development-workflow use can qualify. Runtime integration creates more opportunity to demonstrate depth.
Can AI-generated code be used?
Yes. The team remains responsible for originality, licensing, review, security, and behavior.
What does “MIT, no modifications” mean?
Use the standard MIT permission and warranty text. Populate only the year and copyright holder. Do not add restrictions, riders, exceptions, or a conflicting dual-license requirement.
When are winners announced?
Primary: August 9 at 11:30 PM EDT. Fallback, if review volume requires it: August 16 at 11:30 PM EDT.