Agenda Contatos Laravel Package

Product Decisions This Supports

• Admin/CRUD build-vs-buy: This package is an integration layer for MocaBonita, a Laravel admin-panel/CRUD-scaffolding tool. It informs the recurring "do we hand-roll admin screens or scaffold them" decision — relevant to internal tools, back-office, and CRUD-heavy MVPs.
• Support matrix and upgrade planning: v1.2.0 is a compatibility-only release ("adaptado para a versão 3.3.6.10 do MocaBonita"). That tells us the package tracks upstream MocaBonita on a point-version basis, not a range. Every upstream patch may require a corresponding package release — this is a real line item in your maintenance budget and in any SLA you commit to.
• Roadmap dependency check: Before committing admin-panel scope to a milestone, confirm the delivery date is not gated on a third party shipping a MocaBonita compatibility bump. This release is evidence that such bumps are routine, not exceptional.
• Vendor concentration risk: If a meaningful share of your back-office surface depends on MocaBonita, this package is a single point of failure in your dependency graph. That's an input to architecture review, not just a composer.json detail.
• Not a feature decision: There are no new capabilities, deprecations, or API changes in v1.2.0. Nothing here should move a roadmap item, and nothing here should trigger a migration.

When to Consider This Package

Consider it when:

• You are already running MocaBonita (or have standardized on it for pt-BR/Latin American Laravel projects) and need the bridge layer rather than writing it yourself.
• Your admin surface is genuinely CRUD-shaped — entities, forms, listings, permissions — and scaffolding saves weeks versus Filament/Nova/custom Blade.
• Your team is comfortable with a Portuguese-language, Brazil-ecosystem package and its documentation and issue tracker.
• You can pin MocaBonita to 3.3.6.10 (or whatever the package currently supports) and control upgrades on your own cadence.
• The admin panel is internal-facing, where a broken screen is an inconvenience rather than a customer-visible outage.

Look elsewhere when:

• You are not on MocaBonita — this package has no standalone value, and adopting it implies adopting the upstream framework too.
• You need semantic-versioning guarantees or a published compatibility range. The release pattern here is point-to-point coupling; expect to upgrade the two packages in lockstep, forever.
• You need a vendor-neutral, English-first, large-community admin stack. Filament or Laravel Nova carry more documentation, more hiring signal, and less lock-in.
• Your admin panel is customer-facing or revenue-critical, where a transitive dependency's release cadence becomes your incident response plan.
• You require a security disclosure process or CVE history you can point an auditor at. A single-line release note gives you no such evidence.

How to Pitch It (Stakeholders)

To executives: This is a small accelerator for internal admin tooling in our Laravel stack — it saves scaffolding time on back-office screens. The tradeoff is dependency coupling: the package is version-pinned to a specific release of an upstream framework (currently MocaBonita 3.3.6.10), which means routine upstream patches can force coordinated upgrades on our side. Treat it as a tactical time-saver, not a strategic platform bet, and keep it scoped to internal tools. Confidence in this recommendation is low — it rests on a single release note and no prior evaluation, so commission a short spike before it enters a committed milestone.

To engineering: v1.2.0 is a compatibility bump only — no new APIs, no deprecations, no migration work. The signal worth acting on is the pinning model: the package targets an exact MocaBonita point version, so treat the pair as a single unit in your upgrade runbook. Before adoption, verify (a) the current supported MocaBonita version matches what you run or can run, (b) who maintains the package and how quickly compatibility releases ship after upstream changes, and (c) whether your CI pins both packages or floats them — floating either one here is how you get a Friday-afternoon surprise. If any of those checks come back thin, the fallback is straightforward: build the admin surface on Filament and skip the transitive dependency entirely.