Review specification consistency
Read the datasheet, application note and specification as the design inputs. Compare their facts where the generated documents and RTL consumers use them.
- Match pin names, directions, widths and voltage domains.
- Compare register addresses, field widths, reset values and access behavior.
- Compare clock rates, timing units, protocol encoding and latency.
- Resolve contradictory limits, absent requirements and undocumented defaults.
- Check that examples exercise the stated normal, boundary and error cases.
Keep original source and PDK limits. Report the conflicting facts with their
source locations rather than resolving them through a quality score. When RTL
exists, run the normal native lint, simulation, formal or equivalence task for
the concrete requirement. An absent execution result is NOT_MEASURED.
Read the selected rows in <project>/reports/flow_engine.json and open their
native reports. flow/steps.json names each current tool and
flow/native_limits.json retains its original limits. Review tool_ran,
native_steps, native_metrics, and each metric's value, operator and limit.
A missing native measurement is NOT_MEASURED. AI reviews the engineering
meaning of every result and fixes problems in the design, tool or plugin.
python3 programs/flow_engine.py report --project <project>