Week 7: Build the Product Core

This lesson turns the curriculum into product logic. You are defining how the learner moves through the system and where the system applies pressure.

A strong course can still fail as a product if the loop is muddy. If users do not know what to do, what they owe, and what happens next, the product loses force.

Think in states and transitions: visitor, onboarding, active learner, submitted, under review, revise, complete, blocked, capstone-ready.

This lesson focuses on the runtime contract that makes the course feel alive: roadmap generation, progression state, and structured review feedback.

A roadmap without progression is decorative. A review without actionability is noise. A learning runtime without consistency becomes an expensive blog.

Roadmaps set direction, progress tracks commitment, and reviews create corrective pressure. The system becomes useful when these three are bound together.

This lesson defines the operator layer: the minimum admin surface needed to understand learner state, intervene when needed, and keep the platform trustworthy.

Without admin visibility, the product becomes opaque. Without admin restraint, the product becomes dangerous because privileged actions are hard to audit or govern.

Admin is not all-powerful UI. It is an operational control plane with explicit permissions, read models, and audited interventions.