Axiom Laravel Package

Product Decisions This Supports

• Market expansion / localization roadmap: The addition of a Vietnamese citizen rule expands the package's country coverage, which directly supports decisions about launching or localizing onboarding flows in Vietnam.
• KYC and onboarding feature scoping: Citizen/National ID validation is a building block for registration, identity capture, and compliance-adjacent flows. This release lets the team scope a Vietnam-specific onboarding requirement without custom validation work.
• Build vs. buy: Rather than maintaining per-country ID format and checksum logic in-house, the package absorbs that maintenance. Decisions about owning vs. depending on country-rule coverage can be made against the package's supported-country list.
• Prioritization of validation coverage: Product can treat supported countries as a coverage matrix and prioritize markets by whether validation is already available versus requiring custom rules or vendor support.
• Use cases: user registration and profile completion, age/identity gating, fraud reduction on signup, form-level validation in Laravel applications, and pre-checks before handing off to a dedicated identity-verification vendor.

When to Consider This Package

Consider adoption when:

• The product is a Laravel/PHP application that needs country-specific National ID / citizen number format validation.
• Vietnam is on or near the roadmap, or the team wants a maintained, extensible set of country rules rather than bespoke regex and checksum code.
• The requirement is format and structural validation at the form/validation layer, integrated with Laravel's validator.
• The team values a small, composable dependency over a full identity platform.

Look elsewhere when:

• The requirement is true identity proofing — document OCR, liveness, government database checks, or regulatory-grade eKYC. A validation rule confirms format plausibility, not that an ID is genuine or belongs to the user.
• The target markets are not covered and cannot be reasonably contributed upstream or extended locally.
• Compliance obligations require certified vendors or audited processes, or the package's maintenance cadence and test coverage are insufficient for a regulated flow.
• You need deep customization of rule behavior that would effectively fork the package.

Release-specific note: v3.2.1 is a patch-level, additive change (one new country rule). It carries low regression risk and no apparent breaking changes, deprecations, or migration work. Treat it as a coverage expansion, not an architectural shift.

How to Pitch It (Stakeholders)

For executives: This is a low-cost enabler for entering the Vietnamese market. It removes the need to hand-build and maintain country-specific ID validation, shortening time-to-launch for localized signup and onboarding. The trade-off to flag is scope: this validates format, not identity — it should sit in front of, not replace, a KYC/verification vendor. The incremental release is small and low-risk; the strategic value is the growing country coverage.

For engineering: The change is additive and patch-versioned — a new Vietnamese citizen rule with no indicated breaking changes. It slots into Laravel's validation layer as a rule, keeping country logic out of application code. Before adoption, confirm dependency health: release cadence, test coverage for the new rule, semver discipline, and whether uncovered markets can be extended locally or contributed upstream. Budget a small spike to verify the Vietnamese rule against representative real-world inputs and edge cases before relying on it in production.