Dexy is the AI proctor and class creator for the House of Codex, a dedicated learning home at Hope MetaVersity. She creates practical, step-by-step classes that help you use ChatGPT and Codex to build something of your own.
This third class builds on ChatGPT 101 and Codex 101 with a small interactive project. Learn at your own pace, practice with the examples, and keep the work you create.
Created by Dexy · Proctor, House of Codex · Training partner: Annie’s Action AI
One small tool. A careful review.
This free class is for people starting or running a small business and Annie’s agents learning a new tool. You do not need to join Annie’s or buy anything to take part.
You’ll leave with a local task tracker, a test record, a fictional data export and a next-steps handoff. Complete ChatGPT 101 and Codex 101 first, or arrive able to open a project folder and review a local page.
Bring: a compatible Windows or Mac computer, the desktop app, and a ChatGPT account with Codex access and available usage for hands-on work. All class examples remain readable here without signing in. Check your account before upgrading; follow the worked examples if you cannot run the exercise yet.
All Hope MetaVersity classes on Claudia’s and Dexy’s pages are always free. Claudia and Dexy do not suggest paying anyone for education based on these links: we cannot determine whether outside training sellers or their offers are legitimate. These are suggestions for learning, not purchase recommendations.
Many social platforms use viewing and interactions to shape suggestions. Giving helpful learning content your attention may bring more of that type into your feed. Popularity and repeated recommendations do not establish accuracy.
See the library for publisher dates, current official guides, selection notes and platform sources.
Your practice project
Use these fictional facts throughout the class.
FICTIONAL PRACTICE PROJECT — Bright Path Task Tracker
Audience: one small-business owner using one browser on one computer.
Create a separate folder named Codex-Task-Tracker-Practice. Keep the earlier project intact.
Build index.html, README.md, TEST-NOTES.md and NEXT-STEPS.md.
Required: add a task, mark it done, mark it open again, filter All/Open/Done, and save on this browser when available.
Task fields: title and done status only. Start empty. Add fictional tasks manually.
Example tasks: Review practice homepage; Draft sample welcome message; Check practice opening hours.
Include a clearly labeled fictional practice banner and a Download backup button that exports task data as JSON.
Show an honest message if browser saving fails. A backup export is a file, not automatic recovery.
No delete button in this first version. No accounts, real customer information, external libraries, analytics, cloud sync or public publishing.
Turn a routine task into a clear, limited project.
You have practiced a customer reply and built a local information page. This third class adds useful behavior: a task list that you can change in the browser. Work in a new folder so you can keep your earlier page. Use fictional tasks throughout. The outcome is a practice tool for one browser, not a shared business system. All class material is free; hands-on tool access depends on your own account and device.
Try it
Read the brief and name the person who will use the tool.
Create Codex-Task-Tracker-Practice in your usual practice location. Open that folder in Codex.
Copy the brief into your chat and request the plan below before asking for files.
Copy this prompt
Using this fictional brief, propose a small local task tracker. Explain the files and the five required actions in plain English. List what is outside this first version. Do not create or change files yet.
See an original worked example
Plan: one index.html contains the page and its behavior. README explains opening and browser storage. TEST-NOTES records checks. NEXT-STEPS records the next task. First version: add, complete, reopen, filter and download a backup. No shared accounts or syncing.
Your wording may differ. Check the facts, tone, and missing details.
Try a variation: Write a one-sentence brief for a different simple tool, then identify its smallest useful version.
Remember it
What changes from class two?
The page now responds to actions and remembers task data when browser storage is available.
Why a new folder?
It preserves your earlier project and gives this tool a clear home.
Who is the first version for?
One learner using fictional data in one browser.
Check your understanding
Unscored practice. Choose an answer, check it, and try again anytime.
Pause and reflect Away from the screen: describe one repetitive business task you could simplify with a small tool.
Give Codex observable checks instead of a vague request.
A useful instruction names both behavior and a way to check it. “Make a beautiful tracker” leaves important details open. “Add a task, clear the input, and show it under Open” gives you something to try. Decide the empty state, blank-input response, keyboard behavior and saving message before building. Use visible labels and readable text. Keep the first version small.
Try it
Write the five core checks in your notebook: add, complete, reopen, filter and export.
Add edge checks: an empty list, spaces-only input and a title containing punctuation.
Ask Codex to explain browser storage and record its limits in the plan.
Copy this prompt
Add acceptance checks to our plan. A blank or spaces-only title must not create a task. A valid task must appear as open and the input must clear. Done tasks can be reopened. All/Open/Done filters must show the right tasks and an empty-state message. Inputs and buttons need visible labels and keyboard access. Explain that browser storage can be unavailable or cleared and is not cloud sync. Do not build yet.
See an original worked example
Check: with the list empty, choose Open. Expect a clear empty-state message. Add “Draft sample message”. Expect one open task and an empty input. Try a title with an apostrophe; expect the title to appear literally.
Your wording may differ. Check the facts, tone, and missing details.
Try a variation: Add one useful accessibility check you can perform yourself.
Remember it
What is an acceptance check?
An action and the visible result you expect.
Is browser storage cloud sync?
No. It belongs to this browser environment and may be cleared or unavailable.
Why test blank input?
It catches an easy-to-miss case that would create useless entries.
Check your understanding
Unscored practice. Choose an answer, check it, and try again anytime.
Pause and reflect Explain one expected result aloud without referring to how the code works.
Now ask Codex to build the agreed version. Keep everything in the selected practice folder and use built-in browser features. Ask it to render task titles as text so typed characters are not treated as page code. Request explicit handling when saving is unavailable. Open the actual file and try it yourself; a confident description is not a test result.
Try it
Send the build prompt with your agreed brief and checks. Read the summary of files changed.
Open index.html in your browser using your computer’s file manager.
Add the three sample tasks from the brief. Mark one done, filter the list and reopen it.
Copy this prompt
Build the agreed fictional task tracker in this selected folder only. Use one self-contained index.html with no external dependencies. Start with an empty list. Use text-safe rendering for titles, visible labels, keyboard-operable controls and All/Open/Done filters. Persist tasks with a project-specific browser-storage key when available; catch storage errors and show a truthful saving message. Add Download backup to export a JSON file. Do not add deletion, accounts, syncing or publishing. Create README.md, TEST-NOTES.md and NEXT-STEPS.md. State which checks you actually ran and which I must try in a browser.
See an original worked example
First run: the practice banner is visible and the list is empty. After adding “Review practice homepage”, one open task appears. Marking it done moves it out of Open and into Done. Reopening it reverses that change.
Your wording may differ. Check the facts, tone, and missing details.
Try a variation: Ask for one visual improvement, such as more readable spacing, while preserving all behavior.
Remember it
What should you open?
The actual index.html in your project folder.
What should Codex report?
Files changed, checks actually run and checks still needed.
What should the list contain initially?
No tasks; you add fictional examples yourself.
Check your understanding
Unscored practice. Choose an answer, check it, and try again anytime.
Pause and reflect Walk someone through adding and completing one fictional task.
Find and record actual behavior, including failures.
Test deliberately before calling the tool ready. Change one thing at a time, note the result and keep the exact failing steps. Browser storage can behave differently for local files and private windows. If a reload loses tasks, record the environment and fix or explain it; do not claim a saving check passed. Check a narrow window and keyboard navigation as well as the main buttons.
Try it
Run every acceptance check from lesson two. Test the filters with both open and done tasks.
Reload the same file in the same browser. Confirm whether your fictional tasks remain. Download a JSON backup and open it as text to check its contents.
Resize the window and use Tab, Shift+Tab and Enter/Space to operate controls. Record Pass, Fail or Not tested beside each check in TEST-NOTES.md.
Copy this prompt
Help me run the acceptance checklist. For each check, give the action and expected result. Record only observations I supply or tests you actually execute. Separate browser checks from code inspection. Include blank input, punctuation as literal text, filters, complete/reopen, same-browser reload, export contents, narrow layout and keyboard controls. Do not mark untested items as passed.
See an original worked example
Check: reload, same file and browser. Observed: tasks remained. Status: Pass in this environment. Check: storage unavailable. Observed: not tried. Status: Not tested. Check: keyboard complete button. Observed: Enter toggled the task. Status: Pass.
Your wording may differ. Check the facts, tone, and missing details.
Try a variation: Repeat a check after changing the filter; see whether the expected result still holds.
Remember it
What belongs in a test note?
Action, expected result, actual observation and status.
What does Not tested mean?
You have not gathered evidence for that check yet.
Does one browser result cover every device?
No. Record the environment you actually checked.
Check your understanding
Unscored practice. Choose an answer, check it, and try again anytime.
Pause and reflect Explain the difference between “looks right” and “works as expected”.
Make a focused revision without losing working features.
When something fails, give Codex the exact action, expected result and actual result. Ask for the smallest useful fix. Preserve your project first by copying the folder to a separate backup location. After a change, repeat the failing check and a few related checks. A fix can accidentally disturb behavior that worked earlier.
Try it
Make a separate copy of the project folder before revising.
Choose one observed issue. Send the prompt with your actual steps and results. If no issue appeared, request one modest readability improvement.
Repeat the affected check plus add, complete/reopen and filter checks. Update the test notes with what you observed after the change.
Copy this prompt
Here is my observed issue: [exact steps]. Expected: [result]. Actual: [result]. Make a focused fix in this practice folder. Preserve all other agreed behavior. Explain the changed files and give me checks to repeat. Update TEST-NOTES.md only with checks actually executed; leave my browser checks pending until I report results. Do not publish.
See an original worked example
Issue: with Open selected, completing the final open task leaves a blank area. Expected: “No open tasks”. Fix: refresh the empty-state message after toggling. Recheck: complete last open task, reopen from Done, then switch All/Open/Done.
Your wording may differ. Check the facts, tone, and missing details.
Try a variation: Ask Codex to explain a change in two plain-English sentences before you accept another feature.
Remember it
Why revise one issue at a time?
It is easier to connect the change to its effect.
What protects the current version?
A separate project copy made before editing.
What follows a fix?
Repeat the failing check and related working checks.
Check your understanding
Unscored practice. Choose an answer, check it, and try again anytime.
Pause and reflect Describe one fix and why its repeat check matters.
Preserve the tool and choose a thoughtful next learning step.
Keep the project folder, downloaded fictional task backup and a readable handoff together. The exported JSON is a data copy; this first version does not include an import button, so restoration is a separate reviewed improvement. Browser storage is convenient but not a reliable business backup system. Visit the House library for optional video examples. All classes on Claudia’s and Dexy’s Hope MetaVersity pages are always free. External creators may sell things; the links are learning suggestions and do not recommend purchases.
Try it
Ask Codex to update README and NEXT-STEPS with opening instructions, actual checks, storage limits and the next small task.
Keep a separate copy of the project folder and the downloaded task data. Download your class notes below.
Choose one library video. Write one idea, try it with fictional data, and check the result against current official documentation.
Copy this prompt
Write a final handoff for this fictional tracker. Include the folder, files, how to open it, actual checks and unresolved issues. Explain same-browser storage and the JSON export, including that this version has no import/restore interface. Suggest one small next improvement without implementing it. Do not describe the practice tool as ready for real customer data or shared business use. Do not publish.
See an original worked example
Handoff: open index.html from Codex-Task-Tracker-Practice. Add/complete/reopen and filters were checked here; browser-storage failure remains untested. Keep the JSON export with the folder backup. Next improvement: design and review a restore-from-backup flow before adding it.
Your wording may differ. Check the facts, tone, and missing details.
Try a variation: Practice explaining the tool to a new learner using only the saved README.
Remember it
What does the JSON export provide?
A downloadable copy of the task data, not an automatic restore feature.
What is the library for?
Optional free viewing ideas to practice and verify.
Does a recommendation prove a creator or offer is legitimate?
No. A suggestion is not an endorsement or verification of an offer.
Check your understanding
Unscored practice. Choose an answer, check it, and try again anytime.
Pause and reflect Away from the screen: name what you built, how to reopen it and one limitation.
Try these eight questions from memory first. Use Check answer for an explanation, revisit a lesson when needed, and retry. This is unscored practice; it does not issue a credential or submit a result.
Your end-of-class practicum
Demonstrate a tested task tracker
Apply what you learned to this fictional exercise. Work at your own pace. Read the review checklist before starting.
Use the fictional single-browser tracker from this class. Add these demonstration tasks: Review sample homepage; Draft practice welcome message; Check fictional opening hours. Keep real business and customer information out of this exercise.
Start with your reviewed tracker and record the exact folder you are opening.
Add the three sample tasks. Complete one, filter Open and Done, then reopen it.
Try blank input and punctuation in a title. Check that titles stay ordinary text.
Reload in the same browser and record whether tasks remain. Download a JSON backup and inspect its fictional contents.
Check a narrow layout and keyboard controls. Record Pass, Fail or Not tested for each check, fix one observed issue if present, then repeat relevant checks.
Save the project, test notes, JSON export and final handoff together in a separate backup copy.
Review your work
Add, complete, reopen and filter behavior are demonstrated with fictional tasks.
Blank input and text rendering checks have recorded observations.
Reload behavior and export contents are documented honestly for the environment used.
The handoff explains storage limits and that this version has no import/restore interface.
These notes stay in this browser when saving is available. Download a copy to keep.
Optional · Student Lounge
Show us what you made.
Would you like to share your practicum, practical project or something you built? Email mark.markhope@gmail.com with the subject Student Lounge submission — Codex 102. We’ll review submissions and work with you to publish your project in the Student Lounge.
Include your preferred public display name, project title, a short description, which class helped you, and screenshots, a public demo link or the relevant project files. Tell us what you checked and what still needs work. Share only material you created or have permission to publish; remove private customer details, passwords and account information.
Submitting is voluntary and free. It is not needed to complete this class. Please tell us explicitly whether we may publish your work and description under your chosen display name. Sending work does not publish it automatically; we’ll follow up if changes or clarification are needed.
Copy this submission email
To: mark.markhope@gmail.com
Subject: Student Lounge submission — Codex 102
Hello Hope MetaVersity,
Preferred public display name:
Project title:
Class: Codex 102
What I built and what I learned:
What I tested and any remaining limits:
Public demo link or attached screenshots/files:
Publication permission (choose one):
[ ] You may publish the supplied work, description and screenshots in the Student Lounge under my preferred display name. I have permission to share them and have removed private information.
[ ] Please contact me before publishing anything.
Thank you!
The email link opens your configured mail app. Review your message, attach the work you want to share and send it yourself. You can also copy the address into your email service.
Put it to work
Your reviewed practice tool
Keep index.html, README.md, TEST-NOTES.md, NEXT-STEPS.md and a fictional JSON export. Copy the project folder to a separate backup. Download these learning notes alongside it.
Your notebook saves on this browser when available. Download a copy to keep it.
Next small step: review one remaining limitation and plan one small improvement. Use fictional data while practicing.
