vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(#3255): state the present, drop the changelog framing

Browse source 
mara: "pls remove historical wording, only present pls".

The correction was written as a diff against what the docs used to claim
-- "this used to say X", "where this is going", "the intended state for
now". That is a changelog, and a reader arriving cold has to reconstruct
the current truth from it. The reasoning about why the old shape was
wrong belongs in the PR that changed it, not in the file.

Now says what is true: the controller interprets a delivery and emits a
semantic message; receipt is all that is wired today because the
swarm->hive channel does not exist yet.
This commit is contained in:
atlas 2026-08-18 12:35:27 +02:00
commit eb8387bd73
2 changed files with 19 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

24
swarm-controller/src/webhook.rs
View file

@ -6,23 +6,17 @@
//! deliveries. One owner is the only non-racing shape, and the only
//! swarm-wide thing in the deployment is this daemon.
//!
//! **Receipt only, for now — the interpretation lands here next.** The
//! payload is currently opaque bytes keyed by a [`DeliveryKind`] from the URL
//! path, because nothing consumes it yet.
//! **This daemon interprets a delivery; it does not forward it.** It parses
//! the payload and emits a semantic message — *the knowledge repo changed*,
//! *deploy agent X at rev Y* — addressed to the hives that need it. One place
//! decides what a forge payload means, so no hive re-derives it.
//!
//! ⚠️ This used to say *"this relays; it does not interpret"*, and that is no
//! longer the direction: this daemon is to **parse a delivery and emit a
//! semantic message** — *knowledge repo changed*, *deploy agent X at rev Y* —
//! addressed to whoever needs it, rather than forwarding forge bytes for each
//! hive to re-derive. The earlier reasoning ("parsing here would be a second
//! place deciding what a delivery means") counted this daemon as a *second*
//! interpreter while assuming the hives stay interpreters. They do not: the
//! parsing **moves** rather than duplicating, so one place decides.
//! Receipt is all that is wired today: the payload is opaque bytes keyed by a
//! [`DeliveryKind`] from the URL path, and nothing consumes it until the
//! swarm→hive channel exists.
//!
//! The HMAC code is deliberately **not** shared with `hive-c0re`: that copy
//! is leaving, not staying, and a shared crate is right only when a second
//! consumer *arrives*. Same arriving-or-leaving question as the paragraph
//! above, asked about code instead of about meaning.
//! The HMAC code is deliberately **not** shared with `hive-c0re`: that copy is
//! leaving, and a shared crate is right only when a second consumer arrives.
//!
//! **These hooks are registered ALONGSIDE the per-hive ones** — see
//! [`crate::forge::Client::ensure_swarm_webhooks`].