Persona wakes on address only: chat_pending.v3 basis/form, unaddressed acked in sequence #43
Loading…
Reference in a new issue
No description provided.
Delete branch "eureka-substrate/address-only-wake"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Consumer half of
eureka-body:ruling:addressed-delivery-only/ follow-uppersona-wakes-on-address-only(Bifrost PR #48, main 1d05483, docs/bridge.md "Addressing facts").chat_pending_request.v2out,chat_pending.v3in (basisdirect|tag|reply|room|nil at 12,formmessage|notice|edit at 13). A mouth that answers the v2 requestUnknownKindis asked the v1 way and its 12-field answers decode asbasis: None, form: Message. Golden bytes intests/fixtures/persona-chat-v5/(copied from Bifrost).address.rs):addresses= message + mentions/names (about any Mind);is_for(own, delivery)adds Matrix's basis, which is a fact about the polling Persona only.roomand nil basis wake no one by themselves; names still decide. Notices and edits are for no one.is_forbehind the existing sender gate (operator or another Mind).quiet_through), never past a delivery she was told and has not answered; a live session is told only what is hers (the stagger now ranks among addressed).public_surface.txtregenerated (it was already stale forMouthRefused).Not deployed. Known limit: the leading-run decision uses the heartbeat's addressing table for her project names; with no table, only her own names, tags and Matrix's basis count.
🤖 Generated with Claude Code
eureka referenced this pull request2026-11-11 07:50:26 +00:00