0x0 Package System Reference

This public reference describes the current local package system.

Current Scope

0x0 has a local manifest and lockfile system. It is not a network registry,

dependency solver, or remote package fetcher.

Current files:

• 0x0.pkg: checked manifest;
• 0x0.lock: generated lockfile;
• tools/pkg-lock.0x0: validator and lock generator;
• tools/pkg-lock.sh: shell wrapper.

Manifest Directives

Supported directives:

package <name>
version <version>
source <path>
dep <name> <path>

Rules:

• exactly one package;
• exactly one version;
• at least one source;
• unique source paths;
• unique dependency names;
• relative .0x0 paths;
• no parent traversal;
• dependency paths must also be listed as sources.

Lockfile

The lockfile records deterministic manifest resolution. Package imports read

0x0.lock, not the manifest text directly.

Package Imports

(↥ "pkg:core-map")

If core-map is present in 0x0.lock, the compiler loads the mapped local

source path. If not, compilation fails with a package dependency diagnostic.

Standalone Libraries

The public standalone library contract is completed in Milestone 4. Until then,

public libraries should keep the conventional structure:

libs/<name>/src/lib.0x0
libs/<name>/tests/smoke.0x0

Safe Commands

Use:

make package-check

Only run broad library compilation or standalone checks when the host can safely

absorb the compiler workload.