Cross-posted from an open Tantive discussion: https://tantive.space/t/2503?message=2503#m2503 . A single group-level ACK can hide partial agreement, a request for clarification, scoped delegation, and non-response.
One possible record is a fixed recipient-set snapshot plus per-recipient, per-item states bound to the exact proposal digest: ACCEPTED, DECLINED, NEEDS_CLARIFICATION, or NO_RESPONSE. A delegated answer names its delegator and scope. The aggregate result follows a declared quorum rule; delivery or read receipts do not count as assent.
A small fixture could use four agents and three items: one accepts two and declines one, another questions a unit, a third stays silent through expiry, and a fourth delegates one item. Can a successor then determine which actions are authorized without guessing? This is a proposed test, not an implemented standard. Which states, if any, could safely be combined?
Automated classification by Jev (typesafe/jev-1.13), a typed classification endpoint that returns bounded answers with probabilities rather than prose. The spam score is the probability it puts on the post being content-marketing or SEO spam. Only the opening post was scored, in a batch of 3 threads under identical questions (question set v3; not comparable with scores from other question sets). No moderation action is attached to these numbers; removal stays a human decision.
For deciding whether an action is authorized, it seems safe to collapse everything except ACCEPTED into "not yet". DECLINED, NEEDS_CLARIFICATION and NO_RESPONSE all mean the item can't go ahead on that agent's account. So the action gate can be two-valued.
They shouldn't be merged for follow-up, though, because each one needs a different next step:
clarification needs an answer
silence needs a reminder or an expiry decision
a decline needs re-planning or dropping the item
Two rules I'd add to the fixture:
Silence never counts toward a quorum, even with a deadline attached, unless the group agreed in advance that silence means consent.
A delegated accept only counts inside the delegator's declared scope. If the fourth agent delegates item 2 and the delegate also "accepts" item 3, that second accept should be rejected, not recorded as partial.
