Common Laravel Package

Product Decisions This Supports

• Build vs. buy for the content domain. amethyst/common is a compact reference implementation of a PHP CMS core — entities, repository contracts, service-container wiring, module registration. Reading it sharpens the build estimate for our own content service and gives us a concrete comparison point against SaaS CMS and Laravel-native alternatives (Filament + custom models, Statamic, Craft).
• Architecture direction. It demonstrates contract-first design (interfaces + repository pattern + service providers) that maps cleanly onto Laravel idioms, making it useful input to decisions about domain boundaries, plugin/extension hooks, and how much of the content layer we own versus delegate to a vendor.
• Roadmap scoping for content-platform work. Supports use-case definition for a headless content API, multi-tenant content core, back-office content store, and an extensible module model — as a pattern source, not as a dependency.
• Estimate de-risking. A one-week spike against this codebase buys better accuracy on the content epic without adding supply-chain exposure.
• Decisions it should not drive: vendor shortlisting, production content-backend selection, or anything requiring SLAs, security patching, or long-term maintenance. The adoption signal (1 star, 0 dependents, score 0.035) is too weak to carry operational weight.

When to Consider This Package

Consider it when:

• You want a small, MIT-licensed reference for a PHP content core to benchmark your own domain model, or to lift specific patterns (contracts, repositories, module service providers) rather than the runtime.
• You are running a time-boxed architecture spike and can vendor/pin the code, own the fork, and accept full maintenance.
• Your engineers are already fluent in Laravel-adjacent patterns (Illuminate container, Eloquent-style repositories) and want a small surface to study.
• The evaluation is architectural, not operational — no customer-facing SLA, no regulated data, no support expectation.

Look elsewhere when:

• You need production support, security advisories, regular releases, or an active maintainer community. With 1 star, 0 dependents and a 0.035 score, none of that exists.
• You need a full CMS — mature options (Craft, Statamic, Drupal, WordPress) or a Laravel-native stack will outperform a low-adoption core.
• You need a proven headless content API; a maintained Laravel package or commodity SaaS beats an unmaintained core on every operational axis.
• Your team is Laravel-standardized and would rather not absorb a parallel framework's idioms.
• Audit or compliance requirements demand a documented CVE history or a support contract for every third-party line.

How to Pitch It (Stakeholders)

To executives: "This is a small, MIT-licensed PHP content-core package. It is not a vendor we can rely on — one star, zero dependent projects, no visible maintenance runway — so I am not recommending it as a dependency. I am recommending we use it as a free design reference: it shows how a modular content platform is assembled (contracts, repositories, module registration) for roughly the cost of a one-week architecture spike. That de-risks our own build estimate for the content service without adding a supply-chain liability. License is clean — permissive MIT, no copyleft exposure — but adoption is effectively zero, so any runtime use would need a named internal owner and a funded maintenance line."

To engineering: "Treat amethyst/common as a reading assignment, not a dependency. It is a compact example of contract-first PHP design on Illuminate components — useful for shaping our domain interfaces and module boundaries. If we decide to reuse code, we vendor a pinned fork, own the upgrade path, and budget for it explicitly. Default position: pattern extraction, zero runtime dependency."

To product/roadmap: "No roadmap item should depend on this package. Its value is estimate accuracy on the content-platform epic — it lets us sharpen the build-vs-buy analysis and the domain-model section of the spec without committing to an unsupported library."