Use the product
Error Decoder and assistant contract
The assistant contract defines how decoder output should stay evidence-scoped and actionable.
Use when
- You are pasting Vivado, Quartus, Gowin EDA, Yosys, Verilator or GHDL output.
- You need the report fields expected from the decoder workflow.
- You want to check what is a draft and what must be independently verified.
Outcome
- You can judge a report by its evidence, confidence and next actions.
- Generated HDL, constraints and testbench notes stay clearly marked as drafts.
- Unsupported signoff claims are visible before the workflow starts.
Report fields
- confidence
- evidence
- sources
- tool_results
- warnings
- limitations
- repro_steps
- next_actions
Expected intake
- Paste the smallest log section that includes the actual error and nearby context.
- Include tool name, HDL language, stage and file references when they are safe to share.
- Keep license files, private keys, customer data and confidential RTL out of public alpha uploads.
Boundary
- LLM output is not the source of truth.
- Generated suggestions require simulation, synthesis and engineering review.
- fpga.chat does not claim timing, CDC or RDC signoff.