Engineering note
Why board support at AccelFury is evidence-gated
A short note on fail-closed constraints, build evidence and why board wrappers do not count as verified hardware support by themselves.
Definitions
Why wrappers are not enough
The public portability matrix makes a strong distinction between “board wrappers present”, “build evidenced” and “hardware evidenced”.
- A wrapper proves only that a board-local top module exists.
- A build report proves only that synthesis, place-and-route and bitstream packing succeeded for a stated configuration.
- Hardware evidence requires programming plus observed board behavior or measured pins.
Practice
Fail-closed constraints
The public Tang Nano 20K and Tang Mega 138K notes remain fail-closed until source-attributed pins, I/O voltages and measured behavior are added. This keeps the public site honest for engineers and AI agents alike.