Přeskočit obsah

Operator task packs HOWTO

The complete implemented walkthrough lives with its Node owners: English HOWTO and Polish HOWTO. Its command examples are checked by the actual CLI parser in both languages; they do not authorize effects when validated.

The procedure covers package inspection, pinned qmail image preparation, conformance and activation, restrictive local binding choices and profile diffs, readiness, exact offer approval, one local or queued remote task, HIL per mutation, verification/destruction evidence, pause/resume, recovery, withdrawal and revocation. It reuses existing APIs rather than describing candidate commands as available.

The communication-continuation development checkpoint adds an exact epoch preview, confirmation and interrupted Room recovery to the participant page. It preserves the original cumulative loop budget and deadline, but inherits no membership or effect approval. Historical candidate adoption and cross-epoch task routing remain unimplemented; this is not full guided continuation qualification. The Node HOWTO states the resulting task-position refusal.

Package provenance, local trust and current execution authority remain separate. Proposal 094 owns the bounds and decisions; Story 013 owns the qmail reference. The owner-refusal gate preserves historical native and physical evidence classes and does not adopt the proposal or declare alpha ready. Known journal capacity and unsupported relay migration recovery are explicit in the walkthrough, not hidden behind an automatic retry.