SpecLink

Documentation
Source

The traceability chain and the vendor-neutral boundary between simulation and Django.

From requirement to evidence

The closure chain

Requirement ↔ Test ↔ Check → TestRun / CheckEvidence → RequirementEvidence → ClosureSnapshot

Requirements are organized under a project and category. Explicit mapping records say which tests and checks prove, stimulate, observe, cover, or guard each requirement and whether that relationship is required for closure.

Simulation reports JSON, not database calls

SpecLink generates a small SystemVerilog package. Verification code reports pass, fail, and hit events to that package. At end of test it prints a marked JSON summary; a standalone or Django parser converts the transcript to evidence JSON for upload.

Simulator-independent by design

  • The generated API is plain SystemVerilog and UVM-independent at the evidence boundary.
  • The parser searches text markers and validates required JSON fields rather than depending on a simulator database.
  • Regression metadata can record branch, commit, tool, start/end time, and arbitrary JSON metadata.