Turn the build into evidence

Document the system, review the integrated path and show what changed on a real branch.

Today’s outcome

Leave with a diff, a passing or meaningful red test and an explanation another student can follow.

Scrum evidenceTechnical reviewDocumentation

Embedded practice

45-minute team tool

Run the check-in, confirm dependencies, continue a real branch and close with code evidence.

Attach visible source, date, limitation and confirmation information to every supported answer.

Create repeatable evidence that the first journey works, fails safely and remains safe after future changes.

Nisa may explain reviewed public information. It must not decide a personal case, inspect a private record or collect identifying data.