Read the explanation
The default NLP curriculum selects seven milestone records with estimated hours thirty, fifteen, twenty, thirty five, forty, thirty and thirty. These sum to two hundred. At ten weekly hours the summary ceiling is twenty weeks. The syllabus separately rounds each node up, giving three, two, two, four, four, three and three weeks, totaling twenty one. Bars compare summary twenty and sequential syllabus twenty one at nine pixels per week. The export therefore can describe a schedule extending beyond the headline duration. These are authored learning estimates rather than validated completion guarantees or evidence that a learner mastered the subject. No model assesses proficiency or adapts instruction here. Advanced mathematics changes its foundation hours to zero and statistics to five, while proficient coding changes Python hours to zero. The NLP total becomes one hundred forty, giving fourteen summary weeks at ten weekly hours. The syllabus still allocates at least one week to every node, even zero hour nodes. Its durations become one, one, one, four, four, three and three, totaling seventeen. Bars compare fourteen and seventeen at ten pixels per week. This is a rounding and minimum allocation consequence. The pathway uses the source node array order and filters graph edges for drawing; it does not solve an optimized prerequisite scheduler or verify learner competence. At twenty five weekly hours the default two hundred hours give eight summary weeks. Rounding each milestone separately yields two, one, one, two, two, two and two weeks, totaling twelve. Bars count eight and twelve at fifteen pixels per week. The target month is current time plus summary weeks times seven days, not the final syllabus week. Offline missing D3 throws during graph initialization after controls and downloads bind. Subsequent configuration edits update settings but graph rendering returns early before updating the visible metrics or empty syllabus. Actual JSON and Markdown downloads compute the selected curriculum independently and remain available. Native exports preserve this distinction without supplying the dependency, changing source controls, guaranteeing learning outcomes or claiming public publication.