A module can come from a registry reference, local path, Git URL, npm package, or tarball. Always inspect the plan before allowing an unfamiliar artifact to write files.
damat module plan <registry-ref|path|git-url>
damat module add <registry-ref|path|git-url>
The plan shows source identity, trust status, capability destinations, package
changes, owned files, and integration notices. Installation is transactional
for managed files and records checksums and provenance in damat.lock.json.
Installation does not finish application integration. Continue with: