Core Bundle Laravel Package

Product Decisions This Supports

• Feature and lifecycle: v1.19.0 makes archive an active lifecycle event: archiving an entity automatically resets its history. PMs can use this to align “archived” with “history no longer current,” reducing stale version/history data. The per-entity resetOnArchive override gives product and engineering an exception path.
• Roadmap: Useful for account/user retirement, workspace/tenant deactivation, content deprecation, soft-delete cleanup, and data-minimization initiatives. Add archive-policy requirements to the roadmap: what is retained, reset, and exempt.
• Build vs buy: Favor the package when standard Laravel entity archive plus history cleanup is close to your needs. Build custom only for legal hold, immutable audit, selective retention, or cross-system archival.
• Use cases: user/account archival, tenant offboarding, content retirement, cleanup of version history, and compliance-friendly minimization where policy allows.
• Risk decision: Because reset is automatic by default, treat this as a potential behavior change for existing archive flows. PM should require an inventory of archive paths and resetOnArchive overrides before broad rollout.

When to Consider This Package

• Consider it when your Laravel app has explicit entity archive/deactivation and associated history or version data that should not linger after archive.
• Consider it when per-entity exceptions are sufficient; engineering can override resetOnArchive where history must persist.
• Consider it when default reset is acceptable or can be reviewed and staged with tests/feature flags.
• Look elsewhere or plan custom work if you need immutable audit trails, legal hold, regulatory retention schedules, cross-system archival, or granular record-level retention. Avoid it if “archive” is only a UI filter with no lifecycle meaning.

How to Pitch It (Stakeholders)

Executives: v1.19.0 improves lifecycle hygiene: archiving an entity can automatically clear obsolete history, reducing storage cost and stale-data risk. The per-entity override keeps exceptions manageable. Engineering: the release is additive, but the default reset can change archive behavior; inventory archive flows, add resetOnArchive overrides for audit-sensitive entities, and test before enabling broadly. PM recommendation: adopt if archive already means “retire”; otherwise define archive semantics first.