jackin-image

Image generation and binary-artifact management for jackin❯. Builds the derived role image, acquires/caches the agent and capsule binaries, and decides the image-build vs reuse path.

What this crate owns

Derived-image Dockerfile generation (derived_image, image_recipe) and the build pipeline (image_build).
Agent + capsule binary acquisition and caching (agent_binary, capsule_binary, binary_artifact).
The image decision — build vs reuse vs published (image_decision, version_check) and image naming (naming).

Architecture tier and allowed dependencies

L1 application (image subsystem). Allowed workspace dependencies: jackin-core, jackin-manifest, jackin-docker, jackin-diagnostics, jackin-build-meta. No presentation or runtime dependencies — image materialization is a domain/app concern consumed by jackin-runtime.

Structure

Module	Owns	Tests
`lib.rs`	crate root, re-exports	—
`derived_image.rs` · `derived_image/`	derived-image Dockerfile generation	`tests.rs`
`image_recipe.rs` · `image_recipe/`	Dockerfile recipe	`tests.rs`
`image_build.rs` · `image_build/`	build pipeline	`tests.rs`
`agent_binary.rs` · `agent_binary/`	agent binary acquisition + cache	`tests.rs`
`capsule_binary.rs` · `capsule_binary/`	capsule binary acquisition + cache	`tests.rs`
`binary_artifact.rs` · `binary_artifact/`	shared artifact helpers	`tests.rs`
`image_decision.rs` · `image_decision/`	build-vs-reuse decision	`tests.rs`
`version_check.rs` · `version_check/`	version check	`tests.rs`
`naming.rs`	image naming	—

Public API

The image-build decision and materialization entry points consumed by jackin-runtime. The construct Dockerfile (operator-built base) lives under docker/construct/; this crate generates derived images on top of it.

How to verify

cargo nextest run -p jackin-image
cargo clippy -p jackin-image --all-targets -- -D warnings