Block a user
[Task] Which future module comes first after platform cleanup: cases, workflow, or connectors?
[Task] Which event transport is the first production target: DB outbox only, Redis/Celery, or pluggable dispatch?
[Task] Should admin be one platform module or split across access/tenancy/policy/audit?
[Task] Should tenants be extracted before policy, or after access but before policy?
[Task] Is access required for any useful product startup, or should kernel-only expose only health/shell/config pages?
[Task] Should
govoplan-core be renamed conceptually to govoplan-kernel, while keeping package compatibility for now?
[Task] Write
govoplan-idm concept
[Task] Write
govoplan-audit concept
[Task] Write
govoplan-policy concept
[Task] Write
govoplan-connectors concept
[Task] Write
govoplan-workflow concept
[Task] Write
govoplan-cases concept
[Feature] Keep mailbox, mail policy, mail credential inheritance, and file storage behavior covered by focused tests
[Feature] Ensure mail does not require campaign
[Feature] Ensure files does not require campaign
[Feature] Ensure campaign uses files/mail only through capabilities/metadata/API boundaries
[Feature] Keep module-specific admin panels in owning modules
[Feature] Move generic admin layout into core WebUI
[Feature] Define admin route contribution contract
[Task] Inventory admin pages by owning future module