The Compliance Expedition

The Duck Has Repository Access

During the final TeachUEasy rehearsal, Ksusha discovers the rubber duck beside the three-minute video timer.

1. Ksusha: 😐 Why does the rubber duck have repository access?
2. Oleksandr: It found the licensing issue before I did.
3. Vitaliy: Technically, that makes it a contributor.
4. Ivanka: 😂 Then put its collaboration in the README.
5. Oleksandr: Please don't create an authorship ambiguity at midnight.
6. Ksusha: Midnight? The deadline is 5:00 p.m. Pacific Time.
7. Oleksandr: Excellent. My nontechnical reviewer now frightens me.
8. Ivanka: Good. Fear may help you cut the three-minute video.
9. Vitaliy: Not the part where TeachUEasy generates the lesson. That proves it's viable.
10. Ksusha: Keep that. Cut the forty seconds of spinning loader.
11. Oleksandr: 😬 The loader demonstrates suspense.
12. Ivanka: It demonstrates that judging access might fail.
13. Vitaliy: And where is the Codex Session ID?
14. Oleksandr: In the submission form, beside the repository and README.
15. Ksusha: Does everything comply, including the music?
16. Ivanka: No music, no infringement, and no dancing duck.
17. Oleksandr: 😐 Fine. The Official Rules prevail over choreography.
18. Ksusha: 😂 Too late. The duck has already submitted a substantially different project.

At 9:02 on a humid July morning, Oleksandr opened TeachUEasy, placed a rubber duck beside his laptop, and announced that he would win OpenAI Build Week by generating the perfect language lesson. The fan hummed over a cold cup of coffee. Then Ksusha tapped the Official Rules with her paper checklist. The AI tool already existed, she observed, so calling every feature new would be like putting fresh parsley on yesterday's soup. Because the project was pre-existing, Oleksandr needed to prove a meaningful extension built with Codex and GPT-5.6 during the submission period. He chose the Education track and began preserving timestamped Codex logs and dated commits. Vitaliy arrived carrying an IT textbook heavy enough to flatten the keyboard. He inspected the repository, licensing, English description, README, and Codex Session ID while the printer clicked like an impatient judge. Ksusha then tested the product without technical vocabulary. When a lesson appeared with a story, dialogue, grammar, homework, and interactive exercises, she nodded—but stopped the celebration music. It might cause infringement, and the public YouTube demonstration needed audio, not copyrighted thunder. She set a timer for the three-minute video. Oleksandr tried to demonstrate sixteen features in 178 seconds; his narration became so fast that even automatic captions appeared to request judging access. Because the demo was incomprehensible, Ivanka joined remotely through crackling headphones. Although she and Oleksandr had known each other for years without meeting in person, she deleted his dramatic introduction without hesitation. She checked whether the project was viable, worked consistently, fit its theme, and meaningfully used the required technology. Vitaliy noted that multiple entries were allowed only when substantially different. Ksusha added that access must remain free through August 5. Any ambiguity, Ivanka warned, required written clarification before the deadline, and the Official Rules would prevail over conflicting plugin advice. At dawn, Oleksandr made a choice: fewer fireworks, stronger evidence. He recorded one teacher creating a complete lesson, showed the new Codex-assisted workflow, documented what predated the event, and tested the public link in a private browser. The pale screen displayed a working lesson before the July 21, 5:00 p.m. PT deadline. Ksusha ticked the final box; Vitaliy closed his textbook; Ivanka raised a mug on-screen. Beside the green checklist, the rubber duck wore a tiny paper rocket.

Independent Compliance Check