Level 6 · Research preparation teaching kit · Doctoral and independent-research pathway
Open replication laboratory
Use the learner record during the live investigation, then use the instructor guide to facilitate comparison, address misconceptions, and assess evidence-bounded reasoning.
Learner lab record
Portable replication-package release gate
Can an independent team reproduce the apparatus state, raw-data lineage, analysis environment, and declared decision without private clarification?
Setup
Use the replication-package gate. Assemble hardware/sample identity, protocol, calibration, raw data, metadata, code, environment lock, analysis outputs, null/failed runs, and license; test the package from a clean environment.
Predict first
- 1. Predict which missing artifact would most likely prevent an independent rerun.
- 2. Declare what mismatch triggers a package hold rather than an explanatory patch.
| Variable | Role | Unit |
|---|---|---|
| Package artifacts | release inputs | files/records |
| Checksums and environment lock | integrity inputs | hash/version |
| Independent rerun result | dependent | pass/hold |
| Discrepancy classification | adjudication output | category |
Observation columns
Analyze
- 1. Can raw results be regenerated from immutable inputs?
- 2. Are failed and null runs preserved?
- 3. Does the environment lock cover all analysis dependencies?
- 4. Can a discrepancy be localized without changing the preregistered decision?
Conclusion frame
The package passed ___ of ___ gates; independent rerun ___ at artifact ___, classified as ___, so release state is ___ pending ___.
Instructor guide · 80–120 minutes
Teach the investigation, not the interface
Learning target: Researchers turn an exploratory result into a portable, independently executable evidence package that preserves positive, null, and failed outcomes.
Prepare
- • Define the package schema and release license.
- • Provision a clean rerun environment.
- • Prepare one hidden missing dependency and one data-lineage break.
Facilitation moves
- • Do not let the original author operate the independent rerun.
- • Require immutable raw inputs and checksums.
- • Classify discrepancies before changing code or protocol.
Accessibility and participation
- • Provide a machine-readable and human-readable manifest.
- • Use explicit gate labels and remediation owners.
- • Ensure documentation is screen-reader navigable and command examples are copyable.
Evidence of learning
- • A complete immutable manifest
- • A clean-environment rerun
- • A classified discrepancy and release decision
Misconception checks
Publishing analysis code is sufficient for replication.
Hardware/sample identity, calibration, raw data, metadata, environments, decisions, and failures are also required.
A failed independent run proves misconduct or falsity.
It triggers structured discrepancy localization across protocol, apparatus, environment, data, and analysis.
Extension
Run a third-party reproduction using only the public package and publish a versioned discrepancy report.