Core Laravel Package

Product Decisions This Supports

• Claim-governance rules: The package now enforces that a seat can only claim a task_claim when it is not parked and is within its developer's assignment hours. This turns "who is allowed to pick up work" into a first-class, policy-enforced behavior rather than application-layer convention.
• Feature scoping / roadmap: This is the kind of capability that lets us defer building a bespoke validation layer for dispatch workflows. It directly supports roadmap items around labor scheduling compliance, seat availability, and task distribution integrity.
• Build vs. buy: For products with a "seat claims task" model (contact-center routing, field-service dispatch, internal ticketing, on-call rotation), this package replaces custom claim-validation logic with a maintained abstraction — a favorable buy decision at 0.x scale.
• API contract and UX decisions: The structured 422 with a named rule gives us a reliable signal for front-end behavior — disable claim buttons for parked/off-shift seats, surface precise error messaging, and avoid optimistic-UI rollback complexity.
• Operational policy decisions: Product can now express rules like "parked seats cannot take new work" and "work cannot be claimed outside assignment hours" as configuration/enforcement rather than as manual process or after-the-fact reconciliation.

When to Consider This Package

Adopt when:

• You already model seats (agents, resources, workers) and task claims — the package's domain vocabulary must match yours.
• You need policy enforcement at claim time, not retrospective auditing.
• You want machine-readable validation errors (task_claim, named rule) for client integration and observability.
• Your stack is Laravel/PHP and you prefer composing focused packages over building dispatch semantics in-house.

Look elsewhere when:

• You need general-purpose queueing (use Laravel Queues/Horizon) or cron-style scheduling — this is claim-policy, not execution infrastructure.
• Your labor rules are more complex than parking + assignment hours (e.g., skills matrices, capacity weighting, multi-tier escalation); the current rule surface is narrow.
• You cannot tolerate pre-1.0 churn: at v0.8.x, breaking changes remain plausible; pin versions and gate upgrades behind tests.
• You have no existing seat/claim model — the adoption cost of reshaping your domain likely exceeds the benefit.

How to Pitch It (Stakeholders)

To executives: This release closes a real operational gap — work can no longer be claimed by unavailable resources (parked seats or staff outside their assigned hours). That means fewer mis-assignments, cleaner SLA adherence, and less manual cleanup, at essentially no incremental build cost since it's handled inside an existing dependency.

To engineering: Claim validation is now centralized and returns a well-defined 422 task_claim response naming the violated rule, so we can delete ad-hoc guards in our controllers and build precise client-side handling. It's a small, focused change with a clear contract. Caveat: the package is still pre-1.0, so we pin the version and verify behavior in staging before rollout.