Expand description
Typed Lockfile — resolved, content-addressed dependency tree.
Every package manager ships a lockfile (Cargo.lock,
package-lock.json, Gemfile.lock, poetry.lock, go.sum,
mix.lock, …). Each pins exact resolved versions + integrity
hashes so subsequent installs are deterministic.
Adapters parse their native lockfile into this canonical shape;
the resolver in gen-engine validates the manifest’s typed
constraints against the lockfile’s resolved versions.
Structs§
- Content
Hash - BLAKE3-32 content hash. Used for lockfile integrity + cache keys.
- Lockfile
- Typed lockfile — content-addressed, deterministic.
- Resolved
Package - One resolved package in the lockfile. Pins exact source + integrity.