Give the seed plans canonical CONTENT-WP frontmatter and task blocks, and classify the repo as infotech research so repo-onboard can project it. Assistant: grok Assistant-Session: 01a130f1-abfb-7d71-9cd6-a8b75ec7f95a
2.1 KiB
2.1 KiB
| id | type | title | domain | repo | status | flavor | depends_on | created | updated |
|---|---|---|---|---|---|---|---|---|---|
| CONTENT-WP-0000 | workplan | Upstream baseline and IP audit | infotech | content-explorer | ready | planning | 2026-10-12 | 2026-10-12 |
Upstream baseline and IP audit
Reproduce the OnCo baseline and establish the legal, behavioral, and visual reference. The 2026-10-12 research pass read public files and the live site. It did not clone or execute the upstream repository.
Work packages
Pin an immutable upstream git SHA and preserve the original MIT license and NOTICE.
id: CONTENT-WP-0000-T01
status: todo
priority: high
Install the locked dependencies and record build, test, lint, and typecheck results.
id: CONTENT-WP-0000-T02
status: todo
priority: high
Trace dependencies of the browser, detail, graph, navigation, and data layers.
id: CONTENT-WP-0000-T03
status: todo
priority: high
Capture responsive screenshots and a keyboard interaction walkthrough.
id: CONTENT-WP-0000-T04
status: todo
priority: high
Inventory data, code, logos, artwork, fonts, and external dependency licenses.
id: CONTENT-WP-0000-T05
status: todo
priority: high
Quantify oncology-specific references and decide component-by-component reuse.
id: CONTENT-WP-0000-T06
status: todo
priority: high
Acceptance gates
Commit the pinned SHA, baseline report, and component inventory.
id: CONTENT-WP-0000-T07
status: todo
priority: high
Separate MIT software from the NC dataset and assets in a license matrix.
id: CONTENT-WP-0000-T08
status: todo
priority: high
Capture one reference example each for browse, detail, search, and relations.
id: CONTENT-WP-0000-T09
status: todo
priority: high
Key risk
R1: license/source boundary. R2: unable to reproduce the baseline. Log evidence and deviations in the workplan review before marking complete.
Evidence
Pull requests, test logs, pinned artifacts, screenshots, or a comparison report where applicable. Add ImplementationNotes.md and Review.md on completion. Do not mark a gate passed without a verifiable link.