Fleet

The fleet surface keeps machines visible, trusted, and converged through a readable store and host-owned evidence.

• Store — the layered desired-state repository.
• Convergence — one edit from source to applied state.
• Trust — roster, signing ratchet, enrollment, and revocation.
• Operating — commands, cadence, doctor, and journals.
• Config — the local machine and capability schema.
• Why jj — the version-control properties that support the store.

Desired state gives the same model a standalone reader path.