Classify one claim as directly observed, source-supported, inference, or unsupported.
Research, Sources, and Career EvidenceTurn one project claim into a traceable source trail and a credible project story.
A polished claim is not automatically credible. Students leave the AI draft, inspect sources, compare independent evidence, label claim strength, and explain what their own project evidence actually demonstrates.
Bring or recreate one project purpose and capability claim from Topic 10, or use the supplied Study Sprint Evidence Trail Lab. No prior packet, public URL, live web, AI account, paid tool, Git history, resume, job application, personal contact detail, or identity evidence is required.
Four outcomes you can demonstrate.
The focus is judgment students can show, not vocabulary they can merely repeat.
Build a source trail that identifies what each source supports and what remains uncertain.
Separate source citation from an accurate account of AI or human assistance.
Map project evidence to selected career competencies without claiming unsupported mastery or impact.
Two meetings with separate learning arcs.
Meeting 1 plans 68 taught minutes plus a 12-minute flex and access buffer; Meeting 2 plans 68 plus 12.
Verify One Project Claim
Relay six synthetic claims through author, verifier, reader and mentor; write the rule each case needed; then turn those rules into one auditable source trail with its disclosure and limit.
- LaunchOne rule, six cases, four roles, one laptop per table.
- Cases 1–2 · the route, the pageWhere an answer actually came from; why a page that vouches for itself settles nothing.
- Cases 3–4 · the citation, the statusWhether a source exists and supports this exact sentence; what a blocked check may and may not change.
- Cases 5–6 · the trail, the limitWhich sentence each source supports; how sentences that are each true add up to a false story.
- Source trailTurn the rules the table wrote into one auditable row plus its disclosure.
- Close · evidence checkpointLeave with one claim, its status, its trail, and its limit.
- Flex/access bufferUse supplied cards, projected/transcript route, paper, or LMS text when live research is unavailable.
Six cases, four roles, one laptop per table. Your table relays one claim through author, verifier, reader and mentor, then writes the rule the case needed. Open it when your instructor names the case; it also works alone.
Open the simulationTurn Evidence into a Credible Project Story
Retrieve the verified claim, analyze human and AI task boundaries, map evidence to selected career competencies from NACE (the National Association of Colleges and Employers), build a calibrated story, practice explanation, and submit a privacy-safe packet.
- Retrieve + task and competency lensesReconnect the source trail, classify task responsibility, and choose one evidence-backed competency.
- Three-round project storyReplace adjectives with evidence, map the claim, and draft a bounded story.
- Explanation practice + privacyUse pair, solo, projected, or written routes and remove unnecessary personal evidence.
- Packet + Topic 12 handoffAssemble five pages and convert one weak sentence into a prompt-strategy target.
- Flex/access bufferComplete missing evidence, use an alternate format, or rehearse privately.
Research and Career Evidence Packet
Verify one exact project claim; build a source trail and lateral-reading record; separate citation from AI-use disclosure; map one evidence-backed career competency; write a calibrated project story; practice explanation; protect privacy; and prepare a Topic 12 prompt-strategy handoff.
What to submit
- Submit one completed packet through the course LMS before Topic 12. Preferred filename: Lastname-Topic11-ResearchCareerEvidence.pdf; maximum five pages. LMS text, DOCX/export, scanned paper, speech-to-text, or an instructor-approved accessible alternative is accepted. The LMS supplies exact deadline and grading-policy details.
- Include one exact claim, its evidence route/status, source identity/date/type, exact support, an additional comparison/repeated run or accurately labeled blocked reason, AI or human assistance disclosure, and a limitation. A blocked check earns full credit when it names what could not be accessed and the next check; keep the claim status calibrated to the evidence you do have and do not upgrade it because a check was blocked.
- Complete the action → artifact → selected NACE competency → human judgment → limitation map, then write one 90–130 word project story that does not claim mastery, measured impact, employment readiness, or production deployment without evidence.
- Record the three-question explanation practice through a partner, private written rehearsal, projected/transcript route, speech-to-text, or approved equivalent. Public speaking and partner disclosure are not required.
- No prior packet, public URL, live web, AI tool, account, paid certificate, Git history, resume, job application, contact detail, code volume, or identity evidence determines core credit.
Core sources and optional extensions.
The class deck contains the required explanation. These links support verification, deeper reading, or alternate access.
Topic 12: Prompt Strategy and Source Boundaries
Carry one weak sentence, its evidence, a non-invention/privacy boundary, and a human evaluation rule into prompt-strategy practice.