Files
Quadrapassel/docs/DECISIONS.md
T
Brian Holman d412e35c4e Implement CoCo 3 Quadrapassel and deliver build 01
Add gameplay, keyboard/joystick controls, disk-backed high scores and settings,
standard CMOC effects, and the approved C graphics renderer. Include the clearer
attributed font, title/credits updates, source-verified Modern and Classic (40.2)
scoring, meaningful regression fixtures, and recorded guest validation.

Deliver QUADPSL01.DSK with fresh high scores. Retain source, licenses and selected
guest evidence; exclude personal disks, private connections and build scratch.

Host rules/input/persistence/video checks and memory guards pass. Official
512 KB playtests pass the recorded checks; actual 128 KB/physical joystick
qualification and the normal-window buzzing retest remain pending.
2026-11-11 03:14:14 -07:00

42 lines
2.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Reviewed decisions
## November 10, 2026 — C graphics exception
Brian's explicit decision, relayed by the coordinating chat **Deploy VCC Plus
Gitea** (`01a1c3a8-8bde-77f0-b8af-d0d29b874c7c`): **“Approve the C graphics
exception.”** The approved wording was:
> C code for screen-memory mapping and drawing changed regions, using CMOC/BGraph
> where practical, with no assembly or emulator changes and explicit 128 KB validation.
Allowed scope: the narrowly proposed CoCo 3 C framebuffer/MMU renderer in
`src/platform/coco3_video.c/.h` and associated memory/build documentation. Prefer
standard CMOC/BGraph primitives where practical. Bound dirty-region/text drawing,
preserve code, stack, BASIC graphics/disk workspace and interrupt behavior during
temporary mapping, and restore the state needed by standard APIs and disk calls.
Retain the public-API fallback and compare measured drawing and visible input.
This approval does **not** authorize hand-written assembly, custom sound/input/
interrupt drivers, emulator source access or changes, custom app builds, or a
replacement MCP integration. Official VCC Plus 3.5.5 (48) and reference boundaries
remain required. Further exceptions need review. Actual 128 KB testing remains
separate from the 512 KB MCP worker; Brian offered to perform that manual check.
### Evidence prompting review
Official build 48, Release `-O2`, isolated MC6809, 512 KB, NTSC-rate worker:
- One 8×8 block erase/redraw through `hset`: worst 4 BASIC ticks at ordinary speed.
- T-piece one-cell shift: only four changed 8×8 cells (256 plotted pixels), worst
12 ticks at ordinary approximately 0.895 MHz speed.
- Same 60-shift test using standard `setHighSpeed(TRUE)` at approximately
1.79 MHz: p95 and worst both 6 ticks, approximately 100 ms.
Build `B928140E-6147-4DB5-BEF0-729678C498B0`, MCP revision 2, artifact
`12931271-4662-4B9F-B138-03913F23E58B`, disk SHA-256
`87f9d22c0afe7313f08031b9b4d88c2e0b6eeb4e81050739d108d82fe1fe76ad`.
These measure foreground drawing cost, not full-game input-to-display latency.
Smaller blocks, sparse outlines and staged `hset` drawing remain possible API-only
alternatives, with board-area, appearance or latency compromises. No direct screen
code was implemented before this approval was received and recorded.