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
1.8 KiB
1.8 KiB
| id | type | title | domain | repo | status | flavor | depends_on | created | updated | |
|---|---|---|---|---|---|---|---|---|---|---|
| CONTENT-WP-0006 | workplan | Extensibility and first real-world pilot | infotech | content-explorer | proposed | implementation |
|
2026-10-12 | 2026-10-12 |
Extensibility and first real-world pilot
Attach an independently maintained knowledge source and validate user value.
Work packages
Implement a third connector, GitHub issues or Wikidata, after a rights and rate review.
id: CONTENT-WP-0006-T01
status: todo
priority: high
Provide a connector authoring template with fixture-based certification tests.
id: CONTENT-WP-0006-T02
status: todo
priority: high
Pilot one non-medical infospace with real users.
id: CONTENT-WP-0006-T03
status: todo
priority: high
Prioritize API, JSON-LD, MCP, and ask enhancements from observed needs.
id: CONTENT-WP-0006-T04
status: todo
priority: high
Define long-term update and governance responsibilities.
id: CONTENT-WP-0006-T05
status: todo
priority: high
Acceptance gates
The third connector is refreshable and auditable.
id: CONTENT-WP-0006-T06
status: todo
priority: high
The pilot uses no hardcoded kinds in the UI.
id: CONTENT-WP-0006-T07
status: todo
priority: high
Document an informed go or no-go for dynamic deployment and a search backend.
id: CONTENT-WP-0006-T08
status: todo
priority: high
Key risk
R8: third-party API policies and data quality. 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.