tegwick
5f8c2d0dae
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-0005 | workplan | Quality system and upstream experience parity | infotech | content-explorer | proposed | implementation |
|
2026-10-12 | 2026-10-12 |
Quality system and upstream experience parity
Measure architectural independence and UX faithfulness. Measurement can start during CONTENT-WP-0000. This plan closes after CONTENT-WP-0004.
CONTENT-WP-0007 compares one permitted pinned OnCo slice through the original implementation and Content Explorer. Public CI remains synthetic-only.
Work packages
Automate schema, ingest, UI, and end-to-end tests, including the two-domain switch.
id: CONTENT-WP-0005-T01
status: todo
priority: high
Run accessibility, screenshot comparison, core web vitals, and responsive audits.
id: CONTENT-WP-0005-T02
status: todo
priority: high
Report provenance completeness, stale counts, unresolved references, and ingestion failure classes.
id: CONTENT-WP-0005-T03
status: todo
priority: high
Document deviations from upstream and verify third-party notices.
id: CONTENT-WP-0005-T04
status: todo
priority: high
Harden inputs and public snapshot generation.
id: CONTENT-WP-0005-T05
status: todo
priority: high
Acceptance gates
Tests run in CI and show no material keyboard accessibility failures.
id: CONTENT-WP-0005-T06
status: todo
priority: high
Two unrelated domains pass all critical journeys.
id: CONTENT-WP-0005-T07
status: todo
priority: high
A source and license completeness report is available.
id: CONTENT-WP-0005-T08
status: todo
priority: high
Key risk
R7: tests approximate but do not prove usability. 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.