Classify Existing Hardware by Role, Not Product Tier

We measured idle state and model-loaded state separately. Storage capacity does not prove that a model can remain loaded with OS and context headroom.

The working rule for “The operating problem” is: We measured idle state and model-loaded state separately. Storage capacity does not prove that a model can remain loaded with OS and context headroom. Preserve timestamped state transitions, reason codes, and retry outcomes so that an operational decision can be reconstructed later.

For verification, save the model and runtime versions, source input, relevant settings, and observed output together. Repeat the step while changing only one factor, and record unexpected results and untested limits as carefully as successes before applying the guidance to private or production data.

The inventory records memory, sustained cooling, AC power, network, available hours, and whether a person uses the machine at the same time.

The working rule for “The design decision” is: Initial roles are coordinator, interactive worker, batch worker, and knowledge worker. Their stability requirements differ. Preserve timestamped state transitions, reason codes, and retry outcomes so that an operational decision can be reconstructed later.

Preserve the before-and-after state and the time of the check so that another run can reproduce the result. Include at least one failure condition—such as empty input, constrained resources, or a restart—to reveal the boundary of the step rather than documenting only the happy path.

Initial roles are coordinator, interactive worker, batch worker, and knowledge worker. Their stability requirements differ.

The working rule for “How the mechanism works” is: The first inventory is complete when every device has a role or exclusion rule and one coordinator plus one chat worker have been selected. Preserve timestamped state transitions, reason codes, and retry outcomes so that an operational decision can be reconstructed later.

Define completion with an observable result instead of a general impression. Repeat the same input, and if the output changes, isolate whether the model, runtime settings, or source data changed before moving to the next stage.

Every excluded device receives a reason and a retest condition such as wired networking, a RAM upgrade, or night-only use.

The working rule for “What we verified” is: We measured idle state and model-loaded state separately. Storage capacity does not prove that a model can remain loaded with OS and context headroom. Preserve timestamped state transitions, reason codes, and retry outcomes so that an operational decision can be reconstructed later.

For verification, save the model and runtime versions, source input, relevant settings, and observed output together. Repeat the step while changing only one factor, and record unexpected results and untested limits as carefully as successes before applying the guidance to private or production data.

The first inventory is complete when every device has a role or exclusion rule and one coordinator plus one chat worker have been selected.

The working rule for “Boundary and completion criteria” is: Initial roles are coordinator, interactive worker, batch worker, and knowledge worker. Their stability requirements differ. Preserve timestamped state transitions, reason codes, and retry outcomes so that an operational decision can be reconstructed later.

Preserve the before-and-after state and the time of the check so that another run can reproduce the result. Include at least one failure condition—such as empty input, constrained resources, or a restart—to reveal the boundary of the step rather than documenting only the happy path.