normalize-youtube-comments-public-signals

name	normalize-youtube-comments-public-signals
description	Normalize fetch-youtube-comments results into unified public signals and write them into the signal plane database. Use when investigators need canonical YouTube comment rows, artifact refs, provenance, platform quality flags, and coverage limitations.

Eco Normalize YouTube Comments Public Signals

Core Goal

• Read one fetch-youtube-comments raw artifact.
• Convert comment-thread records into canonical public signals.
• Write normalized rows into the unified signal plane.
• Return compact receipts, artifact refs, signal ids, and query-oriented handoff.

Triggering Conditions

• A fetch step already produced YouTube comments output.
• The council needs canonical public-language comment evidence instead of provider-native payloads.
• Investigator query, finding, and evidence-bundle work should operate from normalized signals.

Read/Write Contract

• Reads one raw artifact from disk.
• Writes normalized rows into normalized_signals in runs/<run_id>/analytics/signal_plane.sqlite.
• Does not generate claim candidates directly.

Required Input

• run_dir
• run_id
• round_id
• artifact_path
• Optional:
  • db_path

Output Contract

• status
• summary
• receipt_id
• batch_id
• artifact_refs
• canonical_ids
• warnings
• board_handoff

References

• ../../docs/openclaw-project-overview.md

Scripts

• scripts/normalize_youtube_comments_public_signals.py