REFERENCE · 07

Every exit code, one table.

This page carries the complete named-exit table: every loader refusal from 64 through 79, plus the three codes that live outside the loader block. Every loader failure prints a one-line reason before exiting, and that line is the first thing to read.

The loader block, 64 through 79.

The codes exist so scripts can branch.

Exit	Refusal	What it means
64	usage	the command line itself was wrong — a bad flag or a missing argument — and the usage line prints
65	manifest	the trailer or a manifest is missing, corrupt, or names no usable entrypoint
66	launcher ABI	the package speaks a handoff wire format this runtime predates
67	runtime reference	the runtime reference in the trailer cannot be parsed or honored
68	overlay	an overlay/decrypt binding failed — an unbound retained store, missing or non-opening key material, an unwritable store, an orphan binding, or a malformed TEBAKO_OVERLAYS / TEBAKO_DECRYPT
69	unavailable	an artifact could not be resolved — an offline miss or a download failure; TEBAKO_OFFLINE, the network, and the release page are the first places to look
70	sha256	a checksum verification failed; nothing was installed
71	signature	a signature is invalid — or the artifact is unsigned under TEBAKO_REQUIRE_SIGNED=1
72	trust	the signing key is not in the trusted set
73	jail	the jail policy is malformed; the run failed closed, nothing mounted
74	I/O	a filesystem, lock, or install operation failed
75	contract	runtime and loader generations do not meet — the message names both and the remedy
76	install	installation was refused — the publisher froze the package (no-install), or the verb belongs to the CLI
77	era	the artifact comes from a different tebako generation, in either direction
78	layout	the env image does not match the layout the interpreter was compiled for — or a mount-root override the image does not grant
79	check	a payload check FAILed — the tebako check aggregate; the verdict line names the check and the failed expectation

Exit

Refusal

What it means

usage

the command line itself was wrong — a bad flag or a missing argument — and the usage line prints

manifest

the trailer or a manifest is missing, corrupt, or names no usable entrypoint

launcher ABI

the package speaks a handoff wire format this runtime predates

runtime reference

the runtime reference in the trailer cannot be parsed or honored

overlay

an overlay/decrypt binding failed — an unbound retained store, missing or non-opening key material, an unwritable store, an orphan binding, or a malformed TEBAKO_OVERLAYS / TEBAKO_DECRYPT

unavailable

an artifact could not be resolved — an offline miss or a download failure; TEBAKO_OFFLINE, the network, and the release page are the first places to look

sha256

a checksum verification failed; nothing was installed

signature

a signature is invalid — or the artifact is unsigned under TEBAKO_REQUIRE_SIGNED=1

trust

the signing key is not in the trusted set

jail

the jail policy is malformed; the run failed closed, nothing mounted

I/O

a filesystem, lock, or install operation failed

contract

runtime and loader generations do not meet — the message names both and the remedy

install

installation was refused — the publisher froze the package (no-install), or the verb belongs to the CLI

era

the artifact comes from a different tebako generation, in either direction

layout

the env image does not match the layout the interpreter was compiled for — or a mount-root override the image does not grant

check

a payload check FAILed — the tebako check aggregate; the verdict line names the check and the failed expectation

The three outside the block.

The two everyday codes are 69 (something could not be fetched — TEBAKO_OFFLINE is checked first) and 73 (a malformed jail policy — the run fails closed and nothing mounts).

Three codes live outside the loader block, each owned by its own layer: 126 is not a loader exit but the ENOKEY errno — a read of a sealed (encrypted) path without the key material answers it, and a payload that surfaces the errno exits with it; 132 is the runtime factory’s refusal of a pre-era or corrupt source tarball — it appears in factory continuous integration (CI), not on a user machine; 138 is a press-time miss: TEBAKO_OFFLINE=1 with the bootstrap not yet in the local store.