Verbs History Laravel Package

Product Decisions This Supports

• Event-sourced audit/history capability: Using hirethunk/verbs-history alongside Verbs lets the team capture domain event history without building bespoke audit-log or event-replay infrastructure.
• Build vs. buy for event history: For a Laravel product already committed to Verbs, adopting this package is likely cheaper than building historical event persistence, projection rebuild support, and audit trails in-house.
• Roadmap dependency planning: v0.6.0 is primarily a compatibility release adding Verbs v0.6 support. It informs upgrade sequencing: if the product plans to move to Verbs v0.6, this package version must be included in that upgrade wave.
• Use cases to validate: regulatory/audit trails, customer-visible activity history, debugging via event replay, and reconstructing aggregate state from historical events.
• Risk tracking: The package is still pre-1.0 and tightly coupled to Verbs. PM should treat it as an infrastructure dependency with lockstep upgrade requirements, not a standalone product differentiator.

When to Consider This Package

• Consider it when: the product is already using or actively evaluating Verbs for event sourcing in Laravel, and the team needs persisted event history, auditability, or replay support without custom infrastructure.
• Strong fit when: the roadmap includes event-driven domain workflows where historical traceability is a product or compliance requirement.
• Upgrade-specific criterion: adopt v0.6.0 only if the application is moving to Verbs v0.6 or already on it. Teams staying on older Verbs versions should not upgrade this package independently without verifying compatibility.
• Look elsewhere when: the product is not using Verbs, needs a vendor-neutral event store, requires a stable 1.0+ API surface, or cannot tolerate pre-1.0 dependency churn and lockstep upgrades with an upstream event-sourcing framework.
• Also look elsewhere when: the team needs managed event infrastructure, cross-language event streaming, or enterprise-grade audit/retention features beyond a Laravel package’s scope.

How to Pitch It (Stakeholders)

For executives: This is a small but important compatibility update to an event-history add-on for our Laravel event-sourcing stack. It does not add new customer-facing features; it keeps our audit/replay capability aligned with Verbs v0.6. If we upgrade Verbs, we should plan this package upgrade at the same time to avoid compatibility gaps.

For engineering: v0.6.0 adds Verbs v0.6 support and brings in a new contributor. Treat it as an upgrade enabler rather than a feature release. Before adopting, confirm the app’s Verbs version, run migration/compatibility tests, and verify event persistence and replay behavior. Because the package is 0.x and tightly coupled to Verbs, pin versions and include this in dependency-upgrade planning.