Lockfile & Integrity 1.4.0

velin-blocks.lock.json records install truth for updates and diagnostics without affecting application boot.

Recorded data

Field	Purpose
name + version	Installed identity
source	Official ID / registry or local provenance
integrity	Per-file content hashes
installedAt	Install timestamp
conflictStatus	clean, dirty, missing-files, or peer-mismatch style state

Integrity map

Phase 5 writes file integrity information on install. Community manifest integrity, when present, uses sha256 and 64-character hexadecimal file hashes.

Not a runtime lock

The application does not need this file to boot, and the file is not a license or telemetry mechanism.

Dirty source

A changed hash indicates user-owned edits. Reinstall must fail by default instead of silently overwriting those edits.