best-peer 0.0.24

best-peer 0.0.24

Every peer serves /metrics to a collector holding a key that may read them and nothing else, and a cloud door serves its members' series under the workspace, the cloud and the peer; best-peer answers -h and --help with its commands and settings.

Commits since v0.0.23

• Review: a renamed or re-pointed member's series are cleared after the members are swapped, and a scrape checks its member and writes under the one series lock, so the machine a name stood for before cannot be shown as the one it stands for now (006a612)
• Review: a key held to the accelerators reads no member's CPU among the federated series, and a scrape answered after its member was removed, re-pointed or no longer admits the cloud is dropped (aa96633)
• Review: a cloud door serves of a member only what is the cloud's to show, to whom it may show it: the machine's own series and the workloads the cloud placed there, the door's labels winning, to a collector for every cloud and to a key approved for all for the workspaces it is a member of; a removed, re-pointed or no longer admitted member has none, and the scrape never holds back the tick (90159ea)
• A cloud door serves its members' series under where they sit: each cloud reads a member's /metrics with its own credential at every reconcile tick, and the door serves them labelled workspace, cloud and peer to a key that reads the whole door; a member that does not answer has none. A metrics key stands alone, and a workspace's door serves no /metrics (behavioralstate/spec#47) (4665888)
• Every peer serves /metrics, how its devices, workloads and door move, to a collector holding a key that may read them and nothing else (behavioralstate/spec#47) (2ba23d0)
• best-peer answers -h and --help with its commands and the settings to start with, and each command with its usage, so an operator or an agent setting a peer up can ask the binary what it takes (behavioralstate/spec#83) (1f430dc)

Run it

One binary. Download the archive for the machine, check it against SHA256SUMS, unpack it and run best-peer with the environment the README's Run section names; best-peer --version says best-peer 0.0.24. Each archive is here twice, byte for byte the same: under the name with the version, for pinning, and under the name without it, which releases/latest/download/<name> resolves to the newest release, as the README's commands use.

Machine	Archive	Same file, unversioned
Linux x86_64 (glibc 2.35 or newer)	best-peer-0.0.24-x86_64-unknown-linux-gnu.tar.gz	best-peer-x86_64-unknown-linux-gnu.tar.gz
Windows x86_64	best-peer-0.0.24-x86_64-pc-windows-msvc.zip	best-peer-x86_64-pc-windows-msvc.zip
macOS Apple silicon	best-peer-0.0.24-aarch64-apple-darwin.tar.gz	best-peer-aarch64-apple-darwin.tar.gz

Every archive carries a build provenance attestation: gh attestation verify <archive> --repo behavioralstate/best-peer.