mesh-host

Files

T

jschoubben 4af9483219 declaration: an image may be named by the digest of its own configuration

A manifest digest is assigned by a registry on push, so insisting on one meant a
registry had to exist before the thing that lets a mesh have a registry could
start — a dependency the pinning rule created by accident, not a pin. The mesh's
own control plane is built from source and lives in no public registry.

A bare sha256:... names an image the machine already holds, by the digest of its
own configuration: immutable and unforgeable in exactly the way the rule asks
for. Absent, it says so plainly rather than failing at a pull nothing serves.

Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

2026-09-10 22:40:02 +02:00

access_test.go

declaration: an access is mounted, and the host owns nothing about it

2026-09-05 22:19:33 +02:00

apply_test.go

A container reflects its config: restart-on for containers (04-ISSUES/009)

2026-09-04 23:39:47 +02:00

apply.go

declaration: an image may be named by the digest of its own configuration

2026-09-10 22:40:02 +02:00

archive.go

A user, bytes, and an archive — because most of what people install is