Skip to content

Releases: Maatify/event-logging

Release list

v1.0.0 — Initial Stable Release

v1.0.0 — Initial Stable Release Latest
Latest

Choose a tag to compare

View all tags
@Maatify Maatify released this 09 Jul 07:09
v1.0.0
9f15eab
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

maatify/event-logging v1.0.0

Initial stable release of maatify/event-logging.

This release delivers a framework-agnostic standalone Composer package for isolated event logging domains within the Maatify ecosystem.

Highlights

  • Six isolated logging domains:

    • AuthoritativeAudit
    • AuditTrail
    • SecuritySignals
    • BehaviorTrace
    • DiagnosticsTelemetry
    • DeliveryOperations

  • MySQL/PDO-only persistence with domain-owned repositories and schema files.

  • Typed domain recorders and query interfaces.

  • Factory and provider-based wiring through EventLoggingProviderFactory.

  • Optional pure-PHP DI bindings through EventLoggingBindings::definitions().

  • Optional PSR-3 fallback logging for fail-open domains.

  • AuthoritativeAudit remains fail-closed and does not degrade to fallback logging.

  • Primitive read/query APIs for admin and integration use cases.

  • Release-grade documentation, examples, security policy, contribution guide, and code of conduct.

Architecture Guarantees

  • Framework-agnostic core.
  • No mandatory framework bindings.
  • No Laravel, Slim, Symfony, or PHP-DI runtime dependency.
  • No host application namespaces.
  • No controllers, routes, UI, permissions, or dashboards.
  • No generic logging API.
  • No domain-string routed logger.
  • No shared generic logs or event_logs table.
  • No SQLite runtime support or fallback.

Optional DI Bindings

This release includes optional pure-PHP DI binding helpers for host applications that prefer container wiring.

php-di/php-di is listed only under Composer suggest; it is not required by the package.

Validation

The final Release Readiness Gate passed successfully.

Validated areas include:

  • Composer package metadata
  • Architecture boundaries
  • Domain isolation
  • Failure semantics
  • Optional DI bindings
  • Schema readiness
  • Examples and integration documentation
  • PHPUnit
  • PHPStan
  • Composer validation

Installation

composer require maatify/event-logging

Notes

This is the first stable release and is suitable for use as the baseline 1.x package version.

Assets 2
Loading