Where we stand.
We have curriculum to learn from, machines to run it on, and tools to build it. The next step is to make those parts dependable together.
Code198x needs learner and content acceptance. Emu198x needs complete usability evidence for named configurations. Asm198x needs compatibility evidence connected to real authoring work.
The checkpoints below can change as we learn more. They give us something concrete to assess without assigning an overall completion score.
Snapshot checked . These are editorial assessments grounded in the linked records, with evidence available at that date. This page does not run fresh tests when you open it.
Code Like It's 198x
Help people understand programming by making games on machines they can understand.
Selected first programs build, change and reopen.
Where we are. The four core routes are authored. Selected first-program workflows now have evidence for editing, rebuilding and reopening on macOS; the rest of the curriculum still needs content and learner acceptance.
What we can show. Spectrum editing and recovery, C64 red/green PRG execution, Amiga red/green bootable disks and the NES edited-cartridge handoff have retained observations. The C64 starter and Amiga instructions were corrected during these checks.
What needs attention. Uncoached understanding remains unobserved. Screen-reader use, touch, wider lesson review and deferred Windows/Linux manual walkthroughs remain open. One successful program does not establish a complete course.
Assessment reviewed · Source records unchanged at the snapshot check. This checks the records, not the software again.
Sources behind this assessment
- Purpose and curriculum direction — unchanged at snapshot
- Current curriculum work boundaries — unchanged at snapshot
- Release and learner acceptance — unchanged at snapshot
- Spectrum BASIC catalogue — unchanged at snapshot
- C64 assembly catalogue — unchanged at snapshot
- Amiga assembly catalogue — unchanged at snapshot
- NES assembly catalogue — unchanged at snapshot
- Reviewed first-session workflows, corrections and remaining gaps — unchanged at snapshot
- Retained NES browser/download/native handoff observations — unchanged at snapshot
Emu198x
Run historical machines accurately enough to inspect, explain and create with them.
Named workflows run; broader usability remains open.
Where we are. Selected browser and native paths execute the first programs. Results belong to their named model, release and host; native candidate acceptance and released-binary execution remain separate.
What we can show. Released Emu198x 0.38.1 boots the selected A500 disks and runs the downloaded NTSC NES cartridge. The Spectrum macOS keyboard, listening and recovery checklists received user-reported acceptance; C64 browser PRG execution also passed.
What needs attention. Other models and complete native input, sound and file workflows still need their own evidence. Windows/Linux manual checks are deferred. Hosted Spectrum evidence retention remains blocked; local success does not remove that blocker.
Assessment reviewed · Source records unchanged at the snapshot check. This checks the records, not the software again.
Sources behind this assessment
- Shipping systems and evidence ownership — unchanged at snapshot
- Native UI scope and host gaps — unchanged at snapshot
- Owning system work queues — unchanged at snapshot
- Native installation, execution and source-debug observations — unchanged at snapshot
- Reviewed first-session workflows, corrections and remaining gaps — unchanged at snapshot
- Retained NES browser/download/native handoff observations — unchanged at snapshot
Asm198x
Give retro programs a maintainable toolchain that respects existing source dialects.
First-program builds agree with reference assemblers.
Where we are. Released Asm198x 0.0.71 builds the selected C64, Amiga and NES first programs with independent reference-byte agreement. This is useful authoring evidence for those sources, not a blanket dialect-compatibility promise.
What we can show. ACME, native vasm and ca65/ld65 agree with the selected first-program outputs. The browser’s downloaded NES source rebuilds into identical cartridge bytes, and only the intended colour byte changes between its red and blue variants.
What needs attention. The joined examples cover a small part of the CPU and dialect surface. Legacy reference tests can skip when external tools or sources are absent; a green general suite alone does not establish those comparisons ran.
Assessment reviewed · Source records unchanged at the snapshot check. This checks the records, not the software again.
Sources behind this assessment
- Toolchain front doors and validation scope — unchanged at snapshot
- Reference-test prerequisites and skip behaviour — unchanged at snapshot
- Native installation, execution and source-debug observations — unchanged at snapshot
- Reviewed first-session workflows, corrections and remaining gaps — unchanged at snapshot
- Retained NES browser/download/native handoff observations — unchanged at snapshot
What works together
Four selected programming patterns connect the curriculum, assembler and emulator; the Amiga example also uses Build198x. These are demonstrated paths through the family, with named versions and configurations.
| Example | Connected projects | Evidence state |
|---|---|---|
| Bitmap addressing | Code198x → Asm198x → Emu198x | Execution verified |
| Hardware sprites | Code198x → Asm198x → Emu198x | Execution verified |
| Square wave | Code198x → Asm198x → Emu198x | Execution verified |
| Playing a sample | Code198x → Asm198x → Build198x → Emu198x | Execution verified |
This establishes a useful connection, not universal compatibility. AABB also has a host-Python check. Inspect all five results, versions and limits.
Where to put attention
My recommendation is to deepen one complete learner-to-running-program journey before adding more breadth to this view. It gives all three projects a shared, observable checkpoint.
Keep the tests underneath that journey: source compatibility, program behaviour and usable interaction each need their own evidence. Learner trials, listening and original-hardware checks remain distinct from automated checks.
When the goalposts move, revise the working checkpoint and review its sources. Existing evidence keeps its original meaning; a changed goal does not rewrite a historical result.
The rest of the family
These projects supply tools, shared contracts and media capabilities around the three priorities. The activity labels describe declared project activity, not readiness.
Seven other projects and their roles
| Project | Role | Activity |
|---|---|---|
| Build198x | Convert assets and master native media. | Active |
| Isa198x | Describe instruction encodings and shared disassembly. | Active |
| Format198x | Read and write native disk and media formats. | Active |
| Debug198x | Exchange debug information between development tools. | Active |
| Cat198x | Catalogue and verify binary assets. | Active |
| Play198x | Explore retro images and tracker music. | Active |
| Forge198x | A planned development workbench for the family tools. | Deferred |
Download the reviewed snapshot as JSON. Sources and measurements retain their original dates and scope.