SubscriberTable
Corex\Newsletter\Subscriber\SubscriberTable · class · Add-ons layer
The subscribers table, and what CoreX may do to it (spec 074). This is the framework’s reference writable model, and it is one because a mailing list is the case where importing genuinely belongs: moving a list off another provider is a real thing people do, and the rows are records the site owner authored rather than history somebody else made. Every other managed table CoreX ships is an audit or system log — activity, jobs, login attempts, notifications, reading events, access grants — and those stay read-only, because manufacturing a past event through a CSV would make the audit trail worthless. status is deliberately not writable. Confirmation state is owned by the double opt-in flow; letting an import set it would let somebody import a list as pre-confirmed and skip consent entirely. Imported subscribers arrive in the same pending state as anyone who typed their address into the form.