Parent: #29
Why
The current v0.1 checkpoint ends with a demo-week checkpoint. Contributors need a concrete package format for showing shipped code, pilot results, public writing/media, and research progress.
Contributor Context
- Contributor onboarding context
- Demo day package: presentation, demo, output summary, motivation, research progress, shipped implementation or content
Scope
- Define a Workstream demo-day package template.
- Include shipped issue/PR links, tests/evidence, pilot metrics, research problem, public article/media links, lessons learned, and next-phase roadmap.
- Add maintainer review rubric aligned to shipping, research maturity, reliability, quality, and public contribution.
Acceptance Criteria
- Contributors can assemble a demo package without private instructions.
- Package supports both technical and ops/research contributors.
- Maintainer can use the package for the 3-month continuation decision.
Contributor Fit
Good docs/ops task that turns Workstream work into public proof of contribution.
Parent: #29
Why
The current v0.1 checkpoint ends with a demo-week checkpoint. Contributors need a concrete package format for showing shipped code, pilot results, public writing/media, and research progress.
Contributor Context
Scope
Acceptance Criteria
Contributor Fit
Good docs/ops task that turns Workstream work into public proof of contribution.