Nockchain Nockup Source Trace

nockup-readme-contract

Documents Nockup's experimental status, local cache/toolchain workflow, manifest fields, template names, dependency commands, and untrusted-code security posture.

The README states Nockup is experimental, bootstraps ~/.nockup, scaffolds from nockapp.toml, installs Hoon dependencies, and treats template/dependency execution as untrusted code execution.

nockup-manifest-schema

Defines package metadata, template/template_commit fields, dependency specs, and lockfile records.

The manifest schema supports simple, versioned, and full git dependency specs plus lock entries with exact commit hashes.

nockup-template-init

Scaffolds a new project from a cached template and applies manifest values through Handlebars.

The init command loads <project>.toml, resolves ~/.nockup/templates/<template>, rejects existing target directories, builds template context, copies template files, and processes libraries.

nockup-template-cache

Downloads or refreshes bundled templates and manifests from the canonical Nockchain repository.

Nockup clones nockchain/nockchain master, moves crates/nockup/templates and crates/nockup/manifests into ~/.nockup, and writes commit.toml with the fetched commit id.

nockup-toolchain-channel

Fetches channel manifests for the local architecture and writes cache config for stable/nightly tooling.

The common command code derives architecture identifiers, writes config.toml defaults, downloads release manifests for the active channel, and keeps channel binaries under ~/.nockup.

nockup-dependency-resolver

Resolves dependencies recursively, fetches sources, validates requested .hoon files, loads transitive hoon.toml dependencies, and caches packages by exact commit.

The resolver records exact commits, converts specs into GitSpec values, checks cache, validates source files, loads transitive deps, and computes an install graph.

nockup-registry-install-path

Maps registry packages and Typhoon registry entries into git source paths, install paths, file selections, and dependencies.

Registry entries carry git_url, path, install_path, and file; online registry lookup falls back to hardcoded entries and to_git_spec preserves install_path for package install.

nockup-resolved-graph-order

Defines resolved package metadata and topological install order with cycle detection.

ResolvedPackage stores exact commit, source_url, source_path, install_path, source_files, and dependencies; compute_install_order visits deps first and rejects cycles.

nockup-package-install-links

Installs resolved packages into hoon/packages, creates symlinks into hoon/lib, hoon/sur, or registry install_path directories, and writes nockapp.lock.

Package install creates hoon/packages/lib/sur directories, uses install_path plus source_files for registry packages, sanitizes names/versions, and records exact git source commits in the lockfile.

nockup-cache-index

Tracks package cache identity under ~/.nockup/cache/packages with source URL, version spec, exact commit, timestamp, and cache index.

cache_package copies source into the package cache, records cached_at, and writes cache-index.json; the cache can list, prune, and find packages by version spec.

nockup-git-fetcher

Fetches git dependencies by commit, tag, branch, or default branch and caches them by URL hash plus short commit.

GitFetcher resolves refs with git ls-remote, prefers commit > tag > branch > default, clones repos, checks out exact commits, and supports sparse checkout for subdirectories.