Loading...
Astana time (UTC+5)
Media Literacy: Play Your Part. UNESCO invites youth aged 18–30 from all over the world.
Registration is on the organizer’s site. Opens a new tab.
Before registering, save a local copy or PDF of the current page, the check time, and the document address. Compare at least: official rules/terms, overview page, FAQ, prizes page, specific track requirements, platform rules, code of conduct, and schedule. If the wording differs, you cannot independently choose the more convenient one. Write to the organizer, quote both fragments, and ask them to specify the controlling document.
A separate source of rules has been fixed for this card: open. Main page: event. Status: Open. Changes to the status, deadline, prizes, or eligibility after the catalog is published are possible, so a final check must be done immediately before registration and once more before submitting the work.
These values describe only the known state of the data. They do not automatically answer questions about the citizenship and residency of each participant, organizer employees, relatives of the jury, sanctioned territories, export control, corporate participation, or receipt of monetary payments. Such restrictions are often found deeper in the legal document.
The database indicates Yes — direct. Proof: UNESCO invites youth aged 18–30 from all over the world.. Before applying, each person must verify their own situation, not just the team's country. Age on the reference date, citizenship, country of permanent residence, place of study or work, student status, affiliation with a company, participation in multiple teams, and possible conflicts of interest are checked.
If the participant is a minor, find the exact requirements for parental consent, account, travel, public broadcast, and receiving the prize. If the application is for students, check the acceptable type of educational institution, form of study, graduation date, and documents that may be requested after selection. If an organization is participating, clarify the employee limit, the representative's right to bind the company to terms, and who owns the materials.
Recommendation, not a rule: send the organizer a short letter with facts that cannot be interpreted in two ways: "citizen/resident of Kazakhstan, age, study or work status, participation format, team of N people". Save the written response. The organizer's silence does not equal consent.
In the card, the start is 06.07.2026, the end is 16.08.2026, and the deadline is 16.08.2026. A date without an exact time is insufficient for safe planning. Find out the time zone, whether the platform takes into account daylight saving time, whether registration closes before the project submission, and whether materials can be edited after the initial publication.
Create an internal deadline at least a day earlier for a long competition or a few hours earlier for a short one. Separately plan account verification, email confirmation, inviting participants, access to the track, video upload, checking public links, and the final Submit click. A screenshot of a draft does not prove a completed submission; after sending, save the confirmation page and the platform's email.
Clarify exactly what end date means: end of development, submission deadline, demo day, judging, or announcement. If pages contain different dates, assume the earlier one as a precaution and simultaneously request an official clarification.
Fixed: 2–6. Do not infer permission for solo, replacing participants, cross-country teams, or one person participating in multiple projects unless it is in the rules. Check the minimum and maximum size, the moment the roster is fixed, requirements for team lead, the procedure for removing or adding a participant, and whether individual registration is mandatory.
Recommended work organization: product lead, developer, designer or subject researcher, and a person responsible for testing and submission. Before starting, record the owner of each repository, data source, cloud account, mockup, video, and submission form. Agree on the distribution of potential monetary and non-monetary rewards, the right to continue the project, the order of authorship, and actions in case a participant leaves. This is a private team agreement; it must be compatible with official terms.
It is forbidden to assume that a mentor, teacher, or contractor can write part of the solution. Find the exact definition of participant and permitted external assistance. If the rule is unclear, describe the third party's contribution in the submission and request approval in advance.
Structured fields do not contain enough information to determine whether all code must be created during the event, whether an old project can be continued, whether the repository must be public, and which license to choose. These four points must be found in the official rules. Before confirmation, a safe practice is to separate previously created components, maintain a change history, and list external libraries, models, templates, datasets, and assets.
Check dependency licenses and compatibility with future publication. Do not upload employer's private code, API keys, personal data, paid sets, music, images, or models without permission. In the README, specify the origin of data and third-party materials, version, license, and the team's own contribution. If the organizer receives a license for submitted materials, analyze its scope, duration, territory, right to sublicense, and promotional use. If the rules say IP remains with the team, this still does not override the rights of third parties.
For the topic "applied technologies and open innovations," pay special attention: do not use data, code, or content without rights, do not claim unverified effectiveness, and do not hide dependence on external services. This is a safety and quality recommendation unless the official document sets stricter requirements.
The topic is written as Media Literacy: Play Your Part. UNESCO invites youth aged 18–30 from all over the world.. It does not prove the existence of a mandatory API, SDK, model, cloud, device, or sponsor technology. On the specific track page, find the minimum requirement for using the technology and how to prove it in the demo or repository. Save SDK versions, region settings, and limit checks. Check if the service is available from Kazakhstan and accepts a Kazakhstani payment card if free credits turn out to be insufficient.
Separately, find out the rules for generative AI: is it allowed for code, design, text, music, and presentation; is disclosure required; who is responsible for the results' licenses. If the rules are silent, do not call the use of AI prohibited or allowed — request an answer and disclose significant use voluntarily.
Good technical control for this topic: choose one user and one problem, write down the basic process and success criteria, then build a minimal end-to-end scenario. Expected verifiable artifact: a working vertical prototype, brief architecture, verifiable user scenario, test results, and honestly described limitations. Metrics that can make the demonstration convincing: completion rate, time, quality, cost, error resilience, and target audience feedback. This is not an official scoring rubric until it matches the published criteria.
Find the full list of mandatory fields: title, short description, track, repository, working link, images, presentation, video, tech stack, participants, license, and answers to questions. For each field, define the format, volume, language, and accessibility without authorization. If a link requires an invitation or a regional account, the judge may not see the result.
Recommended kit: README with the problem and launch instructions; architectural diagram; list of sources and licenses; short demo without accelerated or hidden steps; backup recording; test data; metrics table; limitations section; team contacts. Show the initial problem, user action, solution operation, measurable result, limitation, and next experiment. Do not claim a feature if it is shown only by a mockup, and do not mask a manual operation as an automatic one.
Check the video duration and the ban on editing, publicity requirements, allowed hosting services, and the presence of subtitles. Before submitting, open all links in a private window and on another device. If a live pitch is required, prepare roles, a two-minute version, and answers regarding the user, architecture, data, limitations, and next steps.
Jury criteria cannot be reconstructed from the topic. Find the published rubric and turn each criterion into a row in an internal table: team statement, evidence, location in the demo, and responsible person. If the criteria contradict the marketing description, rely on the controlling rules and ask the organizer.
Practically strong evidence answers four questions: what was before the project; what exactly the team did; how the result was measured; where the solution stops working. For "applied technologies and open innovations," useful measurements are: completion rate, time, quality, cost, error resilience, and target audience feedback. Show at least one complex or negative example. This increases trust and helps distinguish engineering work from a beautiful scenario.
Do not assume that the most technically complex work will automatically win. Often, alignment with the challenge, clarity, usefulness, quality of execution, and implementation potential are important. But exact weights can only be named after reading the rubric.
Confirmed: Winners are invited to Greece on 26–28.11; the trip is covered. Entry fee terms: Free. Check if the headline is the sum of monetary and non-monetary awards, how many winners share the fund, if there are separate tracks, if it is possible to receive multiple prizes, and if the organizer can replace the award. Find the winner verification procedure, response deadlines, required documents, and consequences of being unable to accept the prize.
International payment may require an ID, bank details, tax form, age verification, and sanctions screening. Do not send documents through unofficial channels and verify the email domain. The team must assess taxes in Kazakhstan themselves; this card is not tax advice. Credits and subscriptions have value only if the service is accessible, has a useful validity period, and there are no mandatory costs beyond the limit.
Format: Online; location: Online → Greece; confirmed travel conditions: Travel to Greece is covered for winners. If there is an in-person stage, clarify whether attendance is mandatory for eligibility or only for the final, who pays for flights and accommodation, when the invitation letter is issued, and whether it is possible to switch to online if a visa is denied.
Do not purchase non-refundable tickets until official acceptance and clear compensation terms are provided. An invitation letter does not guarantee a visa. Check passport expiration, insurance, hotel age requirements, accompaniment of minors, and equipment transport rules. For overnight events, plan for sleep, food, medication, and a safe route to your accommodation. These measures are practical safety steps, not stated organizer terms.
Find the code of conduct, incident reporting channels, photo and broadcast rules, privacy policy, and account retention terms. Do not publish personal data of testers, closed challenge materials, or contact details of other participants. Use synthetic or legally obtained data, minimal access rights, and separate keys for the hackathon.
The team must honestly disclose previously completed work, external assistance, generative tools, prototype limitations, and manual steps. Do not inflate metrics, votes, or views, and do not test security beyond the permitted scope. When in doubt, request written permission.
An additional risk is noted: This is an ideas challenge: a working application is not mandatory; submission in EN.. Recommended next step: Gather 2–6 people; prepare a proposal and a 3-minute video. Catalog priority: A — submit now. These three fields are for planning purposes and are not part of the official rules.
