This is a PATTERN showing how to structure a code/tool source note — the bracketed fields are placeholders to fill from a real repo, not a completed example.
What it is: open-source package that [pulls street networks / computes X] — class-6 source: useful machinery, zero authority. Useful for: prototyping study-area networks, batch spacing measurements, comp-site scans. Key content/claim: outputs depend on OSM completeness → treat results as screening, never as the cited basis of an engineering conclusion. Trust protocol applied: license checked · issues page scanned for known bugs · output verified against a hand-measured sample (record dataset + date above) · pinned version in requirements. How it enters real work: screening figure labeled “based on OpenStreetMap data (date); field-verify before design use” — the label IS the ethics. Cross-links: Workflow - Research and Source Vetting · MOC - Automation Practice question: a Reddit thread (class 5) says agency X waives TIA under 50 trips — what must happen before that sentence can influence a memo? (Find the actual guideline §, cite THAT; the thread was just a treasure map.) QA/QC reminder: class 3–7 sources never get cited in deliverables — only the class 1–2 source they led you to.