The Product Stage is the execution engine of the NBM4 framework. In traditional development, teams often build Minimum Viable Products (MVPs) that are minimally functional but functionally brittle, frustrating early adopters. NBM4 replaces this with the Minimum Lovable Product (MLP).

MVP vs. MLP in NBM4

Characteristic	Traditional MVP	NBM4 Minimum Lovable Product (MLP)
Scope	Broad, shallow feature coverage	Narrow, deep workflow mastery
User Experience	Rough wireframes, acceptable friction	Polished, delightful first-run experience
Architecture	Throwaway code, rapid tech debt	Governed, modular, and extensible core
Success Criterion	“Did the system crash?”	“Did the user achieve their goal effortlessly?”

The Three Pillars of NBM4 Solution Architecture

1. Theme, Epic & User Job Story (UJS) Hierarchy: Break strategic product roadmaps into hierarchical, testable increments where every single engineering commit directly traces to a verified customer job.
2. Defensive Governance & CI Gates: Automate encoding, linting, architecture constraints, and regression testing at the commit boundary.
3. Continuous Verification Protocol: Ensure every shipped capability has automated integration suites and real-world scenario tests before customer release.

Governed Artifacts in the Product Stage

• Product Requirements Documents (PRDs): Scoped technical definitions establishing functional contracts, non-goals, and boundary conditions.
• Architectural Decision Records (ADRs): Version-controlled records of structural, technology, and architectural trade-offs.
• User Job Stories (UJS): Fine-grained execution units paired with explicit acceptance and testing criteria.

Promotion Gate: Transitioning to Stage 04 (Growth)

To graduate an MLP into Stage 04 (Growth & Scale):

• The core customer journey achieves an uninterrupted completion rate >90%.
• Zero P0/P1 architectural blockers or unmitigated security vulnerabilities remain.
• Quantitative retention signals prove that early cohorts return repeatedly without manual intervention.