Assignment 4 · Part 4 · Page 1

Claim inventory and assistance disclosure

Topic 11: verify one exact claim, preserve a traceable source trail, and explain a project without turning polish into proof. Most fields begin in class; use the LMS calendar for the exact deadline, time zone, late rule, and resubmission rule.

Accepted routes
HTML, LMS text, DOCX/export, five-page PDF, scanned paper, speech-to-text, projected/transcript evidence, or approved accessible equivalent.
Equal-credit starting points: own class-safe project, recreated project claim, supplied Study Sprint record, personal/projected Study Sprint run, or paper route. No Topic 10 packet, public URL, live web, AI account, Git history, resume, job application, or external certificate is required.
Directly observedYou personally ran or observed the bounded artifact behavior.
Source-supportedAn identified source or supplied record supports the wording.
InferenceA limited interpretation, labeled as such.
UnsupportedAvailable evidence does not support it.

Blocked is a check condition, not a fifth claim status: name what could not be accessed/performed 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. Use one or two specific sentences per box unless a prompt asks for a list or story.

Privacy boundary: your own name is allowed only in the header and is never draft-saved. Do not enter names inside evidence, private resumes, applications, contact details, grades, health/identity data, consent/assent records, private paths, account/device screens, full chats, restricted files, or unpublished peer work.
Meeting 1 · Page 2

Build a traceable source trail.

Record what each source or artifact directly supports. A citation and an AI-use disclosure answer different questions; include both when both apply.

Citation/source record: where the information came from. Assistance disclosure: how a tool or person shaped your work and what you verified.
Trail fieldYour recordCalibration check
Exact claimOne sentence; no hidden outcome claim.
Source identityAuthor/organization, title, date/access date when live, type/route.
Exact supportParaphrase what the source actually establishes.
Missing evidenceWhat the source/artifact cannot establish.
Additional checkComparison, repeated run, instructor observation, or blocked reason.
Status + decisionKeep, narrow, remove, or investigate.
Blocked additional check: name what could not be accessed or performed and the next check. This can earn full credit. Keep the claim status calibrated to the evidence you do have; do not upgrade it because a check was blocked, and do not invent a title, author, year, statistic, quotation, test result, or access record.
Route-dependent Study Sprint baseline: record-only route → “the supplied record reports 2/20/3” is Source-supported. Personal/projected run → the bounded app behavior is Directly observed. The 35%/Qu & Lee (2025) claim is always Unsupported here. Privacy-safe evidence unit: a short input/action → output transcript, class-safe excerpt, or instructor-observed check inside this packet is enough; do not attach the private archive.
Meeting 1 · Page 3

Leave, investigate, compare, return.

Lateral reading means leaving the original page or draft to investigate source identity and compare independent evidence before returning to the claim.

1 · LEAVEPause the polished page or AI draft.
2 · INVESTIGATEWho is behind the source and why?
3 · COMPAREWhat does independent evidence say?
4 · RETURNWhat exact wording survives?
5 · RECORDStatus, disclosure, and limit.

Research-route decision

QuestionYour answerStatus
Did the task need background knowledge, current web information, or multiple perspectives?
Did I inspect source identity and exact support rather than trusting a summary?
What remains uncertain after the comparison?
No-live-web route: use the course-owned synthetic source cards and identify them as supplied records. Full external lateral-reading lessons, paid assessments, and account-based courses are optional and never core-credit gates.
Meeting 2 · Page 4

Map project evidence to a career lens.

Use one selected NACE competency (NACE is the National Association of Colleges and Employers) as an interpretation lens. A map can show relevant practice; it does not certify mastery, measured impact, employment readiness, or production deployment.

CommunicationExchange information clearly for an audience and purpose.
Critical ThinkingAnalyze needs and make reasoned decisions.
TechnologyUse technology ethically and effectively for a task.
Career + Self-DevelopmentReflect, seek feedback, and identify next growth.

Credible project story · 90–130 words

Evidence pattern: “I [action] to address [bounded purpose]. The [artifact/test/source trail] showed [specific evidence]. I personally [judgment or verification]. [Tool/person] assisted with [material help], and I [accepted/changed/rejected/checked]. This demonstrates practice relevant to [one lens], but it does not establish [limit].” Adapt the pattern; do not copy unsupported language.
Meeting 2 · Page 5

Explain, protect privacy, and hand off to Topic 12.

Practice explanation through a partner, private writing, projected/transcript route, speech-to-text, or approved accessible equivalent. Public speaking and partner disclosure are not required.

Privacy and submission check

Topic 12 prompt-strategy handoff

Complete

Traceable evidence supports the claim, disclosure, career map, limit, and handoff.

Developing

Core work exists, but one evidence link or calibration decision is incomplete.

Incomplete

Polish, access proof, or unsupported outcomes replace the required evidence trail.

Submission boundary: maximum five pages. Submit the packet—not full source archives, private underlying files, public identity proof, access screenshots, or complete AI chats.