# Local reference

These files were copied from Product Resolver workbench checkpoint 0.5.3 so this guide can be read without the workbench. They record proposals and established design, not a new decision made for this guide.

Clickable links in this folder point at a file in this package or at an equivalent section of the guide. Where a workbench screen was not copied, the sentence names that screen and says it is unavailable. Those names are not hyperlinks.

Copied records still mention workbench screens such as `atlas.html`, `cost.html`, `data.html`, `contracts.html`, `collectors.html`, `decisions.html`, and `implementation-plan.html`. Those screens are not in this package. Follow the guide chapters for the explanation.

Historical verification logs under `verification/` were not copied. `verification.md` identifies each omitted log as inherited workbench evidence. Those results are not checks executed on this guide.

`architecture/technology-ports.md` is the reviewed port note, copied unchanged. In that file, “adapter” means an infrastructure adapter behind a port: storage, a queue, a database, or the host process. A parser adapter is a different use of the word. The guide glossary defines both.

`inventory/` is a distillate of the workbench’s interface, module, actor, permission, and atomic-write fixtures. The guide renders it. `known-fixture-ids.json` is the allowlist the checker uses. Every product, merchant, source, and capture identifier in that list is fictional.

`diagrams-mmd/` keeps the workbench Mermaid sources. The figures you see in the HTML are generated from `../diagrams/figures.json`, not from those Mermaid files.