6. Change lab and meeting rehearsal
Prove that you can navigate the code and explain the project. Prepare for the 18 October 2026 director and procurement meeting.
Your capstone source trace
- Choose the Save & Submit action. Find its component, command shape, and API route.
- Write down where required fields, Final Results currency, and outcome are checked.
- Follow saveCommands through execute and the workflow handler. Identify when validation and received copies are captured.
- Identify the transaction that saves the snapshot, index, notifications, and touch state.
- Find the unit tests and browser journey that cover this behavior.
- Explain what happens on network retry, stale version, missing permission, and unresolved defect map.
Reference answer
Start with workspace-finish-actions/use-finish-flow, the provider, and command-schema. The review POST route supplies the server actor/time. saveCommands checks request replay and database version. execute checks review access and dispatches the handler. Workflow functions enforce state, role, required inputs, and current computation. review-store appends transactional rows. Conflict recovery replaces local state with the server copy. New non-drop senior routing still reaches PEC_ROUTING_PENDING.
Read the exact functions to refine this trace. Use workspace file notes, domain file notes, command tests, and browser journey.
A safe first change exercise
Plan a help-text change to explain why Final Results are stale. Do this in a disposable branch or checkout. This lesson does not ask you to change policy or apply database scripts.
- Find the current validation message and the UI that displays it. Decide whether the problem is wording or a missing state check.
- Write a concrete before/after behavior. Example: after saving changed income, the user sees a message telling them to apply Final Results.
- Change one display message. Keep the calculation, state transitions, and permission checks unchanged.
- Run typecheck, lint, format, and the existing relevant validation/UI checks. For a text-only change, do not add a test that only repeats the string.
- Review the diff. Explain the scope and its limits. Update the relevant wiki section if behavior changes.
- Discard the exercise or have another developer review it before merging.
Five-minute meeting pitch
| Time | What to say | What to show |
|---|---|---|
| 0:00 to 0:45 | We propose one internal review workspace for about 41 staff. It should connect evidence, calculations, approvals, and reporting. | One review and the intended lifecycle. |
| 0:45 to 2:15 | This synthetic demo lets staff test the process and gives engineers a concrete reference. | Find work, edit a computation, save, and explain current-result checks. |
| 2:15 to 3:00 | The real app will be a new agency-hosted build. We will review any reused code. Current non-drop routing and downstream contracts need owner decisions. | Readiness boundaries. |
| 3:00 to 4:15 | We need internal staff capacity, policy decisions, and a secure hosting owner. The first approval is a short discovery stage with deliverables. | Staff effort and cost model. |
| 4:15 to 5:00 | At each gate management can continue, narrow scope, or stop. The first operational release is SNAP Negative. Other programs use the shared platform later. | Stages and gates. |
Rehearsal questions and answer key
| Question | A defensible short answer |
|---|---|
| Why rebuild if this looks complete? | The demo resolves UX and requirement questions. SPII operation needs a supported architecture, agency identity, records controls, receiving-system proof, and independent acceptance. |
| Why internal staff? | We retain ownership and use approved agency services. The plan still needs named staff time and two trained maintainers. |
| Is it only 41 licenses? | There are about 41 users. Internal hosting avoids assuming per-user SaaS. Support, assurance, integration, and staff opportunity cost remain. |
| What is the estimate? | The proposed initial pilot is 88 person-weeks over 26 delivery weeks, with a planning labor value of $264k to $440k before contingency. Discovery must replace those assumptions. |
| Can all programs go live together? | First prove one complete SNAP Negative workflow. Add other programs after their source, rule, document, and output contracts are approved. |
| What do you need on October 18? | A sponsor, a capped discovery allocation, named internal staff/SMEs, and an agency hosting/security review owner. |
| What is the largest current functional blocker? | The Review-tab defect map controls non-drop routing and memo classification. Management must approve its code-to-action mapping. |
| How do we prevent harm from incorrect rules? | Independent policy-owned expected cases, versioned rules, signed acceptance, restricted release, and reconciliation with the legacy process. |
| What if you leave? | An agency repository, two maintainers, review rules, runbooks, and a handover drill. The proposer is a product/domain lead, not the only support path. |
Readiness self-check
Score each course completion item 0 if you cannot explain it, 1 if you need notes, or 2 if you can explain it and locate evidence. There are eight items, so the maximum is 16. Aim for 14 or more and no zero on authorization, demo limits, or the funding ask. This is a study aid, not a competence certification.
Continue with the meeting brief and full FAQ.