You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
013-OD-AACR already lists this under what is still open: "IS-START curriculum is seeded but thin — the onboarding path is not authored." Filing it so it is trackable alongside the platform defects, because it is a different class of problem and will outlive all of them.
The gap
A member who signs in today lands on /home/panel and sees course cards and counts. There is no stated first step, no order, and no definition of what finishing means. IS-START exists as a course code with seeded resources rather than as an authored onboarding sequence.
Why it belongs on the same list as the bugs
The empty-lesson defect (#43) is why members currently say they cannot access the course. This is why, once that is fixed, they will still not know what to do. Fixing #43 alone converts a broken product into an aimless one — the difference matters when the whole cohort is in beta and forming its first impression.
It is also the one item on the current defect list that no code change can close.
Proposed scope
Author IS-START as a real sequence: what to do first, in what order, what done looks like at each step, and what the member should be able to do at the end.
Replace the placeholder courses with pilot content.
Item 2 has a platform dependency. Items 1 and 3 are content work and do not.
Verification
Hand the platform to somebody who has never seen it, say nothing, and watch. If they ask "what do I do now" at any point, that point is the finding.
Circle status: GitHub leg only. No bd binary on my machine and .beads/ is gitignored, so the bead and Plane LEARN cross-refs need adding by someone with those tools.
013-OD-AACRalready lists this under what is still open: "IS-STARTcurriculum is seeded but thin — the onboarding path is not authored." Filing it so it is trackable alongside the platform defects, because it is a different class of problem and will outlive all of them.The gap
A member who signs in today lands on
/home/paneland sees course cards and counts. There is no stated first step, no order, and no definition of what finishing means.IS-STARTexists as a course code with seeded resources rather than as an authored onboarding sequence.Why it belongs on the same list as the bugs
The empty-lesson defect (#43) is why members currently say they cannot access the course. This is why, once that is fixed, they will still not know what to do. Fixing #43 alone converts a broken product into an aimless one — the difference matters when the whole cohort is in beta and forming its first impression.
It is also the one item on the current defect list that no code change can close.
Proposed scope
IS-STARTas a real sequence: what to do first, in what order, what done looks like at each step, and what the member should be able to do at the end.Item 2 has a platform dependency. Items 1 and 3 are content work and do not.
Verification
Hand the platform to somebody who has never seen it, say nothing, and watch. If they ask "what do I do now" at any point, that point is the finding.
Circle status: GitHub leg only. No
bdbinary on my machine and.beads/is gitignored, so the bead and Plane LEARN cross-refs need adding by someone with those tools.