Documentation
¶
Overview ¶
Package actor carries WHO is performing an action across layer boundaries.
The audit log needs to attribute every mutation, but core.Manager sits below the HTTP and bot layers and can't reach a session cookie or a Telegram update. So the actor rides the request context: each entry point (panel session, API key, Telegram bot, subscription page) stamps it once, and the Manager reads it back when it writes its audit row.
This lives in its own leaf package rather than in core so the bots can stamp an actor without importing core — the telegram package deliberately depends on core only through its own narrow Panel interface.
Index ¶
Constants ¶
This section is empty.
Variables ¶
var System = Actor{Kind: model.ActorSystem}
System is the fallback for anything the panel does on its own initiative — the background poller, a provider webhook. A context with no actor means exactly this.
Source Files