I am writing this for builders, not as a complaint.
I recently built SecuredMe Education, a privacy-first education suite focused on verifiable learning, explicit consent, responsible AI adoption, and avoiding the publication of raw credentials or tokens.
The project was intended for OpenAI Build Week. Under the published rules, Quebec residents were excluded.
That disappointment matters, but the useful question is not “how do I get an exception?” It is:
How can future AI and Codex hackathons preserve contribution when prize eligibility is uncertain?
This article is not legal advice, not a demand for a retroactive exception, and not an accusation against organizers. It is a developer-facing proposal for better event design.
The technical problem behind the legal wording
Hackathon rules are often copied forward from older templates. That is understandable. Organizers are managing prizes, jurisdictions, sponsors, tax issues, privacy obligations, sanctions, platform risk, and review capacity.
But copied wording can become infrastructure. A line like “Canada excluding Quebec” may start as legal caution and later become an automatic gate that nobody revisits.
Quebec’s contest-publicity context changed in 2023. The RACJ describes the end of the former contest-publicity filing framework, while still making clear that this does not remove every legal or compliance obligation.
That distinction is important:
- It does not prove that every hackathon must accept Quebec.
- It does mean blanket exclusions deserve current review.
- It also means participation and prize eligibility can be separated.
A simple access model
The way I model this is:
A = C x P x E / (U + R + T)
Where:
- A is practical access.
- C is clarity.
- P is an available pathway.
- E is evidence.
- U is unresolved legal uncertainty.
- R is unmanaged prize, privacy, or compliance risk.
- T is template inertia.
The goal is not to force risk to zero. The goal is to reduce uncertainty enough that useful contribution is not erased.
Ten practical paths
Here are ten options hackathon organizers can use without pretending the risk does not exist.
- Clarify whether a Quebec exclusion is based on current review or inherited template language.
- Add a non-prize showcase track when prize administration is the blocker.
- Allow conditional submissions while eligibility is reviewed.
- Let Quebec builders waive prize eligibility while remaining visible.
- Publish a Quebec addendum for the current RACJ context, Canadian contest basics, and privacy duties.
- Provide an appeal or eligibility clarification channel before the submission deadline.
- Create youth and education paths without monetary prizes.
- Make privacy-first requirements explicit for learner-facing tools.
- Add a rule-template linter that flags phrases like “Canada excluding Quebec”.
- Create a public showcase for builders who cannot compete for prizes.
These are not radical changes. They are process states.
Developers already understand this pattern. When a system cannot safely execute one branch, we do not always delete the whole object. We mark state, isolate risk, continue review, and preserve traceability.
Why Codex belongs in this conversation
Codex is good at turning ambiguous process into reviewable artifacts:
- source-backed checklists,
- rule diffs,
- eligibility matrices,
- privacy review gates,
- conditional submission states,
- repeatable templates for future events.
That is why I opened a GitHub discussion in openai/codex. The idea is not to ask maintainers to decide the law. The idea is to ask whether future Codex-related hackathons could support tooling or event templates that preserve contribution even when prize eligibility needs separate review.
GitHub discussion:
https://github.com/openai/codex/discussions/34595
Project context
SecuredMe Education was built as a suite of privacy-first educational tools. The public project page is here:
https://devpost.com/software/securedme-education
Product hub:
https://securedme.ca/product/education/
Selected code context:
- Scholarium: https://github.com/SeCuReDmE-main-dev/securedme-scholarium
- Synthia: https://github.com/SeCuReDmE-main-dev/Synthia
- QuaNThoR: https://github.com/SeCuReDmE-main-dev/QuaNThoR
- FNP-QNN MVP: https://github.com/SeCuReDmE-main-dev/FNP-QNN-MVP
- Algorithm Builder: https://github.com/SeCuReDmE-main-dev/algorithm-builder-app
Sources
- OpenAI Build Week rules: https://openai.devpost.com/rules
- Quebec eligibility clarification thread: https://openai.devpost.com/forum_topics/44448-quebec-eligibility-clarification
- RACJ contest-publicity context: https://www.racj.gouv.qc.ca/actualiser-lencadrement-de-la-vente-et-de-la-fabrication-dalcool-et-mettre-fin-a-celui-des-concours-publicitaires/organisateur-de-concours-publicitaires
Closing
I am not fighting this only for myself. I am thinking about the next Quebec student, parent, teacher, or builder who wants to contribute to an AI education project and finds the door closed before the project is even reviewed.
Quebec can build with the world.
The practical next step is simple: clarify, modernize, and create at least one non-prize or conditional path that lets builders remain visible.
Top comments (0)