Think like a junior engineer in a review with senior engineers. You are expected to make the decision, but the board will coach you until the reasoning is strong enough to own.
Signals help you navigate the review. They are not an autonomous course grade.
The board will use your team's evidence and coach you through one engineering move at a time. You may ask questions before you make a decision.
Early reviews may include substantial coaching. Over the semester, the board will expect more independent engineering reasoning.
Your conversations are individual, but every review remains tied to the same frozen team evidence used at that moment.
Team membership and repository evidence are shared. Your coaching conversations and learning state remain individual.
This is your team's evidence workspace for the current released phase. File names are clues, not proof: the Studio also considers equivalent evidence, GitHub workflow history, and project-specific artifacts that actually support the engineering claim.
Surface where teams need attention, what evidence is weak, and which reasoning moves remain implicit—without reducing students to activity counts.
Token and latency telemetry will appear as reviews run. Cost estimates use a versioned OpenAI public rate card and are advisory.
Repository connection, shared evidence state, phase readiness, and student review participation.
Add, deactivate, or move students without rewriting historical team membership.
Team evidence is shared; student conversations are private to the individual and authorized teaching staff.
Inspect FACT observations, REVIEW interpretations, provenance, disputes, and phase-to-phase changes.
Usage telemetry is operational intelligence, not student evaluation.
Start from the COMP 330 lifecycle template, then adjust each section independently as the semester changes.
Create each semester once, then add one or more sections. Sections inherit the COMP 330 lifecycle template but keep independent rosters, teams, review availability, and date overrides.
Import the Sakai gradebook CSV. Only Student ID and Name are used.
Create teams, then assign or move students. Changes preserve membership history.
Dates are proposed from the COMP 330 lifecycle template. Each section may override availability, due dates, and release state independently. Sakai remains the course deadline authority.
Add instructors, TAs, or reviewers by institutional email. Authentication and authorization remain separate.
Archiving preserves all historical reviews, evidence snapshots, team membership, and usage records. It does not delete them.