Godfather Laravel Package

Product Decisions This Supports

• Build vs. buy: Treat pugx/godfather as a reference implementation of the Strategy pattern, not a strategic dependency. For new product work, the better decision is usually to build a small internal strategy registry in modern PHP/Symfony rather than adopt a 2014-era package.
• Feature architecture: Supports decisions around pluggable business rules where multiple algorithms must be selected at runtime — e.g. pricing, discount eligibility, shipping-cost calculation, tax rules, payment routing, or content-ranking variants.
• Roadmap prioritization: Useful when deciding whether to invest in a reusable “strategy” abstraction for multiple upcoming features versus hard-coding each workflow. If only one or two variants exist, the abstraction is likely premature.
• Legacy modernization: Relevant only if the roadmap includes maintaining or extending a Symfony2/PHP 5-era application. In that context, it may reduce bespoke wiring for tagged strategy services.
• Vendor and maintenance risk: Signals a clear recommendation to avoid adding an unmaintained, low-adoption dependency to new product surfaces; use the pattern, not the package, unless constrained by legacy architecture.

When to Consider This Package

• Consider only when: you are working in an existing Symfony2 application, need tagged-service strategy selection, and have accepted the maintenance burden of a package last released in 2014.
• Strong fit criteria: legacy Symfony2 DI conventions, simple strategy resolution needs, MIT license compatibility, and a team able to vendor/fork the code if necessary.
• Look elsewhere when: the product runs on modern PHP or Symfony versions, requires security maintenance, long-term support, active community, documentation, or compatibility guarantees.
• Prefer an internal implementation when: the strategy behavior is core to the product, the selection rules are likely to evolve, or the team needs observability, testing hooks, and configuration tailored to the domain.
• Avoid when: you need a full rules engine, workflow orchestration, feature-flag platform, or runtime configuration system. This package is a narrow pattern helper, not a product platform.
• Adoption gate: require engineering review of PHP/Symfony compatibility, a fork-and-own plan, and an exit strategy before using it in any revenue-critical path.

How to Pitch It (Stakeholders)

pugx/godfather is a small MIT-licensed Strategy-pattern helper for PHP/Symfony2. It can make interchangeable business algorithms — such as pricing, shipping, or routing rules — easier to plug into an application. However, it was last released in 2014, has very low adoption, and targets Symfony2, so it is not a safe dependency for new product investment. The recommended pitch is: we will use the architectural pattern, not the package — implement a lightweight internal strategy registry in our current stack, keep selection rules testable and observable, and avoid locking the roadmap to an unmaintained library. Revisit the package only for a constrained legacy Symfony2 maintenance effort, with a clear fork-and-own plan.