Worker Lockfile

iii.lock

What It Records

• Lockfile version.
• Registry-managed worker entries.
• Binary source artifacts keyed by platform target triple.
• OCI/image source pins such as resolved image digests where available.
• Dependency graph pins returned by the worker registry.

config.yaml

iii.lock

Commands

iii worker add <worker[@version]>

iii.lock

iii worker update [worker]

iii.lock

iii worker sync

iii.lock

iii worker sync --frozen

iii worker verify

iii worker verify --strict

iii.worker.yaml

Reproducible Install Workflow

iii worker add image-resize@1.0.0
git add config.yaml iii.lock
iii worker verify

iii worker sync
iii worker verify

iii worker sync --frozen
iii worker verify --strict

Commit Rules

• Commit

  iii.lock

  with

  config.yaml

  .
• Update pins intentionally with

  iii worker update

  , not by hand-editing resolved artifact entries.
• Do not expect built-ins, direct OCI refs, local-path workers, or sandbox rootfs/base images to be replayed by the v1 lockfile contract.
• Extra lockfile entries are allowed by normal verification; strict verification adds freshness checks.

Pattern Boundaries

• For command-by-command worker operations, prefer

  iii-worker-lifecycle

  .
• For config YAML structure, prefer

  iii-engine-config

  .

When to Use

• Use this skill when the task mentions

  iii.lock

  , reproducible worker installs, frozen sync, worker verification, CI worker setup, or cross-machine worker reproducibility.

Boundaries

• Do not invent lockfile entries manually.
• Do not treat

  sync

  as an update command; it replays existing pins.
• Do not generate removed service APIs or adapter-extension APIs.