Hypervel Auditing Laravel Package

Product Decisions This Supports

• Compliance and audit-trail roadmap: Supports features that require “who changed what, when” records—useful for regulated customers, enterprise procurement, and internal governance.
• User attribution and impersonation flows: Auditor::actingAs($user, fn () => ...) lets the product attribute audits to a specific causer inside a callback, which is valuable for admin impersonation, background jobs, imports, and system-triggered changes.
• Testability of audit behavior: Auditor::fake() makes audit events assertable in tests, reducing the cost of shipping audit-dependent features and lowering regression risk.
• Build vs. buy: Auditing is often commodity infrastructure, but compliance-specific behavior, redaction, and causer attribution can justify buying/ adopting a package rather than building from scratch—provided the team accepts pre-1.0 API risk.
• Feature prioritization: Enables PMs to prioritize audit visibility, actor attribution, and compliance reporting without blocking on custom infrastructure.
• Adoption risk decision: The release requires hypervel/components 0.4.x-dev, so PMs should treat platform dependency stability as a gating factor for production roadmap commitments.

When to Consider This Package

• Consider it when building on Hypervel and you need first-class audit logging with causer attribution and test assertions.
• Consider it when your roadmap includes compliance, admin action tracking, impersonation audits, or “who did this” support workflows.
• Consider it if your team uses the package’s built-in Auditor and does not maintain custom implementations of Ipsocode\Auditing\Contracts\Auditor.
• Look elsewhere or defer if you need a stable 1.0+ API contract, cannot tolerate a 0.4.x-dev platform dependency, or are not on Hypervel.
• Plan migration work if you have custom auditors: v0.2.0 adds actingAs() and currentCauser() to the contract, which is breaking for direct implementers.
• Be cautious if your organization requires long-term support guarantees, predictable release cadence, or no dev-branch dependencies in production.

How to Pitch It (Stakeholders)

For executives: This package gives us audit-trail capability with actor attribution and test coverage, which can support compliance and enterprise readiness. The trade-off is maturity risk: it is pre-1.0 and currently tied to a dev version of hypervel/components, so we should pilot it before making it a committed production dependency.

For engineering: v0.2.0 adds Auditor::actingAs() for explicit causer attribution and Auditor::fake() for test assertions. Applications using the package’s own Auditor are unaffected, but custom implementations of the Auditor contract must add actingAs() and currentCauser(). The main adoption concern is the hypervel/components 0.4.x-dev requirement and the breaking contract change for custom auditors.