Why a project score changes
Read the explanation
The exact saved representative fixture returns score eighty-nine. It bypasses the generic incubation base eighty-five plus four for team size at least three and three for timeline at least six, which would otherwise sum ninety-two. Bars use five pixels per assigned score point. This is a programmed label, not a validated readiness probability. Named campus services and availability are unverified. Outside that exact fixture, an incubation team of at least three gets four points. A five-week timeline receives minus two, giving eighty-seven. A six-week timeline receives plus three, giving ninety-two. The threshold therefore adds five points; bars share five pixels per point. The source does not demonstrate that an extra week causes this change in real project success. A non-fixture hackathon sprint starts at ninety-two. Team size at least three and timeline at least six add four and three, yielding ninety-nine before clamping. The code caps this at ninety-six, so three assigned points are removed. Both bars use five pixels per point. Full raw native brief, original reset, tool allocation, four-width resize and first-footer placement preserve the existing project planner.