v3.218.0 — hub inbox admin persistence

Hub Inbox Admin UI Persistence

Reviewer-facing persistence guidance for hub inbox rows, outbound instructions, acknowledgement receipts, reviewer evidence exports, round-trip fixtures, ErrorNotifier stale-client signals, and CreativeExpansion review notes.

Boundary: message receipt, acknowledgement, human approval, and protected-anchor application are separate events.

Admin tables and readiness

Hub inbox rows

Inbound client message envelopes become reviewable rows. They do not approve work.

Outbound instructions

Teleodynamic can leave bounded instructions for clients to poll and acknowledge.

Acknowledgement receipts

Acknowledgement proves only that a client saw the instruction. It is not execution.

Reviewer exports

Human reviewers export route screenshots, JSON parse output, cache state, and notes.

Round-trip fixture runner

  1. Issue instruction.
  2. Receive client acknowledgement.
  3. Receive status reply.
  4. Record no-op talk-back if a protected anchor blocks the action.
  5. Export reviewer evidence.
  6. Reject any client-side anchor-apply attempt.

ErrorNotifier and CreativeExpansion closure

ErrorNotifier stale-client fixtures

Repeated communication failure becomes telemetry and review evidence, not automatic remediation or incident closure.

CreativeExpansion review notes

Dashboard copy and UX proposals enter review buckets as proposal-only drafts, not publication.

Protected-anchor apply separation

Client messages, acknowledgements, no-op talk-back, and reviewer exports do not mutate totem.uai, taboo.uai, or talisman.uai. Apply requires a separate human-governed event with audit evidence.