Read by task.
Pick what you want to understand.
Each path begins with a concise guide and leads to its implementation or verification source.
Clone, check, test, and choose a first exploration.
02Architecture rationale ↗v0, v1, and eventual ASIC direction.
03Software/hardware contract ↗Commands, state, memory, completion, reset, and errors.
04Numerical semantics ↗Formats, rounding, saturation, accumulation, and activations.
05Simulator guide ↗Functional v0 command and memory behavior.
06Conformance corpus ↗Fixture format, derivations, runner, and integrity.
07YOLOv8n workload ↗Manifest, graph audit, preprocessing, partition, and baselines.
08Decision records ↗Why public interface and corpus choices were made.
09Development plan ↗Milestone dependencies, gates, checklists, and evidence.
10Two-block compiler ↗Connected Conv-SiLU validation, channel chunks, intermediate tensors, and deterministic packages.
11Simulator runtime ↗Strict loading, input binding, submission, completion, and reset.
12Experimental package ↗Sections, relocations, and experimental package boundaries.
Know where evidence lives.
The codebase separates reference truth, executable behavior, independent fixtures, workload evidence, and future implementation areas.