Final Portfolio Checklist

Use this checklist before submitting the final repository link on Canvas.

Repository Access

• Repository link opens for course staff.
• Private repository access has been granted to course staff when needed.
• Latest commit is synced to GitHub.
• Canvas submission includes the latest commit hash.
• repository-access-note.md records visibility, staff-access status, the checked date, latest commit hash, and final artifact paths.

Project README

• README names the project audience and purpose.
• README explains the folder structure.
• README explains how to render the report.
• README explains how to open or run the KT product.
• README names any required packages or environment setup.

Data And Stewardship

• Data source is cited.
• Access method is documented.
• Data restrictions are stated.
• Privacy and stewardship risks are acknowledged.
• Public repository contains only shareable data and outputs.

Reproducibility

• Paths are relative.
• Report renders from source.
• Figures and tables are generated by code.
• Dashboard-style product opens or runs, or a static preview (screenshot or rendered HTML page) is committed in its place.
• Dependency notes are current.
• Known failures are recorded in the risk list.

Communication

• Final report states the question, data, methods, findings, and limitations.
• KT product is matched to the intended audience.
• Presentation materials align with the final findings.
• Claims are descriptive, predictive, or causal only when justified.

AI Use

• AI-use note lists major AI-assisted tasks.
• Numeric outputs and citations were verified manually.
• AI-generated code was tested.
• AI-generated prose was reviewed for accuracy and tone.

Definition Of Done

• Final repository link submitted on Canvas.
• Commit hash included in Canvas.
• Final report path included in Canvas.
• Dashboard or KT product path included in Canvas.