Mid-Build Ethics Checklist
Answer each question honestly. If the answer is 'I don't know' — that is a red flag to address before Week 8.
Privacy
What personal or sensitive data does the agent access? Who explicitly consented to it being used? How is it stored? How long is it retained?
Bias
What training data or assumptions does the agent rely on? Which groups could be systematically disadvantaged by its outputs? Have you tested for this?
Transparency
Can a user understand what the agent did and why? If your agent sends a message or makes a recommendation — can the affected person request an explanation?
Accountability
Who is responsible when the agent makes a mistake? Is that person named in your documentation? Do they have a way to be alerted and override?
Your Project README — Six Required Sections
Start it now. Add to it every session. Your final README is part of the assessed submission.
01
Project name and one-sentence description.
What does this agent do, for whom, in one sentence. If you cannot write this sentence, the project scope is still unclear.
02
The problem being solved.
Two to three sentences. Who has this problem? What currently happens without the agent? Why does it matter?
03
How the agent works
Like a recipe. Input → processing → output. Name every tool called. Name every decision point.
04
Data sources and APIs used.
Name every data source. Note whether it is live or simulated. Note the API terms of service — some prohibit commercial use.
05
Known limitations and edge cases.
What does the agent not handle? What inputs break it? What assumptions is it making?
06
Ethics review.
Privacy, bias, transparency, accountability — each with a named concern and a specific design decision you made to address it.
⚠ Critical: Never Commit API Keys to GitHub
Your .env file contains your API keys. If you commit it to a public GitHub repository, those keys are exposed immediately — bots scan GitHub continuously for credentials. Before pushing: (1) confirm .env is in your .gitignore, (2) run git status and confirm .env is not listed, (3) never hardcode API keys directly in code files, (4) if you have already committed a key — rotate it immediately in your provider dashboard.✏️ Student Reflection
Complete sections 01–04 of your README today. For section 03, write the step-by-step description as if explaining it to someone who has never heard of your project. If you cannot explain it simply, the design is not clear enough yet.📝 Your Lesson Submission
Share your reflection, ask a question, or leave a comment. Your mentor will respond.
🔐
You need to be logged in to submit your reflection.
← Previous6.1 — Building Your First Working Prototype
Next →7.1 — Mentor Mid-Build Feedback Session🔒 Submit reflection to unlock