Editorial policy

One question, answered first

Each page answers one engineering question in its opening paragraph, then shows a complete original example or table and walks through what it does and does not establish. Every page ends with what it does not cover and its sources.

Documentation, run, inference

Every page keeps three kinds of statement apart: what a standard, tool or project documents, what a recorded run produced with named tool versions, and what we infer. A documented feature is not tested compatibility. A passing simulation is evidence about that configuration, not a claim about silicon, timing, power intent or every simulator.

Examples are original and executed

HDL, scripts and testbenches are written new for this site and run as printed in open-source tools, with commands, versions and literal output recorded. Anything that would need a commercial tool, a UPF-aware flow or hardware is described as not run.

Tools are described, not ranked

Differences between simulators are reported against their configuration and documentation. We do not call a tool wrong, non-compliant or better, and we make no conformance claims.

Original work only

Explanations, examples, fixtures and compilations are new. We do not reuse prose, code, figures or data from earlier publications at this domain, and company and product names appear only as factual references.

AI assistance and responsibility

Pages are drafted with AI assistance. The publisher is responsible for every page: claims are checked against their sources and runs before publication, and errors are corrected in public as described in corrections.

Review

Independent technical review by named verification and EDA engineers is being added. A reviewed page shows the reviewer’s name, credential and review date. Reviewers must be independent of any sponsor on the page.