Skip to main content
← Chronicles
2 min readFree ChronicleCurrent recordUpdated

A Decoder Is a Resource Scheduler

Decompression is not merely the inverse of compression. It is resource scheduling performed against declarations supplied by an archive you do not yet trust.

ZJX signal lattice resource scheduling artwork
Infrastructure Record

The Archive Is Asking For Resources

Every stored size, declared length, and path inside an archive is a request. A naive decoder accepts those requests as facts. A safe decoder treats them as proposals that must fit an independent operating budget.

This reframing changes the architecture. Instead of asking only whether a payload can be reversed, the system asks how much output may be materialized, how long each step may run, where temporary bytes may land, which destination components may be traversed, and what evidence must survive when the operation stops.

Expansion

Declared output is a request to validate, not permission to allocate.

Time

Every decoding step runs under its own deadline and stops cleanly when the deadline passes.

Storage

Memory and temporary disk are separate budgets, each with its own ceiling.

Paths

Every destination component must remain inside the approved extraction root.

Three States That Stay Separate

Decoder readiness answers whether the current host can read the archive. Integrity answers whether stored bytes, sizes, and digests verify. Extraction permission answers whether this destination and overwrite plan are allowed now. Each state is decided on its own evidence.

A no-write plan answers these questions before any payload is written, and extraction enforces destination policy again when it runs.

Failure Is Part of the Decoder Contract

A good decoder names every refusal. The operator learns whether the host is not ready, the archive is malformed, a valid request exceeds policy, decoded bytes fail integrity, or the destination blocks an otherwise valid extraction. Each outcome points to a different recovery action.

Named outcomes also make conformance testing useful. A test vector proves that an archive was refused at the intended boundary, before an allocation or a destination write escaped its budget, and future implementations can reproduce that result.

The central rule is simple: metadata proposes work, policy authorizes resources, and verification decides whether the result is true.

Named decoder outcomes

Not ready
The current host cannot read this archive yet. No integrity conclusion has been reached.
Malformed
The archive's structure, sizes, or paths are invalid.
Budget denied
The request is structurally valid but exceeds a named resource ceiling.
Integrity failed
Decoded bytes disagree with the archive's own size or digest evidence.
Extraction denied
Destination, overwrite, link, or path policy blocks the write.