content-explorer/workplans/CONTENT-WP-0003-ingestion-publishing.md
tegwick 5f8c2d0dae Register content-explorer workplans for State Hub projection.
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
2026-10-12 18:35:28 +02:00

2.1 KiB

id type title domain repo status flavor depends_on created updated
CONTENT-WP-0003 workplan Ingestion, provenance, and publishing infotech content-explorer proposed implementation
CONTENT-WP-0001
2026-10-12 2026-10-12

Ingestion, provenance, and publishing

Turn raw inputs into trustworthy, reproducible snapshots. This gate is required before any externally ingested public content is published. It may proceed in parallel with CONTENT-WP-0002.

Work packages

Implement build-time JSON, NDJSON, and Markdown frontmatter connector APIs.

id: CONTENT-WP-0003-T01
status: todo
priority: high

Make import idempotent with source digests and a connector version.

id: CONTENT-WP-0003-T02
status: todo
priority: high
id: CONTENT-WP-0003-T03
status: todo
priority: high

Model source licenses, citations, and attribution, and quarantine unsupported content.

id: CONTENT-WP-0003-T04
status: todo
priority: high

Generate the snapshot, manifest, and machine-readable and human import reports, and publish atomically.

id: CONTENT-WP-0003-T05
status: todo
priority: high

Acceptance gates

Two connector types produce identical normalized snapshots for equivalent input.

id: CONTENT-WP-0003-T06
status: todo
priority: high

Repeated ingest yields the same content hash.

id: CONTENT-WP-0003-T07
status: todo
priority: high

Every published sourced claim has a retrievable evidence reference.

id: CONTENT-WP-0003-T08
status: todo
priority: high

Rights violations prevent publication.

id: CONTENT-WP-0003-T09
status: todo
priority: high

Key risk

R5: rights metadata missing. Quarantine instead of guessing. 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.