application/

Package activity declares how an item's history is written and how it is read back.

Package admin holds the control plane's outbound ports (multi-tenancy.md §5).

Package audit declares how the evidence trail is read back.

Package automation is the repository port of the rules (automation.md §1).

Package backup is the outbound port for the targets a tenant has configured.

Package idempotency declares what the idempotency guard needs from storage.

Package identity declares what the identity use cases need from storage.

Package importer is the outbound side of an import: the run's repository, and the converter port - a foreign file in, archive records out.

Package integration holds the repository ports of what reaches into this system from outside it: today the calendar feeds, later the webhook subscriptions beside them.

Package job is the outbound port for background work as a caller sees it.

Package jumble is the repository port of the inbox (domain-model.md §2).

Package lifecycle declares what the end of data's life needs stored: the instructions not to delete, and the record of what was deleted anyway.

Package mail is the store of a workspace's mail intake (ADR-0094): its settings, the receipts of what it received, and the lookups that route a message.

Package media declares what the media use cases need from storage of the *records* - the rows beside the bytes.

Package meta declares what the self-description needs from storage.

Package notification declares what the notification path needs from storage: the records it writes, and the preferences it honours.

Package outbox declares how a domain event leaves the write path.

Package privacy declares what data subject rights need stored: the case, the consent, and the two marks an erasure leaves on things it does not delete.

Package quota holds the outbound ports of the §4 limits (multi-tenancy.md).

Package sealing is the census a rotation ends on (ADR-0045, security.md §8.1): how many stored values still name each master key, and in which kind of value.

Package streams holds the outbound port of the partitioned streams' maintenance: activity entries, outbox events and rule runs partition by month, the leader keeps the coming months existing, and the retention engine drops what has wholly aged out.

Package suggestion is the outbound port of what AI proposed.

Package sync declares what offline clients need recorded about a change.

Package view declares how the application layer stores saved views.

Package voice is the store of a workspace's voice settings (ADR-0093).

Package work declares what the work management use cases need from storage.

Package access decides whether an actor may do something.

Package admin holds the control plane's use cases: the lifecycle of a tenant, as multi-tenancy.md §5 draws it.

Package audit is the trail as somebody reads it: a page of it, an archive of it, and the check that it has not been rewritten (audit.md §5).

Package automation holds the use cases that write the rules (automation.md §1).

Package backup is where an operator says where backups go, and finds out whether they can (backup-restore.md §2).

Package idempotency makes a repeated write harmless.

Package identity holds the use cases that turn a credential into an actor.

Package importer is an import from another system (backup-restore.md §9): the use case that accepts one, the read that answers its report, and the job that runs it.

Package integration holds the use cases that let another system reach into this one, and this one reach out: today the webhook subscriptions, later the trigger polling and the jumble's inbound routes.

Package job is the caller's half of the queue: finding out how a piece of background work is getting on, and stopping it.

Package jumble holds the use cases of the inbox (domain-model.md §5): something arrives, is listed, and becomes work or ages out.

Package lifecycle is where data stops existing: the hard delete, and the rules that decide when it is allowed (ADR-0020, data-retention.md).

Package mail is the administration of a workspace's mail intake (ADR-0094): its settings, its log, a collection's handle, and the address a notification's reply goes to.

Package media is the upload life of a file: staged, carried to storage by somebody other than this server, confirmed, and eventually reclaimed (arc42 §8.4).

Package meta answers what this installation is and what it can do.

Package notification is the application half of the Notification context: the consumer that turns events into records, and the delivery that turns a record into a message.

Package platform writes the installation's events: what a provider's purchase platform learns about a workspace (UC-INS-14, multi-tenancy.md §4.3).

Package privacy is data subject rights as use cases rather than as a support process (data-protection.md §4, ADR-0018 decision 4).

Package quota turns multi-tenancy.md §4's table into enforcement: per-tenant limits from `tenant.settings.quotas` with the mode's defaults, one resolution, one refusal shape.

Package sealing is the half of a key rotation that lets it finish (ADR-0045, security.md §8.1).

Package suggestion is the application layer of what AI proposed.

Package sync is the application half of the change stream: what a client is allowed to be told about, and where in the log it stands (ADR-0021).

Package voice turns what a person says to a voice assistant into work (ADR-0093): entries put on a list, a list read out, an entry ticked off, the day's due entries told.

Package work holds the work management use cases: containers and the items inside them.