Design context and scope
The original site had a project showcase page with example project listings. This lab version turns that concept into an engineering notebook format so you can document constraints, QoR changes, and observations without mirroring the production presentation.
Coverage map for this lab note
- How to convert a one-off project demo into a repeatable implementation case-note template.
- Defining project context: block type, goals, constraints, tool version, and assumptions.
- Capturing baseline metrics before experimentation (timing, area, power, congestion indicators).
- Recording each change step and the intended hypothesis, not just the command sequence.
- Documenting outcomes, regressions, and correlation issues across synthesis and PD stages.
- Retrospective sections for what to keep, what to roll back, and what requires deeper validation.
What you should be able to explain
- Create a project-note format that is useful for future debugging and interviews.
- Track implementation changes with enough context to compare runs fairly.
- Separate observations from assumptions so your conclusions remain testable.
- Maintain a .site test-space portfolio without duplicating the .top site structure.
Review checklist before moving ahead
- Start each case note with design scope, revision ID, and tool environment.
- Capture baseline QoR before changing constraints or optimization settings.
- Log each experiment with expected benefit and measured outcome.
- Summarize regressions and suspected root causes, not just final results.
- End with next actions and validation gaps.
Common watchouts
- Project notes become useless if they only store screenshots and no assumptions or metric context.
- Comparing runs across different corners or libraries without noting it creates false conclusions.
- Do not publish proprietary details on a public test domain; keep examples sanitized.
Self-check prompts
- What minimum information makes an implementation experiment reproducible?
- How do you separate a real QoR improvement from run-to-run noise?
- What should be redacted before posting a case note publicly?