Submission deliverables¶
The deliverables below describe implemented behavior and reproducible verification. Competition submission is a separate action after the candidate is qualified.
Deliverable |
Documentation and executable material |
|---|---|
Architecture |
Engines, memory, pins, timing and host interface; reset and state loss |
ISA |
|
Assembler/toolchain |
|
Example programs |
UART, SPI modes 0–3, I2C 100/400 kHz matrix, generated assembly/images and checked traces |
Verification write-up |
Independent models, simulation, formal, mutations and limits; proof assumptions |
Physical implementation |
Stock TT procedure and repair provenance; release evidence index |
TT Markdown datasheet |
Project datasheet, retained at |
HTML is built with pinned Sphinx, MyST and Alabaster dependencies and retained as an Actions artifact and published on GitHub Pages, with the interactive layout explorer. Source, package and example archives and checksums identify the software candidate separately from the selected physical source. The release evidence index records the layout, source correspondence and publication checklist.