Devtools Laravel Package

Product Decisions This Supports

• Developer experience and onboarding: DevTools can reduce time to first working SeviaFlow resource by discovering Eloquent models and generating Resources, which supports decisions about onboarding investment and internal enablement.
• Build vs. buy / internal tooling: Because it is MIT-licensed, free-edition, require-dev tooling, teams can avoid building custom Artisan commands for model discovery, status checks, and resource scaffolding.
• Safe resource generation: Built-in safeguards against exposing sensitive model fields support product and security decisions around default-safe scaffolding and review workflows.
• Roadmap and platform fit: The beta targets Laravel 12/PHP 8.2+ and Laravel 13/PHP 8.3+, informing platform-upgrade planning and whether SeviaFlow tooling fits the current stack.
• Adoption scope: DevTools depends on SeviaFlow Core but not the UI or API packages, so it can support backend/API-oriented SeviaFlow projects without requiring the full UI stack.

When to Consider This Package

Consider DevTools when:

• The product is already using SeviaFlow Core and the team wants development-time Artisan tooling.
• Engineers need faster Eloquent model and Resource discovery, resource generation, or application status inspection.
• The stack is Laravel 12 with PHP 8.2+ or Laravel 13 with PHP 8.3+.
• The package can be installed as a dev-only dependency and is not needed in production runtime.
• The team is comfortable adopting a beta package where APIs and compatibility may change.

Look elsewhere or defer when:

• The project is not on SeviaFlow.
• The project requires Laravel 11 or PostgreSQL support as verified targets.
• Production stability and long-term API guarantees are required immediately.
• The organization cannot accept beta-stage tooling in developer workflows.

How to Pitch It (Stakeholders)

For executives: SeviaFlow DevTools is a free, MIT-licensed developer productivity package for SeviaFlow projects. It is dev-only, low operational risk, and aimed at reducing engineering time spent on model discovery, resource scaffolding, and app inspection. The main caveat is that this is a beta release, so compatibility and APIs may change.

For engineering: Adopt it as a require-dev dependency on Laravel 12/PHP 8.2+ or Laravel 13/PHP 8.3+ SeviaFlow Core projects. It adds Artisan tooling for discovering Eloquent models, generating Resources with safeguards against sensitive fields, and inspecting application status. Do not treat it as production runtime infrastructure, and validate behavior carefully on Laravel 11 or PostgreSQL since those are not verified beta targets.