maatify/exceptions

Policy-driven, escalation-aware exception library for PHP applications.

v1.0.0 2026-02-27 01:19 UTC

Requires

• php: ^8.2

Requires (Dev)

• phpstan/phpstan: ^1.11
• phpunit/phpunit: ^11.0

MIT

• Mohamed Abdulalim

• php
• http
• exceptions
• domain
• Policy
• error-handling
• maatify
• escalation

README

Enterprise-grade, hardened exception handling library for PHP applications.

maatify/exceptions provides a strictly typed, immutable taxonomy for application errors, enforcing semantic correctness, security, and consistent HTTP mapping. It is designed to prevent "taxonomy drift" and ensure that critical system errors are never masked by lower-severity wrappers.

🚀 Key Features

• Strict Taxonomy: Exceptions are categorized into 9 distinct families (System, Validation, Auth, etc.) backed by ErrorCategoryEnum.
• Guarded Overrides: Prevents developers from accidentally mismatching error codes or HTTP statuses.
• Escalation Protection: Automatically escalates severity when a critical exception is wrapped in a lighter one (e.g., a Database failure wrapped in a generic runtime exception will typically retain 500 status).
• Zero Dependencies: Pure PHP implementation. No framework coupling.
• PSR-4 Compliant: Ready for immediate Composer autoloading.

Requirements

• PHP 8.2+

📦 Installation

composer require maatify/exceptions

📖 Usage

Basic Usage

Throwing a predefined exception:

use Maatify\Exceptions\Exception\Validation\InvalidArgumentMaatifyException;

throw new InvalidArgumentMaatifyException('The email format is invalid.');
// Result:
// Category: VALIDATION
// HTTP Status: 400
// Error Code: INVALID_ARGUMENT

Advanced Usage (Wrapping)

When catching a low-level error and re-throwing, the library automatically handles severity escalation:

use Maatify\Exceptions\Exception\BusinessRule\BusinessRuleMaatifyException;
use Maatify\Exceptions\Exception\System\DatabaseConnectionMaatifyException;

try {
    // Simulate a critical database failure (System / 503)
    throw new DatabaseConnectionMaatifyException('Connection timeout');
} catch (DatabaseConnectionMaatifyException $e) {
    // Attempting to wrap it in a "softer" business exception
    // Note: BusinessRuleMaatifyException is abstract, so we use an anonymous class for this example
    throw new class('Unable to process order', 0, $e) extends BusinessRuleMaatifyException {};
}

// RESULT:
// The final exception will report:
// Category: SYSTEM (Escalated from BusinessRule)
// HTTP Status: 503 (Escalated from 422)
// This ensures monitoring tools see the root cause (System Failure), not a generic Business Rule error.

📚 Documentation

Detailed documentation is available in the BOOK/ directory:

1. Introduction
2. Architecture
3. Taxonomy
4. Exception Families
5. Override Rules
6. Escalation Protection
7. Security Model
8. Best Practices
9. Extending The Library
10. API Integration Guide
11. Testing Strategy
12. Versioning Policy
13. Packagist Metadata

🛡️ Guarantees

• Category Immutability: An exception's category is defined by its class and cannot be overridden at runtime.
• Status Class Safety: You cannot force a 4xx exception to return a 5xx status code manually, or vice versa.
• Escalation Determinism: Severity calculation is deterministic and side-effect free.

✅ Quality Status

• PHP 8.2+
• PHPUnit 11
• 100% Code Coverage
• Zero Warnings
• Immutable Exception Design
• Deterministic Escalation & Policy Engine

🪪 License

This library is licensed under the MIT License.
See the LICENSE file for details.

👤 Author

Engineered by Mohamed Abdulalim (@megyptm)
Backend Lead & Technical Architect
https://www.maatify.dev

🤝 Contributors

Special thanks to the Maatify.dev engineering team and all open-source contributors.
Contributions are welcome.

_{Built with ❤️ by Maatify.dev — Unified Ecosystem for Modern PHP Libraries}