Skip to content

Chapter 29: The Fleet

Cattle, Identity, and Consented Support

The surface shows services, and underneath it are machines — this chapter makes them a fleet with identities and records rather than pets.


1. Machines Are Not Pets

The three structures run on machines somewhere. A fleet is not a set of servers you tend; it is a set of nodes you replace. The moment a machine is named, hand-configured and remembered, it has become a pet — and a pet is a machine nobody can rebuild.

Cattle, concretely:

Property What it means
enrolment a bare machine becomes a node in one idempotent command
identity the node has its own identity, revocable in one command
configuration everything comes from the repository, nothing from memory
reimage the node is replaced, not repaired

What must survive a rebuild: data that is not on the node, configuration that is in the repository, identity that can be reissued. What must not: anything a human typed into it.

🎯 What You'll Learn

  • What enrolment means when a machine is disposable
  • Why node identity is the precondition for everything else
  • Consent-first support as a record, not a courtesy

Roles as Capabilities

A node is not "the database server"; it declares a capability — support, storage, compute — and the fleet schedules by capability. Optional infrastructure must never be a dependency: a workstation-class node can vanish without taking the estate with it.

Pooled capacity, simple replication, shared pools — never per-contributor silos. A silo is a pet with a person's name on it.

✅ What to Check

  • Name a machine you would not rebuild today. That is a pet.
  • Does a node declare capabilities, or a role someone typed?

2. Enrolment and Identity

Command What it does The checkpoint
enrol bare machine → node, idempotent run twice, one node
revoke node identity → invalid, one command the node cannot rejoin

Identity is the precondition. Without it, the fleet has no way to refuse a node, and support has no way to name who was helped.

Capacity and cost telemetry come from the fleet itself: who is using what, and what it costs. A fleet you cannot measure is a fleet you cannot size.

✅ What to Check

  • Can a node join without an identity? That is the gap.
  • Is revocation one command, or a procedure with a checklist?

3. Consented Support

Remote support on someone else's machine is the most sensitive operation in this book. Consent-first means three things, all recorded:

Element The record
visible consent the person saw the request, and approved it
audit trail who connected, when, for how long, to what
partner isolation the session could reach their scope, and no further

A support flow without a record is a courtesy. A support flow with a record is a control — and the difference is what a client is buying when they ask "who can see our data?".

The Support Record, as a shape

support_session:
  requested_by: <who>
  consented_by: <the person, at what time>
  scope: <what was reachable>
  duration: <from, to>
  actions: [<the changes made>]
  isolated: true

✅ What to Check

  • Can you reconstruct the last support session from a record?
  • Could a session reach beyond the partner's scope? That is the isolation test.

4. Degradation

A fleet loses nodes. The question is not whether, but what still works:

  • which services degrade, and how;
  • which data remains readable;
  • which operations refuse, rather than corrupt.

The degradation table is written per node class, and rehearsed by killing a node. A table nobody has tested is a hypothesis about resilience.

✅ What to Check

  • Kill a node (in a drill). Does the estate behave as the table says?
  • Does anything refuse rather than corrupt?

5. The AI Delta

An agent may reimage a node, so enrolment must be identity-bound and revocation must be one command.

Support consent has to be a machine-checkable record rather than a conversation, because an agent can request a session and an agent can grant one if nothing stops it.

💰 Cost Check: a pet machine costs the afternoon you cannot rebuild it. A support session without a record costs the client question you cannot answer. A fleet without a degradation table costs the surprise on the day a node dies. Enrolment and identity cost a day and make the rest routine.

flowchart LR
  B["bare machine"] --> E{"enrol — idempotent"}
  E -->|"identity issued"| N["node"]
  N --> C["capability declared"]
  N --> S["support — consented, recorded"]
  N --> R{"revoke"}
  R -->|"one command"| X["cannot rejoin"]

What this shows: the node's life is two commands and a record — no step depends on remembering what a person typed.

The Delegation Line

The agent enrols nodes, reports capacity and requests support. The human consents to the session and approves the lifecycle. The system refuses a node without an identity, and a support session without a recorded consent.


6. Build the Delivery

Deliverables

Artefact Shape Where it lives
enrolment recipe bare machine → node, idempotent fleet/enrol/
node identity per node, revocable, audited the identity store
support flow consent · record · isolation the Playbook
capacity report who uses what, and the cost generated
degradation table what works when a node is gone the Playbook

Decisions

Choice Default What changes if you choose otherwise
reimage or configure in place reimage, because it is testable a node with a history nobody can reproduce
support by session or proxy session, with consent recorded a channel with no attribution
pooled or dedicated pooled, with declared exceptions silos per contributor
capability or role capability a node whose purpose is a name

✅ Gates

  • A node without an identity cannot join.
  • A support session without recorded consent is refused.
  • A fleet change that breaks the degradation table is a finding.

Runbook

  1. Write the enrolment recipe. Checkpoint: run twice, one node.
  2. Issue node identities. Checkpoint: a node without one cannot join.
  3. Implement consented support. Checkpoint: a session without consent is refused.
  4. Emit capacity telemetry. Checkpoint: cost per node is answerable.
  5. Kill a node and read the degradation Map. Checkpoint: the behaviour matches the table.

🎯 Proof

  • A node replaced in one command.
  • A support session an auditor can reconstruct.
  • A node loss that degrades as documented.

7. 🔑 Chapter Summary

A fleet is disposable machines with identities and records — not servers you tend.

  1. Cattle means enrolment, identity, configuration from the repository, and reimage — never a named machine.
  2. Capabilities, not roles; pooled capacity, never per-contributor silos.
  3. Consent-first support is a record — visible consent, audit trail, partner isolation.
  4. The degradation table is written and rehearsed, or it is a hypothesis.
  5. The agent enrols and requests; the human consents; the system refuses identity-less nodes and unconsented sessions.