The manifest is the single document that says what is being taped out and what was checked. Every argument at a tapeout review is really an argument about the manifest: a version nobody recorded, a check nobody ran, a result attached to the wrong revision. This topic builds the NanoSoC manifest from scratch: what rows it holds, how the baseline is frozen so it cannot drift, how a second engineer reproduces it, and the script that checks it every night. Its one job is the list and its integrity; what the waivers inside it mean is the next topic.
Lesson | After it you can... |
|---|---|
Name every row of a chip manifest and who owns it. | |
Freeze a baseline, derived databases included, so no input can drift under a result. | |
Run the checker that proves a manifest complete and current, and make it fail on purpose. |
Suggested order: top to bottom. Contents first, because the freeze only makes sense once you know what is frozen; then the checker, which enforces both. The waiver topic next door explains the rows this topic treats as entries.
The manifest: a result without a recorded revision is not evidence. The freeze rule exists so this cannot happen silently.