Kjell Tore Guttormsen
b185db9a12
The lifecycle layer over the trend store: what happens to a trend AFTER first capture.
- re-score on re-capture (last-wins; addTrend duplicate branch, score the one mutable
field; provenance + lifecycle untouched; no false-merge via JSON compare). Reverses
R3a's first-sight D3 — that R3a test reconciled to the new behaviour.
- status new/acted/skipped (effectiveStatus/setStatus + act/skip/reset CLI verbs);
rankForBrief EXCLUDES handled trends (a work queue, not an archive).
- seen-log surfacedCount/lastSurfacedAt (markSurfaced, per-day idempotent); the brief
CLI records surfacing on the store AFTER the pure render, unless --no-mark.
- render: entry id in backticks (copy-paste for act/skip) + · sett Nx prior-day hint.
- schema v3→v4 (additive lossless); the R3a migration block reconciled to the bump,
the new R3b block committed against SCHEMA_VERSION (breaks the reconcile cycle).
score.ts + item.ts untouched (re-score reuses the R3a capture path). RED-first (two
phase: 16 logic-RED + 4 stub-RED). Gate: Section 16k (6 emitters), TRENDS_TESTS_FLOOR
146→171, ASSERT_BASELINE_FLOOR 99→105. trends 171/171, gate 120/0/0, hook suite 139/139.
Plan: docs/research-engine/{brief,plan}-re-r3b.md (light-Voyage hardened @ c40b937).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011vmzxpsFpc8q19LaogAWLD
137 lines
7.2 KiB
Markdown
137 lines
7.2 KiB
Markdown
# linkedin-trends-store
|
||
|
||
Persistent **trend store** — the foundation layer of the research engine
|
||
(retning §5). A topic-tagged, provenance-bearing inventory of trend signals
|
||
captured over time, so the engine accumulates **history** instead of starting
|
||
amnesiac each session.
|
||
|
||
Twin of [`scripts/specifics-bank`](../specifics-bank): same deterministic
|
||
store / dedup / query discipline, different dedupe key — a trend is identified by
|
||
its **normalized title+URL**, not by free-text content.
|
||
|
||
## Generic by architecture
|
||
|
||
Nothing niche-specific lives here. A `TrendRecord` carries free-form `topics`
|
||
tags and a free-form `source` string; *which* topics matter and *which* sources
|
||
to poll are decided upstream (config/profile + the capture agent), never
|
||
hard-coded in this module. The same store serves any niche.
|
||
|
||
## Data location
|
||
|
||
The store lives under the per-user data dir (M0 data-path convention), so trend
|
||
history survives plugin upgrades/reinstalls:
|
||
|
||
```
|
||
${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/trends/trends.json
|
||
```
|
||
|
||
`LINKEDIN_STUDIO_DATA` overrides the root. No path is hard-coded in prose.
|
||
|
||
## Record shape (minimal generic core)
|
||
|
||
```ts
|
||
interface TrendRecord {
|
||
id: string; // sha256(normalized title+url).slice(0,12) — also the dedupe key
|
||
title: string; // headline, verbatim
|
||
url: string; // source URL, verbatim
|
||
source: string; // "tavily" | "websearch" | "manual" | <mcp-name>
|
||
capturedAt: string; // ISO-8601 date — when WE captured it
|
||
publishedAt?: string;// optional source publish date (ISO-8601); distinct from capturedAt, first-sight, never back-filled
|
||
topics: string[]; // query tags; unioned across re-captures
|
||
summary?: string; // optional, verbatim
|
||
score?: TrendScore; // persisted relevance (RE-R3a): { mode, dimensions, composite, priority } — REFRESHED on re-capture (RE-R3b, last-wins)
|
||
status?: TrendStatus; // lifecycle (RE-R3b): "new" | "acted" | "skipped"; absent ⇒ "new"; the brief excludes non-new
|
||
surfacedCount?: number; // seen-log (RE-R3b): distinct days surfaced in a brief; absent ⇒ 0; per-day idempotent
|
||
lastSurfacedAt?: string; // seen-log (RE-R3b): ISO date of the most recent surfacing
|
||
}
|
||
```
|
||
|
||
`score` is the persisted relevance envelope (RE-R3a): a capture **item** carries the
|
||
agent's **judgment** — `{ mode, dimensions }` (the five 1–10 dimension scores) — and the
|
||
store turns that into the persisted `TrendScore` `{ mode, dimensions, composite, priority }`,
|
||
computing the composite + band once via the single scorer owner (`src/score.ts`). It is
|
||
**refreshed on re-capture** (RE-R3b, last-wins — the timing dimension decays, so the newer
|
||
judgment supersedes the stored one; `score` is the one mutable field, provenance stays
|
||
first-sight); the score-free `add` manual path omits it. The morning brief ranks each bucket
|
||
on `composite` first (schema v4).
|
||
|
||
The **lifecycle** fields (RE-R3b) are the trend's life after first capture: `status` is set by
|
||
the `act`/`skip`/`reset` verbs (a freshly-captured trend is implicitly `new`), and the seen-log
|
||
`surfacedCount`/`lastSurfacedAt` is recorded by `brief` (per-day idempotent) so the loop can avoid
|
||
re-surfacing handled work.
|
||
|
||
## CLI
|
||
|
||
```bash
|
||
# Capture freshly-polled trends — the NORMALIZING BATCH path (the research agent's path):
|
||
# raw items on stdin → validate+normalize each → dedupe on title+url → union topics on
|
||
# re-capture → persist the source's publishedAt → persist the relevance score (when carried).
|
||
# Content-invalid items (incl. a malformed/out-of-range score) are reported in the summary
|
||
# errors[], never fail the run; the summary is {added, duplicates, merged, errors}.
|
||
# An item's "score" carries the agent's judgment (mode + the five 1–10 dimensions); the store
|
||
# computes the composite + band and persists the full TrendScore first-sight.
|
||
echo '[{"source":"tavily","title":"Agentic workflows hit production",
|
||
"url":"https://example.com/agentic","topics":["agents","engineering"],
|
||
"publishedAt":"2026-06-20","summary":"Teams ship multi-step agents past the demo stage.",
|
||
"score":{"mode":"kortform","dimensions":{"pillar":9,"audience":8,"timing":9,"angle":7,"authority":6}}}]' \
|
||
| node --import tsx src/cli.ts capture [--store <path>] [--json]
|
||
|
||
# Add a SINGLE trend MANUALLY — raw flags, no normalization, publish-date-free:
|
||
node --import tsx src/cli.ts add \
|
||
--title "Agentic workflows hit production" \
|
||
--url "https://example.com/agentic" \
|
||
--topics "agents,engineering" --source tavily \
|
||
--summary "Teams ship multi-step agents past the demo stage."
|
||
|
||
# Topic-scoped history — trends matching these topics, ranked by overlap then recency
|
||
node --import tsx src/cli.ts query --topics "agents,engineering" [--json]
|
||
|
||
# Time-scoped history — newest first, optionally windowed/capped
|
||
node --import tsx src/cli.ts list [--since 2026-06-01] [--limit 10] [--json]
|
||
|
||
# Dated morning brief — rank the store by composite then pillar-overlap then recency, write a
|
||
# dated Markdown file the SessionStart hook surfaces. Pillars come from the caller (user config).
|
||
# The brief EXCLUDES acted/skipped trends and RECORDS surfacing on the store (per-day idempotent)
|
||
# unless --no-mark. Pillars come from the caller (user config).
|
||
node --import tsx src/cli.ts brief --pillars "agents,engineering" \
|
||
[--fresh-days 7] [--out <dir>] [--no-mark] [--store <path>] [--json]
|
||
|
||
# Lifecycle — mark a trend handled so the brief stops re-surfacing it (id shown in the brief / list --json):
|
||
node --import tsx src/cli.ts act --id <id> # wrote about it
|
||
node --import tsx src/cli.ts skip --id <id> # decided to pass on it
|
||
node --import tsx src/cli.ts reset --id <id> # return it to the queue
|
||
```
|
||
|
||
Both `capture` and `add` dedupe on normalized title+url — re-capturing the same trend
|
||
never appends a duplicate, it only unions any new topics in.
|
||
|
||
## Morning brief (RE-R2b)
|
||
|
||
`brief` is the dated, surfaced read over the store (distinct from `query`/`list`, which are
|
||
interactive dumps). It ranks the store against the user's pillars — overlap desc, then
|
||
`publishedAt ?? capturedAt` recency — buckets into top (2+ pillars), single (1 pillar), and
|
||
older (matched but outside the freshness window, default 7 days), and writes:
|
||
|
||
```
|
||
${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/trends/morning-brief/YYYY-MM-DD.md
|
||
```
|
||
|
||
The file's YAML frontmatter carries a single-line `summary` the SessionStart hook surfaces
|
||
verbatim (zero-tsx — it reads the Markdown, never the TS CLI). As of RE-R3a the brief ranks
|
||
each bucket on the persisted relevance **composite first** (then pillar-overlap, then recency);
|
||
a scored entry shows `· <priority> (<mode>)` and the summary names the top entry's band.
|
||
|
||
As of **RE-R3b** the brief is a **work queue**: it **excludes** `acted`/`skipped` trends, shows
|
||
each entry's `id` in backticks (copy-paste-ready for `act`/`skip --id`), flags a re-surfaced item
|
||
with `· sett Nx` (prior-day count, ≥2), and — unless `--no-mark` — **records surfacing** on the
|
||
store (`surfacedCount`/`lastSurfacedAt`, per-day idempotent) after the pure render. An autonomous
|
||
nightly trigger and a brief-history diff remain later slices.
|
||
|
||
## Tests
|
||
|
||
```bash
|
||
cd scripts/trends
|
||
npm install
|
||
npm test # deterministic store: normalize/id, load/save, dedup+union, query, history
|
||
npm run build
|
||
```
|