Reddit/Public Listening Specialist creates safe research items #15

Closed
opened 2026-05-28 18:14:47 +01:00 by bingoss · 1 comment
Owner

What to build

Type: AFK.

Create the Reddit/Public Listening Research slice of Weekly Intelligence. It should find relevant public conversations and produce safe human-use opportunities only; it must not post, comment, vote, DM, scrape private spaces, or run outreach.

Acceptance criteria

  • Public-listening runs produce research items with URL, community, title, safe summary or quote, Mestra relevance, topic/intent match, risk level, and evidence source.
  • High-risk, irrelevant, or insufficient-evidence items are marked with the correct status instead of becoming actionable.
  • Dashboard shows public-listening items and risk/status counts without raw unsafe payloads.
  • Tests are written first for actionable, monitor-only, high-risk, and no-posting boundary behavior.

Blocked by

None - can start immediately

## What to build Type: AFK. Create the Reddit/Public Listening Research slice of Weekly Intelligence. It should find relevant public conversations and produce safe human-use opportunities only; it must not post, comment, vote, DM, scrape private spaces, or run outreach. ## Acceptance criteria - [ ] Public-listening runs produce research items with URL, community, title, safe summary or quote, Mestra relevance, topic/intent match, risk level, and evidence source. - [ ] High-risk, irrelevant, or insufficient-evidence items are marked with the correct status instead of becoming actionable. - [ ] Dashboard shows public-listening items and risk/status counts without raw unsafe payloads. - [ ] Tests are written first for actionable, monitor-only, high-risk, and no-posting boundary behavior. ## Blocked by None - can start immediately
Author
Owner

Issue #15 completion audit

Implemented and verified:

  • Added a Postgres-writing Reddit/Public Listening worker entrypoint, run_public_listening_worker_once.
  • Public-listening runs read configured queries/sources from the Run Request payload and write normalized reddit_public_listening research_items.
  • Research items include public URL, community, title, safe quote/summary, Mestra relevance via why_it_matters, topic/intent match, risk level, suggested human response angle, and evidence source.
  • High-risk items are blocked_high_risk, irrelevant items are not_relevant, weak/missing evidence becomes needs_more_evidence, and relevant items without safe response guidance become monitor_only instead of actionable.
  • The worker stores raw source payloads only in raw_provider_payloads and dashboard output remains normalized.
  • No posting, commenting, voting, DM, outreach, or follow-up run is created; source-supplied automated action fields are ignored.
  • Existing research dashboard shows public-listening rows, status counts, risk counts, and totals without raw unsafe payloads.

Tests run on codex-server:

  • python3 -m unittest tests.test_public_listening_worker tests.test_visibility_worker tests.test_postgres_dashboard tests.test_postgres_schema tests.test_technical_audit_worker
  • Result: 136 tests OK
  • git diff --check: clean
Issue #15 completion audit Implemented and verified: - Added a Postgres-writing Reddit/Public Listening worker entrypoint, run_public_listening_worker_once. - Public-listening runs read configured queries/sources from the Run Request payload and write normalized reddit_public_listening research_items. - Research items include public URL, community, title, safe quote/summary, Mestra relevance via why_it_matters, topic/intent match, risk level, suggested human response angle, and evidence source. - High-risk items are blocked_high_risk, irrelevant items are not_relevant, weak/missing evidence becomes needs_more_evidence, and relevant items without safe response guidance become monitor_only instead of actionable. - The worker stores raw source payloads only in raw_provider_payloads and dashboard output remains normalized. - No posting, commenting, voting, DM, outreach, or follow-up run is created; source-supplied automated action fields are ignored. - Existing research dashboard shows public-listening rows, status counts, risk counts, and totals without raw unsafe payloads. Tests run on codex-server: - python3 -m unittest tests.test_public_listening_worker tests.test_visibility_worker tests.test_postgres_dashboard tests.test_postgres_schema tests.test_technical_audit_worker - Result: 136 tests OK - git diff --check: clean
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
bingoss/owned-growth-engine#15
No description provided.