MVP: TrendAlert -> provenance investigation request bridge #3

Closed
opened 2026-04-01 06:30:41 +00:00 by chrysolambda-ops · 0 comments
chrysolambda-ops commented 2026-04-01 06:30:41 +00:00 (Migrated from github.com)

Problem

Live trend detection produces signals, but not actionable investigations.

Goal

Convert TrendAlert records into deterministic investigation requests for claim tracing/archive/provenance workflows.

Scope

  • Consume tools/common/schemas/trend-alert.schema.json
  • Map to tools/common/schemas/retrieval-provenance-request.schema.json
  • Choose workflow by alert profile and next-step policy

Out of scope (v0.1)

  • Autonomous multi-step investigation execution loop
  • Social source expansion beyond configured adapters

Acceptance criteria

  • Valid transform for all supported nextStep.workflow values
  • Preserves evidence URLs/snippets in request inputs
  • Enforces load-discipline defaults in retrieval policy
  • Deterministic mapping documented and testable

Dependencies

  • tools/common/TRENDALERT-INVESTIGATION-ADAPTER.md
  • Trend + retrieval/provenance schemas

Benchmark target

Evaluate against:

  • benchmarks/datasets/trend-fixture-001-single-source-noise.json
  • benchmarks/datasets/trend-fixture-002-multi-source-breakout.json
  • benchmarks/datasets/trend-fixture-003-high-impact-manual-review.json

Reference

docs/mvp-use-cases-and-issue-specs.md (Issue-ready spec 4)


Imported from GitHub issue/PR. Originally posted by chrysolambda-ops on 2026-04-01T06:30:41Z.

## Problem Live trend detection produces signals, but not actionable investigations. ## Goal Convert `TrendAlert` records into deterministic investigation requests for claim tracing/archive/provenance workflows. ## Scope - Consume `tools/common/schemas/trend-alert.schema.json` - Map to `tools/common/schemas/retrieval-provenance-request.schema.json` - Choose workflow by alert profile and next-step policy ## Out of scope (v0.1) - Autonomous multi-step investigation execution loop - Social source expansion beyond configured adapters ## Acceptance criteria - [ ] Valid transform for all supported `nextStep.workflow` values - [ ] Preserves evidence URLs/snippets in request inputs - [ ] Enforces load-discipline defaults in retrieval policy - [ ] Deterministic mapping documented and testable ## Dependencies - `tools/common/TRENDALERT-INVESTIGATION-ADAPTER.md` - Trend + retrieval/provenance schemas ## Benchmark target Evaluate against: - `benchmarks/datasets/trend-fixture-001-single-source-noise.json` - `benchmarks/datasets/trend-fixture-002-multi-source-breakout.json` - `benchmarks/datasets/trend-fixture-003-high-impact-manual-review.json` ## Reference `docs/mvp-use-cases-and-issue-specs.md` (Issue-ready spec 4) --- Imported from [GitHub issue/PR](https://github.com/Kyvero-Vexus/truth-kit/issues/3). Originally posted by [chrysolambda-ops](https://github.com/chrysolambda-ops) on 2026-04-01T06:30:41Z.
Sign in to join this conversation.
No description provided.