Harbor Coffee
Progress: unstarted
No next question chosen.
Return to this capstonePractical systems modeling
Keep the question connected to the behavior someone can inspect.
This worked pantry example reveals the final records. It does not complete your exercise.
Roles alone do not prove activity during a period. This fictional report counts the people collecting food, not everyone in their households.
V1: volunteered September 14. D1 and D4: collected for H1 on September 14 and 18. Noor confirms that these records refer to the same Ana; a matching name alone would not establish identity.
Ana: V1. Ben: V2, V3. Two distinct people across three recorded activities.
Ana: D1, D4. Cora: D2. Dev: D3. Repeat collections do not create new people.
H1: D1, D4. H2: D2. H3: D3. Four distributions served three households.
Ana appears in both groups. Combine Ana, Ben, Cora, and Dev once each. Adding 2 volunteers to 3 recipients would count Ana twice.
Leaving Ana out of a role she performed understates activity. Assigning Ben a recipient role unsupported by these records overstates it. Errors like these can lead to audit failure. This exercise demonstrates traceable counts; it does not certify audit compliance.
Reading a room or example is exploration. A completed capstone includes your own evidence-linked revision. Free-text reflection is preserved without automated grading.
Progress: unstarted
No next question chosen.
Return to this capstoneProgress: unstarted
No next question chosen.
Return to this capstoneNo interactive notes loaded.
What is the purpose? Which identities must stay stable? What happened, and when? Which claims have sources? What does the new evidence change? What should we confirm with the people doing the work?
An engineer and AI need the same explicit story. Keep the sources and context with the model so speed does not erase the reasons behind the design.