Eagle Eye Filament Laravel Package

Product Decisions This Supports

• Build vs. buy for internal audit tooling. The single biggest decision this informs is whether to keep funding a bespoke "activity log / audit trail" admin screen. This package ships the overview cards, facet-based explorer, event detail with field-level diffs, trace timeline, record history and dashboard widgets as a Filament UI — a meaningful chunk of what a team would otherwise spend a quarter building and then maintaining forever.
• Compliance and audit readiness on the roadmap. Record history, actor activity heatmaps and policy-gated field reveal map directly onto the evidence requests that show up in SOC 2, ISO 27001, GDPR/DSAR and HIPAA access-review work. That makes "can we answer who changed this record, when, and from where" a configuration question rather than a feature request.
• Support and incident-response workflows. Stream and trace views plus structured token search shorten the path from "customer reports something odd" to "here is the sequence of events." That is a support-cost lever, not just a developer convenience — worth scoring against ticket time-to-resolution.
• Analytics without a BI pipeline. KPI cards, sparklines and channel/severity charts give non-engineers a read on system activity inside the admin panel. Useful for early-stage products that do not yet justify a warehouse; revisit once real product analytics land.
• Admin-panel governance. Livewire interaction capture with readable Filament page/action titles means operator actions inside the admin panel itself become legible audit events ("Alice published the invoice"), which is exactly the trail auditors ask for and exactly what raw livewire.update noise fails to provide.
• Scoping decisions this forces. "Policy-gated reveal" is a product policy question, not a technical one. Adopting this package commits you to answering: which fields are sensitive, who may unmask them, and is the unmasking itself logged? Decide that before the first demo, not after.
• Roadmap sequencing. Adopting now lets you defer a planned internal-tools epic and redirect that capacity; the trade-off is a version-pinning obligation while the API is pre-1.0.

When to Consider This Package

Consider it when:

• You are on, or are willing to move to, Laravel 12/13 and Filament 5.x — this is a hard constraint, not a preference, and it is the single most likely blocker.
• You need an internal, operator-facing view over audit/activity data, not an end-customer surface.
• You are adopting or already run dotswan/eagle-eye as the event store; this package is a UI layer and delivers nothing without it.
• Compliance, audit or support-tooling asks are landing in the next one to two quarters — the value is realised when someone actually needs the trail.
• Your team already knows Filament, so the panel is a familiar surface rather than a new framework to learn for one feature.

Look elsewhere when:

• You are pinned to Laravel 10/11 or Filament 3/4, or your upgrade path is more than a quarter out.
• You have no Filament in the stack — adopting a full admin framework to render one screen is a poor trade.
• You need certified, hosted, retention-guaranteed audit infrastructure (WORM storage, legal hold, vendor SLAs). This surfaces data; it is not a compliance archive.
• You need a customer-facing activity feed — different auth model, different performance envelope, different design language.
• You cannot absorb pre-1.0 API churn. The release is explicit that the API may change before 1.0.0; treat any integration as provisional and pin exact versions.
• The value proposition collapses to "it looks nice" — if no one has asked for the audit trail, the adoption cost is real and the benefit is speculative.

How to Pitch It (Stakeholders)

For executives. This is the first public beta of an admin interface for our audit and activity data. It replaces a category of work we would otherwise build in-house — dashboards, a searchable event explorer, per-record history, trace timelines — with a package we install. The strategic value is compliance and support velocity: when an auditor or a customer asks who changed what and when, we can answer from a UI instead of a database query. The caveats are honest ones: it is a beta with an explicitly unstable API, it requires a current Laravel and Filament stack, and it is a viewer, not a certified audit archive. Recommendation is a time-boxed evaluation on a non-critical environment, not a production commitment, until 1.0.0 lands.

For engineering. The package is a Filament 5 UI over dotswan/eagle-eye; there is no new storage engine and no new event pipeline to operate — the dependency surface is the point. Installation is a two-package Composer require against @beta, and both must move together. The meaningful engineering work is not the install but the policy layer: deciding what "policy-gated reveal" protects, wiring Filament page and action titles so the audit trail reads in human terms rather than as Livewire internals, and pinning versions so beta churn does not leak into main. Treat the API as unstable and isolate it behind a thin internal boundary if you build on top of it.

For the product organisation. The unlock is that activity data becomes legible to non-engineers — support can read a trace, ops can see severity trends, and compliance can pull record history without filing a ticket. That is worth piloting with the people who currently ask engineering for this information, and measuring whether the asking stops.