Authority Research Specialist creates no-outreach opportunities #16

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

What to build

Type: AFK.

Create the Authority Research slice of Weekly Intelligence. It should find safe citation, directory, partner, publication, podcast, resource-page, and citation-cleanup opportunities while stopping before outreach, backlink exchange, paid placement, or commitments.

Acceptance criteria

  • Authority runs produce research items with opportunity type, target URL/domain, Mestra relevance, legitimacy evidence, authority/relevance estimate, assets needed, human action, and risk level.
  • Unsafe or insufficient-evidence opportunities are marked blocked, monitor-only, needs assets, or not relevant as appropriate.
  • Dashboard shows authority opportunities and status counts without outreach automation.
  • Tests are written first for actionable, needs-assets, high-risk, and no-outreach boundary behavior.

Blocked by

None - can start immediately

## What to build Type: AFK. Create the Authority Research slice of Weekly Intelligence. It should find safe citation, directory, partner, publication, podcast, resource-page, and citation-cleanup opportunities while stopping before outreach, backlink exchange, paid placement, or commitments. ## Acceptance criteria - [ ] Authority runs produce research items with opportunity type, target URL/domain, Mestra relevance, legitimacy evidence, authority/relevance estimate, assets needed, human action, and risk level. - [ ] Unsafe or insufficient-evidence opportunities are marked blocked, monitor-only, needs assets, or not relevant as appropriate. - [ ] Dashboard shows authority opportunities and status counts without outreach automation. - [ ] Tests are written first for actionable, needs-assets, high-risk, and no-outreach boundary behavior. ## Blocked by None - can start immediately
Author
Owner

Issue #16 completion audit

Implemented and verified:

  • Added a Postgres-writing Authority Research worker entrypoint, run_authority_research_worker_once.
  • Authority runs read configured queries/sources from the Run Request payload and write normalized authority_opportunity research_items.
  • Research items include opportunity type, target URL/domain, Mestra relevance via why_it_matters, legitimacy evidence via quote_or_summary, authority/relevance estimate, required proof/assets, human action needed, risk level, and evidence source.
  • Relevant opportunities with required assets unavailable become needs_assets instead of actionable.
  • High-risk/unsafe opportunities become blocked_high_risk; irrelevant opportunities become not_relevant; weak source/configuration evidence becomes needs_more_evidence.
  • The worker ignores automated outreach/link-exchange fields and creates no follow-up Run Request, email, outreach, paid placement, or commitment side effect.
  • Existing research dashboard shows authority opportunities, status counts, risk counts, and totals without raw payloads or outreach body text.

Tests run on codex-server:

  • python3 -m unittest tests.test_authority_research_worker tests.test_public_listening_worker tests.test_visibility_worker tests.test_postgres_dashboard tests.test_postgres_schema tests.test_technical_audit_worker
  • Result: 140 tests OK
  • git diff --check: clean
Issue #16 completion audit Implemented and verified: - Added a Postgres-writing Authority Research worker entrypoint, run_authority_research_worker_once. - Authority runs read configured queries/sources from the Run Request payload and write normalized authority_opportunity research_items. - Research items include opportunity type, target URL/domain, Mestra relevance via why_it_matters, legitimacy evidence via quote_or_summary, authority/relevance estimate, required proof/assets, human action needed, risk level, and evidence source. - Relevant opportunities with required assets unavailable become needs_assets instead of actionable. - High-risk/unsafe opportunities become blocked_high_risk; irrelevant opportunities become not_relevant; weak source/configuration evidence becomes needs_more_evidence. - The worker ignores automated outreach/link-exchange fields and creates no follow-up Run Request, email, outreach, paid placement, or commitment side effect. - Existing research dashboard shows authority opportunities, status counts, risk counts, and totals without raw payloads or outreach body text. Tests run on codex-server: - python3 -m unittest tests.test_authority_research_worker tests.test_public_listening_worker tests.test_visibility_worker tests.test_postgres_dashboard tests.test_postgres_schema tests.test_technical_audit_worker - Result: 140 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#16
No description provided.