planned project

Formal Bits Notebook

A structured public notebook for assertions, SVA patterns, proof attempts, and verification learning trails.

SystemVerilogSVAWriting

Links

Demo/source links can be added later from Sanity.

Problem

Formal verification notes can become scattered quickly unless examples, assertions, and failure stories are organized by intent.

Outcome

A durable reference for formal verification learning and future technical writing.

System sketch

How this project moves.

planned
01Problem
02Inputs
03Prototype
04Proof
05Writeup
06Next

Approach

  • Group notes by property type and design behavior.
  • Capture counterexamples as learning artifacts.
  • Keep a compact glossary for terms that repeat across posts.

Lessons

  • Proof attempts are easier to revisit when assumptions are explicit.
  • Small examples should be connected to real debugging stories.

Proof trail

Assumption to lesson, not just screenshot to stack.

Assumption

Assertions are easier to learn when grouped by design intent.

Experiment

Organize notes around safety, liveness, and interface behavior.

Result

The notebook becomes easier to search and expand.

Lesson

Verification writing should preserve the reason behind a property.