01

Identify the exact source

Record the authoritative repository, revision, and artifact. A familiar project name alone cannot identify the code you are about to run.

02

Review what can execute

Inspect build and installation scripts and understand their requested effects before approval. Treat a changed revision as a fresh decision.

03

Pin the content

Keep the exact revision and content hash in a reproducible record. When signatures are used, verify the expected signer as well as the bytes.

04

Retain an inspectable result

Keep the installation outcome, integrity check, and bill of materials alongside the recovery instructions.

In practice

A concrete starting point.

An upstream update that changes an installation script should require a fresh content decision even when the package name and repository stay the same.

Make it usable

Your working checklist.

Mark what you have considered. This checklist stays on this page and is cleared when you reload.

Explore the related work.

stackpkg ↗GitHub Access Foundry ↗

General engineering guidance, not a certification, service agreement, or product-specific acceptance report.

Back to all field notes ↗