PrerequisitesApproved question and pre-analysis plan.Completed lab artifacts and claim ledger.Resolved authorization, privacy, safety, and license gates.
Builds on
Approved question and pre-analysis plan. · Completed lab artifacts and claim ledger. · Resolved authorization, privacy, safety, and license gates.
Investigates
What would make the result worth trusting?
Feeds
L08 capstone evidence release.
02
Before class
Arrive with a prepared artifact
Reading route
Student-specific primary set from PAPER-01–PAPER-42 plus relevant academic, repository, platform, standards, and methods sources.
Viewing route
Open the complete text-first lecture packageFive-minute defense format and release-gate briefing. The current equivalent is notes, slide script, worked case, and no-video transcript; no recording is claimed.
Readiness check
Run the release checklist and resolve all P0/P1 findings.
Bring
Release candidate with checksum manifest.
03
Explanation
Concepts, assumptions, and boundary
A result is a traceability network
The capstone is evaluated as a chain from research question and estimand through sources, query/data manifests, code, observations, analysis, figures, claims, limitations, and decisions. Each headline claim must resolve to an observation and an exact analysis artifact. Negative results, exclusions, deviations, and failed reproductions remain in the release. A beautiful figure cannot repair a broken evidence edge, and a significant estimate cannot repair unauthorized collection.
Defense is part of the method
The eight-minute presentation states the question, design, primary result, uncertainty, strongest limitation, and decision. Seven minutes of questions test evidence lineage, alternative explanations, safety, and generalization. The 48-hour revision is not cosmetic: the learner writes a response note, weakens or removes at least one claim if evidence demands it, and regenerates checksums and provenance. The final version is a bounded release, not a universal GEO recipe.
Figure design. Rows are headline claims; columns are source, data/query record, code, result, figure, limitation, reviewer status, and checksum. Broken edges are visibly blocked. Eight required artifact links are shown for each claim. A broken edge blocks release.Long description
Every public claim maps across a matrix to the files and decisions needed to inspect it. Missing evidence is labeled “release blocked,” while non-redistributable dependencies point to lawful retrieval instructions and hashes.
05
Interactive check
One action, one feedback state
Action
Use reviewer mode to walk from each claim to source, observation, code, result, and limitation.
Feedback
Broken, stale, unauthorized, or circular edges block release and name the corrective action.
Accessible alternative
The same release check is available as a command-line validator and printable matrix.