Phase 2 RTL Verification
Register value convention
Read flow/rtl_conventions.json#register_initial_value from this plugin tree
before writing, repairing or reviewing RTL. A value stated in the original input
wins. If the input is silent, use a recognized circuit-class convention from
the table when one applies; otherwise use zero, including internal state. Use a
reset assignment when the register has a reset, otherwise an initial assignment. A reset is the startup mechanism unless the input explicitly requires a
separate initial value. Mark defaults and conventions visibly in RTL comments and list
register, value, mechanism and convention/source in the report. On chip and IP routes, initial-only
storage is a reported, nonblocking finding. This table defines the input/convention/zero
precedence. Never derive values from a testbench, scorer, reference
answer or score. The scorer must not modify candidates.
Doctrine (v0.1.50): 把修法寫進工具,而非寫進 prompt. Programs first; AI is the backstop on residual narrative.
Read the native verification results
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>
Review the completed verification window
Review the exact RTL and native outputs from the selected public window. Keep design-input-only authoring and independent review. When semantic review rejects RTL, demonstrate the issue with a source-derived executable test before repair. Rerun the affected native tools after the fix.
Verification checklist
- Compare native elaborated ports, widths, directions and submodules with the actual L9 integration contract.
- Check required FSM states and transitions through native simulation or formal coverage, including source-declared normal and error behavior.
- Read native lint and
rtl_hygiene_lint.pydiagnostics for undriven signals, unread state, incomplete cases, width/sign changes and unintended latches. - For a protocol that forbids device-generated break, verify the relevant transmit states and durations against the original protocol limit.
- If self-receive masking is required, test its behavior while the device drives the bus. Do not infer it from a signal name.
- Compare OTP addresses and values with the actual loaded memory image.
- Exercise every source-declared scenario and its boundary/default behavior. Read the native transcript and coverage for each required case. Keep any missing execution explicitly unmeasured.
Spot-check actions
- Select source-declared opcodes and boundary/default cases from L3.opcodes, exercise them through the applicable native interface, and compare with the response defined by the current input.
- Compare RTL with a reference only when that reference is explicitly supplied for this task or independently derived from its source. Do not read a previous project's implementation to answer a clean-room task.
When to escalate
- Find any Wave-34 violation → invoke the
rtl-repairskill for the bounded RTL repair/retry loop (not a physical/metal ECO) - Find L9 contract mismatch → re-run phase2 after patching aid_class_rtl_gen template
- Find dead RTL → call out to user, may be intentional or may reveal regression
Output
Append findings to <project>/reports/phase2_verify.md. If all checks pass, write single-line PASS summary.