cadrumo.application.bucket_maintenance package

Inert namespace for bucket-maintenance application services.

The defining service module owns BucketMaintenanceService and its Pydantic command/result contracts for profile-scoped storage maintenance. The service is currently a read-only surface over the current-capsule primitives: target locking (deletion_target_locks), a deletion pre-assessment (assess_deletion), namespace-level inventory (the browse and disk-usage surfaces were retired with their producerless contracts).

Bucket rename, bucket delete, bucket archive (reversible dormancy), bucket restore, sealed-archive export/import/inspect, and the earlier sandbox lifecycle (create_sandbox / discard_sandbox / archive_sandbox / restore_sandbox / merge_sandbox) were removed from this package when profile identity moved onto the encrypted custody capsule; see application.user_profile (ProfileCapsuleLifecycle) for the surviving create/restore/select/delete primitives. Bucket rename has no successor primitive; bucket delete lives on as ProfileCapsuleLifecycle.prepare_delete / confirm_delete / delete, consumed today only by the durable all-profile application.config_reset flow. Bucket delete has no single-target operator route; bucket archive, bucket restore, and sealed-archive export/import/inspect have no successor primitive at all. BucketMaintenanceService.assess_deletion() is the retention pre-assessment for a destructive delete; it does not implement reset orchestration itself.

The package initializer exports no symbols; consumers import each contract from its defining module.

See also

application.user_profile

ProfileCapsuleLifecycle, the custody transaction owner for create, restore, select and delete.

application.config_reset

The durable all-profile reset flow, the sole current caller of ProfileCapsuleLifecycle.delete.

Submodules