Skip to content

AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).

feat(watchlist): spend the per-run budgets on the strongest proposals

Rufus0b1a90426a3a
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 56a1832a..b721dd6f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -130,6 +130,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
server-side, the domain allow/block lists apply, and the search count is
reported, so `RESEARCH_WEB_SEARCH_MAX_USES` and `WEB_SEARCH_MAX_USES`
mean the same thing on both deployment types.
+- **Per-run watch budgets go to the strongest proposals.** The policy
+ scores every proposal first and applies them in descending score order,
+ so when the model files more candidates than the budgets allow, a
+ better-grounded proposal filed later no longer loses its slot to weaker
+ ones filed earlier.
- **Every model call is recorded.** Research specialists, the research
routing and watchlist passes, triage and the chat memory extractor now
write the same `cache_event` audit row the Executive's chat turns always
diff --git a/packages/core/openexecutive/architecture/architecture-facts.yaml b/packages/core/openexecutive/architecture/architecture-facts.yaml
index 5ec99746..a2a7585a 100644
--- a/packages/core/openexecutive/architecture/architecture-facts.yaml
+++ b/packages/core/openexecutive/architecture/architecture-facts.yaml
@@ -1508,7 +1508,15 @@ external_monitoring:
EVERY proposal is rejected (suggestions poll too, so the ceiling must
stop them or it latches); WATCHLIST_RESEARCH_MAX_DIRECT_ADDS (2) and
WATCHLIST_RESEARCH_MAX_PROPOSALS (2) per run (a direct add past its
- budget is filed as a suggestion and charged to that budget).
+ budget is filed as a suggestion and charged to that budget). Budgets
+ are spent strongest first: apply_proposals scores every proposal
+ against the run's starting state, then persists them in descending
+ score order (ties keep file order), re-scoring at insert time so a
+ row inserted for a stronger proposal counts as "already watched" for
+ a weaker one on the same site. Before this a dev run rejected a
+ score-4 Finance watched-entity proposal (Brex) as over budget because
+ two score-3 proposals had been filed earlier in the same call. The
+ returned summaries keep file order.
- quiet defaults on every research row (model cannot loosen): cadence
daily (vendor_status hourly; page_watch/query weekly), severity_floor
medium, keyword trigger (rss/query only — a page_watch summary is
diff --git a/packages/core/openexecutive/architecture/prebuilt/external_monitoring.json b/packages/core/openexecutive/architecture/prebuilt/external_monitoring.json
index 332d5292..d6cf78b4 100644
--- a/packages/core/openexecutive/architecture/prebuilt/external_monitoring.json
+++ b/packages/core/openexecutive/architecture/prebuilt/external_monitoring.json
@@ -1,7 +1,7 @@
{
"section_id": "external_monitoring",
"title": "External Monitoring",
- "markdown": "`openexecutive.monitoring` watches the outside world on a heartbeat and turns detected changes into briefing proposals via the same alert pipeline that handles inbound email and Slack.\n\nThe `external_monitor_scan` heartbeat (`__internal__` channel, default every 5 min) walks `list_watchlist(enabled_only=True)`, skipping rows fresher than their per-source cadence floor. For each due row it fires a read-only source adapter resolved from `_REGISTRY` by `signal_type`:\n\n- `vendor_status` — Statuspage Atom/RSS incident feeds (AWS, Stripe, GitHub, …). Reads each incident's current status out of the entry body, parses `<updated>` into `published_at`, and keys its dedup on `(entry id, <updated>)`; a **seeding** source (see below).\n- `rss` — generic Atom/RSS via feedparser (changelogs, layoffs.fyi, filings). Parses each entry's `<pubDate>`/`<updated>` into `published_at`; a **seeding** source (see below).\n- `stock` — Yahoo Finance chart endpoint; fires on `abs_change_pct_gte` moves.\n- `page_watch` — change-detection on a feed-less page, fetched with the keyless httpx fetcher. A row written before the external scrape path was removed still carries `config.fetch = \"xcrawl\"`; the adapter treats that as a stale baseline, re-captures it from the plain fetch without emitting a signal, and clears the marker.\n- `edgar` and the BILLED `query` web-search adapter.\n\nEach `Signal` is trigger-filtered, severity-clamped to the row's `[floor, ceiling]`, and INSERTed into `external_signals` where `UNIQUE(dedup_key)` drops replays. Survivors pass a suppression cascade (`baseline` → `stale` → `dry_run` → `below_floor` → capture-time relevance enrichment → promote), then `promote_signal_to_alert` builds an `AlertEvent` handed to `alerts.pipeline.schedule_evaluation` and surfaced as a `/today` proposal.\n\nEvery signal carries two timestamps that are never conflated: `captured_at` (when the monitor first saw it) and `published_at` (when the upstream says it happened — RSS `<pubDate>`, EDGAR filing date; null for `stock`, `page_watch`, `query`). Two freshness gates run first in the cascade, before anything that costs an LLM call. **Baseline:** the first poll that returns entries for a row whose adapter declares `seed_on_first_poll` (`rss`, `edgar`) records every entry already in the feed — trigger misses included, so the first entry that ever matches a keyword is news and a later, wider trigger can't resurface old ones — as `suppressed_baseline`, promotes nothing, and stamps `watchlist.baselined_at`, so a new watch reports what changes from now on instead of replaying the feed's back-catalogue (the same idea as `page_watch`'s first-observation baseline). It is keyed on `baselined_at` rather than `last_polled_at`, so a failed first fetch can't forfeit it; the claim and the recording are one transaction (a compare-and-swap on the stamp plus the rows, all-or-nothing), so of two overlapping scans exactly one records the back-catalogue and a failure part-way leaves nothing behind to replay; the other scan promotes only entries dated after that stamp (undated entries count as baseline, since the feed controls the date; entries dated more than a few minutes past its own clock are deferred rather than recorded); and baseline rows don't count against `max_signals_per_scan`, so a large feed can't be half-baselined. `vendor_status` used to sit outside both gates for a structural reason: its dedup key was `sha256(slug, entry id)`, and an incident's id never changes across its updates, so any suppressed insert muted that incident for good. Keying on `(entry id, <updated>)` instead (issue #90) makes a suppression cost one *state* of an incident rather than the incident, so both gates now apply to vendor feeds too — and an incident moving Investigating → Resolved mints a new key and surfaces, while re-polling an unchanged feed still dedups. Because a history feed's archive is mostly incidents resolved months ago, the adapter also carves live news out of its own baseline: it reads each incident's current status from the entry body (Statuspage renders the newest update first as `<strong>Resolved</strong>` / `Investigating` / `Monitoring` / … — the body is parsed by a real HTML parser, off the event loop, and the reading is deliberately asymmetric: any sign that the incident is over closes it, wherever it appears, while only a marked-up label can say it is still open. Working out which update is newest turned out to be something tag soup cannot be trusted to express, and every attempt reported a long-resolved incident as live) and exempts the ones still OPEN via the optional `promote_on_baseline` hook, so a watch added during an outage reports that outage on its first poll while the resolved archive is recorded as `suppressed_baseline`. An unrecognised status counts as closed — a vendor changing feed format must not be able to promote its whole archive at HIGH, and nothing is lost, since the next `<updated>` bump surfaces normally. An exempt entry must still pass the row's trigger filter (one that misses stays in the baseline, so widening a trigger later cannot resurface it) and is still judged by the stale gate below: the exemption buys an entry past the baseline, never past its own timestamp, because \"this is live\" is a reading of vendor-controlled markup and an entry the feed dates outside the age window is not news whatever that reading says. **Stale:** a signal whose `published_at` is older than `EXTERNAL_MONITOR_MAX_SIGNAL_AGE_DAYS` (default 7; `0` disables) at capture time is recorded as `suppressed_stale` and never promoted — a January article a feed resurfaces in September is not September news. An entry dated more than `EXTERNAL_MONITOR_MAX_FUTURE_SKEW_HOURS` ahead (default 24; `0` disables; `config_json.max_future_skew_hours` overrides it per row for calendar or maintenance feeds that legitimately date entries ahead) is deferred instead: skipped for the tick and not recorded (recording would burn its dedup key and let a feed mute an announcement for good by post-dating it), with one aggregated `external_signal_deferred` audit row per poll — carrying each held-back entry's summary and link, and emitted even if the poll later raises — then judged normally once the date passes. Inside the window, the alert body handed to triage carries `Published:` and `Discovered:` lines so the item is judged on when it happened. Adapters prefer a plausible date key over one more than a day in the future (and keep the future value when every key is implausible, so the pipeline defers it rather than waving an undated entry through), and the alert body collapses whitespace in the summary so no source can forge its own labeled body line.\n\nThe `query` adapter is a special case: it emits every web hit flat-LOW (it can't judge materiality per-hit), so for query signals enrichment runs BEFORE the floor gate and `_grade_query_severity` regrades from the relevance read (≥0.8 HIGH, ≥0.5 MEDIUM, else LOW). Without this, any query watch item with a `severity_floor` above LOW would suppress every hit — which is what left the Monitoring section empty even while standing queries were returning material findings.\n\nWhich lane a proposal lands in is decided by `briefing.ranking.categorize`: an unrouted, low/medium signal from a monitoring source (`stock`, `vendor_status`, `rss`, `query`, `edgar`, `page_watch`, or any `external:*` topic tag) is `monitoring` (the collapsible Monitoring section); a routed or high/urgent one is `action` (the \"Needs you\" queue). The triage prompt's External Signals rule covers all six source kinds so it trusts the source and emits the `external:*` tags that drive this split.\n\nThe watchlist is editable from chat (`add_watchlist_entry`, `tune_watchlist_entry`) and HTTP (`/watchlist`); the `executive_research` workflow proposes what to watch through a deterministic policy (next section). Because that workflow is LLM-driven and historically proposed feed URLs it never verified (most were dead — 404 / 403 / not-actually-a-feed), every `rss` target is validated at insert time (`monitoring.target_validation`): a URL that fetches and parses as a feed is kept; a public page that isn't a feed is converted to a `page_watch` when the body the feed check already fetched reduces to readable text, otherwise rejected (HTTP 422 / tool error); SSRF-blocked or unparseable URLs are rejected outright and never fetched. Non-`rss` types insert unchanged with no network I/O.\n\n### One watch, one card — and dismissals teach the watch\n\n`promote_signal_to_alert` stamps the `AlertEvent` with `dedup_hint=\"watch:<slug>\"`, which `alerts.pipeline` uses as the *alert* dedup key. A repeat from the same watch coalesces into the open card (`occurrence_count`, `last_seen_at`, severity max) rather than minting another, and re-pings only when severity rose into high/urgent — so a ticker that stays over its threshold or an incident that keeps updating no longer produces a new \"Needs you\" item every day. The signal-level `dedup_key` (stock's UTC-date bucket, vendor_status's `<updated>`) is untouched, so every observation still lands in `external_signals`. Dismissing a watch-sourced alert calls `store.record_dismissal(slug)` (`dismiss_count += 1`, `trust_score = max(0.2, trust × 0.8)`); approving calls `record_confirmation` (+0.05). `trust_score` discounts the briefing ranking and is shown to the Executive's alert review as evidence, alongside the newer signals for that watch (a \"Resolved\" incident state, a reversed move) that let it close the card with evidence.\n\n### What the research pass may put on the watchlist\n\nThe run itself: seven specialists (or the subset named by `RESEARCH_SPECIALISTS`) each make one call with the basic `web_search` server tool, capped at `RESEARCH_WEB_SEARCH_MAX_USES` searches (default 3, separate from the chat knob; via OpenRouter, Claude or not, the tool becomes OpenRouter's `openrouter:web_search` server tool with the same cap and domain lists, and the search count is recorded there too), and emit at most three findings — the cap sits in the tool schema and is applied again after parsing. Every specialist sees what department heads asked to have watched (a `DEPARTMENT WATCH INTERESTS` block) and the ten most recent decisions, and may ground a finding in either. Findings are deduplicated, low-confidence ones dropped, then the Executive routes the rest; the routing pass cannot start a workflow (`run_workflow` is withheld, `suggest_workflow` is not). There is no external fetch or verify service: every page read is the on-box fetcher. The periodic run is considered every `WATCHLIST_RESEARCH_INTERVAL_MINUTES` (default 360) and skipped when nothing changed. Every model call the run makes is recorded as a `cache_event` audit row tagged with the run id, and the run's result and its `watchlist_research_periodic_ran` row carry a `usage` block (calls, tokens, searches, per source), so what a run did is readable from the audit log.\n\nEvery watchlist row carries an `origin`: `manual` (the principal, via UI/API), `executive` (the chat tool acting on a request), `research` (the research pass added it on its own) or `research_proposed` (a pending suggestion). The `executive_research` workflow's watchlist pass no longer calls `add_watchlist_entry`; its only tool is `propose_watch` (slug, signal_type, target, `grounding_entity`, `rationale`, `certainty`), and `monitoring.research.watch_policy` decides what happens to each proposal from company data, not from the model's confidence in itself:\n\n- **Direct add** — the row lands live, `origin=research`, with quiet defaults the model cannot loosen (daily cadence — hourly for `vendor_status`, weekly for `page_watch`/`query` — `severity_floor=medium`, a keyword trigger of material-event words + the current-year priority terms for `rss` / `query` only — never for `page_watch`, whose summary is just \"page changed\" and would never match, and never the entity's own name, which appears in every feed entry's label and would fire on everything — and `abs_change_pct_gte=5` for stocks). Requires the `grounding_entity` to name an external entity in company data — the company itself, a `competitive_landscape.primary_competitors` entry, one of the profile's `vendors` / `tickers`, or an entity a department lists under its **watched entities** (each list entry is parsed to its name: \"Tesla (TSLA) — Model Y is the benchmark\" grounds as `Tesla` plus the ticker `TSLA`, \"GM / Chevrolet (…)\" as both names, and \"Brex (brex.com)\" pins Brex's own domains so only those sites count as its own source; the description after the dash never becomes a term, short names such as BYD or GM match as whole words, and a ticker grounds only as itself) (an initiative title, a current-year priority, a department's charter-scope phrase or a goal's key result also grounds a proposal, but only ever to a suggestion: they are bags of common words a planted finding can echo) — *and* a score ≥ 4 on a fixed ledger: +2 entity in company data (mandatory), +1 entity already watched under another source, +1 target is the entity's own source (for stock/edgar the grounding entity must be the ticker itself; a URL whose site label — `acme` in `status.acme.com` / `acme.co.uk`, never a subdomain or TLD — is the entity's leading name or all its words run together, never a generic trailing word; or a primary-source host such as sec.gov), +1 finding confidence high, +1 cross-specialist consensus (the finding points count only when the cited finding concerns this source: a URL target must share its site with one of the finding's cited URLs, a ticker must appear in its text — a strong finding cannot be borrowed for an unrelated page), +1 the entity (a company-data term, never a bare watch label) is named in one of the ten most recent episodic decisions from the last 90 days — the whole term, or every distinctive word of it, as whole words — ±1 from the policy's own approval history for that `(signal_type, grounding kind)` once it has ≥5 samples. A direct add is further reserved for the entity's **own** source (its ticker, its site, its status page): a well-corroborated third-party page about a competitor is the principal's call. It also always needs a linked finding that cites the source — company data plus a decision mention can reach the score bar alone, but nothing goes live on hearsay. The model's `certainty` can only downgrade a direct add to a suggestion; a `query` watch is always a suggestion. At most `WATCHLIST_RESEARCH_MAX_DIRECT_ADDS` (2) per run. When one term appears in several sources the strongest kind wins (company > competitor > vendor > ticker > department entity > initiative > priority > department scope > watch label); a term that came from a department carries the department along even when a stronger profile kind wins, so a profile vendor that Finance also lists stays a vendor and still routes to Finance.\n- **Linked finding.** `finding_index` is required on `propose_watch` and the pass is told so; when the model omits it anyway, or cites a finding that does not concern the source, the policy links the finding that best does (a cited URL on the target's site or the ticker named in its text outranks a mere mention of the entity; then the entity's own site, confidence) and says so in the first reason. A proposal that no finding cites is rejected as having no evidence.\n- **Suggestion** — anything that validates, has a linked finding and scores at least 1 but misses the bar is inserted in `dry_run` (polls and records signals, never alerts) with `origin=research_proposed` and the rationale in `notes`, at most `WATCHLIST_RESEARCH_MAX_PROPOSALS` (2) per run. `/watchlist` shows them in a \"Suggested by the Executive\" section with Approve (`POST /watchlist/{slug}/approve` → `active`, `origin=research`) and Decline (`POST /watchlist/{slug}/decline` with a reason: `not_relevant` blacklists the entity, `wrong_source` blacklists only this target, `too_noisy` keeps the source live with `severity_floor=high` — the one way a suggestion goes live without an approve — and counts as a decline for calibration). A suggestion nobody reviews within `WATCHLIST_PROPOSAL_TTL_DAYS` (14) is removed. The morning brief mentions the pending count in one line; a `watchlist_suggestions` alert nudges only once ≥3 suggestions have waited ≥7 days — one card for the whole pile (an open card is refreshed in place; a dismissed one is not re-minted until the next ISO week), so acting on a suggestion never spawns another nudge.\n- **Routed to a department** — a watch grounded in a department's term (or whose entity a recent decision recorded for that department names) is inserted with `route_to_department` and `route_to_person_id` set to the department and its head at insert time. `_signal_to_alert_event` now maps both onto the `AlertEvent` for every watch (`routed_to_person_id`, `department=<slug>` — a tag hint, deliberately not the `channel` field triage reads as a team room), so the alerts it raises queue on the head's `/today` (as action items, since routed alerts are never hidden in Monitoring) and carry the `department:<slug>` tag instead of landing in the principal's unrouted queue. Suggestions in a department's area are put in front of its head, not the principal: after each run, one \"Watch suggestions for <Department>\" card per department is filed through `propose_via_alert` (routed to the head, or the principal when there is no head; an open card is refreshed in place and an acknowledged one is not re-minted until the next ISO week), and the principal's pile-up nudge counts only suggestions that reached no head — the principal's own and those of a department without a head — so none can become invisible. `/watchlist` labels routed rows \"for: <department>\".\n- **Reject** — an invalid target, a second watch on the same site + signal type (disabled rows included), a declined target or entity, nothing vouching for it (no linked finding, score 0), the enabled-watch ceiling `WATCHLIST_MAX_ENABLED` (40; suggestions poll too, so the ceiling stops them as well), or a spent budget. Every decision is audited (`watchlist_research_added` / `_suggested` / `_rejected`) with the score and reasons; the stamp also lives in the row's `config_json._policy` so approve/decline/auto-disable can attribute the outcome.\n\n**Declines are remembered and enforced.** `watchlist_declines` is keyed by the normalized target (upper-cased ticker; URL with `https` forced, `www.` dropped, host and path lower-cased, query, fragment and trailing slash removed; free-text queries case- and whitespace-folded). A `not_relevant` decline also blacklists the *entity*: any later proposal whose `grounding_entity` names it is refused whatever the target. An explicit decline — the Decline button, \"Stop watching…\" on a research-added card, `remove_watchlist_entry` or `DELETE /watchlist/{slug}` on a research-origin row — is permanent; an unreviewed expiry may be re-proposed once after 90 days. The `propose_watch` handler refuses a declined target or entity before anything is fetched, so a new slug cannot route around a decline (URL keys also fold percent-encoding, dot segments and a trailing host dot); the list is also rendered to the model as DECLINED. The routing pass that runs before the watchlist pass has no watchlist write tools at all (`add_watchlist_entry`, `tune_watchlist_entry`, `remove_watchlist_entry` are withheld from synthesis), and `tune_watchlist_entry` accepts only `notes` on a pending suggestion — never `mode` / `enabled` (only the principal's approve or decline moves one out of review) nor cadence / floor / trigger (it goes live with the quiet defaults policy gave it). Every URL-typed target (`rss`, `vendor_status`, `page_watch`) is checked against the SSRF guard at insert time, and a suggestion's `source_url` link is kept only when it is a public http(s) URL.\n\n**The policy learns from outcomes.** Approve, decline, expiry and auto-disable write `watchlist_policy_outcomes` rows keyed by `(signal_type, grounding kind, specialist)`; the pass renders the tallies (\"stock watches grounded in a competitor: 4 approved / 1 declined\"; \"proposals from cso: …\") and the score ledger reads them. The research turn also shows each existing watch's `origin`, `fired_count`, `dismiss_count` and `trust_score`.\n\n**Research watches retire themselves.** The scheduler's 15-minute sweep (`watch_policy.sweep`, alongside the alert expiry sweep) disables a `research`-origin watch — audited as `watchlist_auto_disabled`, re-enable from `/watchlist` — when it fired ≥5 alerts of which ≥2 were dismissed and trust ≤ 0.5, or after 3 consecutive poll failures (silence is deliberately not a rule: an unchanged page or a healthy vendor is a working watch); the retired target is also recorded as a 90-day decline so the next run cannot re-add it under a new slug with fresh counters (a disabled row already counts as \"same source watched\"). Approve, decline and expiry are compare-and-act on \"still pending\", so a concurrent approve always wins over a decline or the sweep. Direct adds and auto-disables appear in the brief's \"handled overnight\" block as `watching` / `stopped_watching`. The research skip-if-unchanged fingerprint hashes only enabled, `active` rows, so approving or declining a suggestion never triggers a fresh 7-specialist run.\n\n### Invariants\n\n- Adapters are read-only — they never write upstream and never auto-execute.\n- Every `Signal` carries a deterministic `dedup_key` and a mandatory `provenance_url`.\n- Every fetch is the on-box httpx fetcher: SSRF-guarded and bounded by `external_monitor_max_fetch_bytes`. No path delegates a fetch to an external service.\n- Suppressed signals are still persisted so audits show the full picture.\n- A repeat from the same watch never becomes a second open card: the alert-level `watch:<slug>` key coalesces it, and only a severity escalation re-dispatches.\n- The research model never writes the watchlist: it proposes, deterministic policy adds (only when grounded in company data) or suggests, and a target the principal declined is refused at the handler.",
+ "markdown": "`openexecutive.monitoring` watches the outside world on a heartbeat and turns detected changes into briefing proposals via the same alert pipeline that handles inbound email and Slack.\n\nThe `external_monitor_scan` heartbeat (`__internal__` channel, default every 5 min) walks `list_watchlist(enabled_only=True)`, skipping rows fresher than their per-source cadence floor. For each due row it fires a read-only source adapter resolved from `_REGISTRY` by `signal_type`:\n\n- `vendor_status` — Statuspage Atom/RSS incident feeds (AWS, Stripe, GitHub, …). Reads each incident's current status out of the entry body, parses `<updated>` into `published_at`, and keys its dedup on `(entry id, <updated>)`; a **seeding** source (see below).\n- `rss` — generic Atom/RSS via feedparser (changelogs, layoffs.fyi, filings). Parses each entry's `<pubDate>`/`<updated>` into `published_at`; a **seeding** source (see below).\n- `stock` — Yahoo Finance chart endpoint; fires on `abs_change_pct_gte` moves.\n- `page_watch` — change-detection on a feed-less page, fetched with the keyless httpx fetcher. A row written before the external scrape path was removed still carries `config.fetch = \"xcrawl\"`; the adapter treats that as a stale baseline, re-captures it from the plain fetch without emitting a signal, and clears the marker.\n- `edgar` and the BILLED `query` web-search adapter.\n\nEach `Signal` is trigger-filtered, severity-clamped to the row's `[floor, ceiling]`, and INSERTed into `external_signals` where `UNIQUE(dedup_key)` drops replays. Survivors pass a suppression cascade (`baseline` → `stale` → `dry_run` → `below_floor` → capture-time relevance enrichment → promote), then `promote_signal_to_alert` builds an `AlertEvent` handed to `alerts.pipeline.schedule_evaluation` and surfaced as a `/today` proposal.\n\nEvery signal carries two timestamps that are never conflated: `captured_at` (when the monitor first saw it) and `published_at` (when the upstream says it happened — RSS `<pubDate>`, EDGAR filing date; null for `stock`, `page_watch`, `query`). Two freshness gates run first in the cascade, before anything that costs an LLM call. **Baseline:** the first poll that returns entries for a row whose adapter declares `seed_on_first_poll` (`rss`, `edgar`) records every entry already in the feed — trigger misses included, so the first entry that ever matches a keyword is news and a later, wider trigger can't resurface old ones — as `suppressed_baseline`, promotes nothing, and stamps `watchlist.baselined_at`, so a new watch reports what changes from now on instead of replaying the feed's back-catalogue (the same idea as `page_watch`'s first-observation baseline). It is keyed on `baselined_at` rather than `last_polled_at`, so a failed first fetch can't forfeit it; the claim and the recording are one transaction (a compare-and-swap on the stamp plus the rows, all-or-nothing), so of two overlapping scans exactly one records the back-catalogue and a failure part-way leaves nothing behind to replay; the other scan promotes only entries dated after that stamp (undated entries count as baseline, since the feed controls the date; entries dated more than a few minutes past its own clock are deferred rather than recorded); and baseline rows don't count against `max_signals_per_scan`, so a large feed can't be half-baselined. `vendor_status` used to sit outside both gates for a structural reason: its dedup key was `sha256(slug, entry id)`, and an incident's id never changes across its updates, so any suppressed insert muted that incident for good. Keying on `(entry id, <updated>)` instead (issue #90) makes a suppression cost one *state* of an incident rather than the incident, so both gates now apply to vendor feeds too — and an incident moving Investigating → Resolved mints a new key and surfaces, while re-polling an unchanged feed still dedups. Because a history feed's archive is mostly incidents resolved months ago, the adapter also carves live news out of its own baseline: it reads each incident's current status from the entry body (Statuspage renders the newest update first as `<strong>Resolved</strong>` / `Investigating` / `Monitoring` / … — the body is parsed by a real HTML parser, off the event loop, and the reading is deliberately asymmetric: any sign that the incident is over closes it, wherever it appears, while only a marked-up label can say it is still open. Working out which update is newest turned out to be something tag soup cannot be trusted to express, and every attempt reported a long-resolved incident as live) and exempts the ones still OPEN via the optional `promote_on_baseline` hook, so a watch added during an outage reports that outage on its first poll while the resolved archive is recorded as `suppressed_baseline`. An unrecognised status counts as closed — a vendor changing feed format must not be able to promote its whole archive at HIGH, and nothing is lost, since the next `<updated>` bump surfaces normally. An exempt entry must still pass the row's trigger filter (one that misses stays in the baseline, so widening a trigger later cannot resurface it) and is still judged by the stale gate below: the exemption buys an entry past the baseline, never past its own timestamp, because \"this is live\" is a reading of vendor-controlled markup and an entry the feed dates outside the age window is not news whatever that reading says. **Stale:** a signal whose `published_at` is older than `EXTERNAL_MONITOR_MAX_SIGNAL_AGE_DAYS` (default 7; `0` disables) at capture time is recorded as `suppressed_stale` and never promoted — a January article a feed resurfaces in September is not September news. An entry dated more than `EXTERNAL_MONITOR_MAX_FUTURE_SKEW_HOURS` ahead (default 24; `0` disables; `config_json.max_future_skew_hours` overrides it per row for calendar or maintenance feeds that legitimately date entries ahead) is deferred instead: skipped for the tick and not recorded (recording would burn its dedup key and let a feed mute an announcement for good by post-dating it), with one aggregated `external_signal_deferred` audit row per poll — carrying each held-back entry's summary and link, and emitted even if the poll later raises — then judged normally once the date passes. Inside the window, the alert body handed to triage carries `Published:` and `Discovered:` lines so the item is judged on when it happened. Adapters prefer a plausible date key over one more than a day in the future (and keep the future value when every key is implausible, so the pipeline defers it rather than waving an undated entry through), and the alert body collapses whitespace in the summary so no source can forge its own labeled body line.\n\nThe `query` adapter is a special case: it emits every web hit flat-LOW (it can't judge materiality per-hit), so for query signals enrichment runs BEFORE the floor gate and `_grade_query_severity` regrades from the relevance read (≥0.8 HIGH, ≥0.5 MEDIUM, else LOW). Without this, any query watch item with a `severity_floor` above LOW would suppress every hit — which is what left the Monitoring section empty even while standing queries were returning material findings.\n\nWhich lane a proposal lands in is decided by `briefing.ranking.categorize`: an unrouted, low/medium signal from a monitoring source (`stock`, `vendor_status`, `rss`, `query`, `edgar`, `page_watch`, or any `external:*` topic tag) is `monitoring` (the collapsible Monitoring section); a routed or high/urgent one is `action` (the \"Needs you\" queue). The triage prompt's External Signals rule covers all six source kinds so it trusts the source and emits the `external:*` tags that drive this split.\n\nThe watchlist is editable from chat (`add_watchlist_entry`, `tune_watchlist_entry`) and HTTP (`/watchlist`); the `executive_research` workflow proposes what to watch through a deterministic policy (next section). Because that workflow is LLM-driven and historically proposed feed URLs it never verified (most were dead — 404 / 403 / not-actually-a-feed), every `rss` target is validated at insert time (`monitoring.target_validation`): a URL that fetches and parses as a feed is kept; a public page that isn't a feed is converted to a `page_watch` when the body the feed check already fetched reduces to readable text, otherwise rejected (HTTP 422 / tool error); SSRF-blocked or unparseable URLs are rejected outright and never fetched. Non-`rss` types insert unchanged with no network I/O.\n\n### One watch, one card — and dismissals teach the watch\n\n`promote_signal_to_alert` stamps the `AlertEvent` with `dedup_hint=\"watch:<slug>\"`, which `alerts.pipeline` uses as the *alert* dedup key. A repeat from the same watch coalesces into the open card (`occurrence_count`, `last_seen_at`, severity max) rather than minting another, and re-pings only when severity rose into high/urgent — so a ticker that stays over its threshold or an incident that keeps updating no longer produces a new \"Needs you\" item every day. The signal-level `dedup_key` (stock's UTC-date bucket, vendor_status's `<updated>`) is untouched, so every observation still lands in `external_signals`. Dismissing a watch-sourced alert calls `store.record_dismissal(slug)` (`dismiss_count += 1`, `trust_score = max(0.2, trust × 0.8)`); approving calls `record_confirmation` (+0.05). `trust_score` discounts the briefing ranking and is shown to the Executive's alert review as evidence, alongside the newer signals for that watch (a \"Resolved\" incident state, a reversed move) that let it close the card with evidence.\n\n### What the research pass may put on the watchlist\n\nThe run itself: seven specialists (or the subset named by `RESEARCH_SPECIALISTS`) each make one call with the basic `web_search` server tool, capped at `RESEARCH_WEB_SEARCH_MAX_USES` searches (default 3, separate from the chat knob; via OpenRouter, Claude or not, the tool becomes OpenRouter's `openrouter:web_search` server tool with the same cap and domain lists, and the search count is recorded there too), and emit at most three findings — the cap sits in the tool schema and is applied again after parsing. Every specialist sees what department heads asked to have watched (a `DEPARTMENT WATCH INTERESTS` block) and the ten most recent decisions, and may ground a finding in either. Findings are deduplicated, low-confidence ones dropped, then the Executive routes the rest; the routing pass cannot start a workflow (`run_workflow` is withheld, `suggest_workflow` is not). There is no external fetch or verify service: every page read is the on-box fetcher. The periodic run is considered every `WATCHLIST_RESEARCH_INTERVAL_MINUTES` (default 360) and skipped when nothing changed. Every model call the run makes is recorded as a `cache_event` audit row tagged with the run id, and the run's result and its `watchlist_research_periodic_ran` row carry a `usage` block (calls, tokens, searches, per source), so what a run did is readable from the audit log.\n\nEvery watchlist row carries an `origin`: `manual` (the principal, via UI/API), `executive` (the chat tool acting on a request), `research` (the research pass added it on its own) or `research_proposed` (a pending suggestion). The `executive_research` workflow's watchlist pass no longer calls `add_watchlist_entry`; its only tool is `propose_watch` (slug, signal_type, target, `grounding_entity`, `rationale`, `certainty`), and `monitoring.research.watch_policy` decides what happens to each proposal from company data, not from the model's confidence in itself:\n\n- **Direct add** — the row lands live, `origin=research`, with quiet defaults the model cannot loosen (daily cadence — hourly for `vendor_status`, weekly for `page_watch`/`query` — `severity_floor=medium`, a keyword trigger of material-event words + the current-year priority terms for `rss` / `query` only — never for `page_watch`, whose summary is just \"page changed\" and would never match, and never the entity's own name, which appears in every feed entry's label and would fire on everything — and `abs_change_pct_gte=5` for stocks). Requires the `grounding_entity` to name an external entity in company data — the company itself, a `competitive_landscape.primary_competitors` entry, one of the profile's `vendors` / `tickers`, or an entity a department lists under its **watched entities** (each list entry is parsed to its name: \"Tesla (TSLA) — Model Y is the benchmark\" grounds as `Tesla` plus the ticker `TSLA`, \"GM / Chevrolet (…)\" as both names, and \"Brex (brex.com)\" pins Brex's own domains so only those sites count as its own source; the description after the dash never becomes a term, short names such as BYD or GM match as whole words, and a ticker grounds only as itself) (an initiative title, a current-year priority, a department's charter-scope phrase or a goal's key result also grounds a proposal, but only ever to a suggestion: they are bags of common words a planted finding can echo) — *and* a score ≥ 4 on a fixed ledger: +2 entity in company data (mandatory), +1 entity already watched under another source, +1 target is the entity's own source (for stock/edgar the grounding entity must be the ticker itself; a URL whose site label — `acme` in `status.acme.com` / `acme.co.uk`, never a subdomain or TLD — is the entity's leading name or all its words run together, never a generic trailing word; or a primary-source host such as sec.gov), +1 finding confidence high, +1 cross-specialist consensus (the finding points count only when the cited finding concerns this source: a URL target must share its site with one of the finding's cited URLs, a ticker must appear in its text — a strong finding cannot be borrowed for an unrelated page), +1 the entity (a company-data term, never a bare watch label) is named in one of the ten most recent episodic decisions from the last 90 days — the whole term, or every distinctive word of it, as whole words — ±1 from the policy's own approval history for that `(signal_type, grounding kind)` once it has ≥5 samples. A direct add is further reserved for the entity's **own** source (its ticker, its site, its status page): a well-corroborated third-party page about a competitor is the principal's call. It also always needs a linked finding that cites the source — company data plus a decision mention can reach the score bar alone, but nothing goes live on hearsay. The model's `certainty` can only downgrade a direct add to a suggestion; a `query` watch is always a suggestion. At most `WATCHLIST_RESEARCH_MAX_DIRECT_ADDS` (2) per run. When one term appears in several sources the strongest kind wins (company > competitor > vendor > ticker > department entity > initiative > priority > department scope > watch label); a term that came from a department carries the department along even when a stronger profile kind wins, so a profile vendor that Finance also lists stays a vendor and still routes to Finance.\n- **Linked finding.** `finding_index` is required on `propose_watch` and the pass is told so; when the model omits it anyway, or cites a finding that does not concern the source, the policy links the finding that best does (a cited URL on the target's site or the ticker named in its text outranks a mere mention of the entity; then the entity's own site, confidence) and says so in the first reason. A proposal that no finding cites is rejected as having no evidence.\n- **Suggestion** — anything that validates, has a linked finding and scores at least 1 but misses the bar is inserted in `dry_run` (polls and records signals, never alerts) with `origin=research_proposed` and the rationale in `notes`, at most `WATCHLIST_RESEARCH_MAX_PROPOSALS` (2) per run — budgets are spent strongest first (proposals are scored, then applied in descending score order, ties in file order), so a better-grounded proposal filed later never loses its slot to weaker ones filed earlier. `/watchlist` shows them in a \"Suggested by the Executive\" section with Approve (`POST /watchlist/{slug}/approve` → `active`, `origin=research`) and Decline (`POST /watchlist/{slug}/decline` with a reason: `not_relevant` blacklists the entity, `wrong_source` blacklists only this target, `too_noisy` keeps the source live with `severity_floor=high` — the one way a suggestion goes live without an approve — and counts as a decline for calibration). A suggestion nobody reviews within `WATCHLIST_PROPOSAL_TTL_DAYS` (14) is removed. The morning brief mentions the pending count in one line; a `watchlist_suggestions` alert nudges only once ≥3 suggestions have waited ≥7 days — one card for the whole pile (an open card is refreshed in place; a dismissed one is not re-minted until the next ISO week), so acting on a suggestion never spawns another nudge.\n- **Routed to a department** — a watch grounded in a department's term (or whose entity a recent decision recorded for that department names) is inserted with `route_to_department` and `route_to_person_id` set to the department and its head at insert time. `_signal_to_alert_event` now maps both onto the `AlertEvent` for every watch (`routed_to_person_id`, `department=<slug>` — a tag hint, deliberately not the `channel` field triage reads as a team room), so the alerts it raises queue on the head's `/today` (as action items, since routed alerts are never hidden in Monitoring) and carry the `department:<slug>` tag instead of landing in the principal's unrouted queue. Suggestions in a department's area are put in front of its head, not the principal: after each run, one \"Watch suggestions for <Department>\" card per department is filed through `propose_via_alert` (routed to the head, or the principal when there is no head; an open card is refreshed in place and an acknowledged one is not re-minted until the next ISO week), and the principal's pile-up nudge counts only suggestions that reached no head — the principal's own and those of a department without a head — so none can become invisible. `/watchlist` labels routed rows \"for: <department>\".\n- **Reject** — an invalid target, a second watch on the same site + signal type (disabled rows included), a declined target or entity, nothing vouching for it (no linked finding, score 0), the enabled-watch ceiling `WATCHLIST_MAX_ENABLED` (40; suggestions poll too, so the ceiling stops them as well), or a spent budget. Every decision is audited (`watchlist_research_added` / `_suggested` / `_rejected`) with the score and reasons; the stamp also lives in the row's `config_json._policy` so approve/decline/auto-disable can attribute the outcome.\n\n**Declines are remembered and enforced.** `watchlist_declines` is keyed by the normalized target (upper-cased ticker; URL with `https` forced, `www.` dropped, host and path lower-cased, query, fragment and trailing slash removed; free-text queries case- and whitespace-folded). A `not_relevant` decline also blacklists the *entity*: any later proposal whose `grounding_entity` names it is refused whatever the target. An explicit decline — the Decline button, \"Stop watching…\" on a research-added card, `remove_watchlist_entry` or `DELETE /watchlist/{slug}` on a research-origin row — is permanent; an unreviewed expiry may be re-proposed once after 90 days. The `propose_watch` handler refuses a declined target or entity before anything is fetched, so a new slug cannot route around a decline (URL keys also fold percent-encoding, dot segments and a trailing host dot); the list is also rendered to the model as DECLINED. The routing pass that runs before the watchlist pass has no watchlist write tools at all (`add_watchlist_entry`, `tune_watchlist_entry`, `remove_watchlist_entry` are withheld from synthesis), and `tune_watchlist_entry` accepts only `notes` on a pending suggestion — never `mode` / `enabled` (only the principal's approve or decline moves one out of review) nor cadence / floor / trigger (it goes live with the quiet defaults policy gave it). Every URL-typed target (`rss`, `vendor_status`, `page_watch`) is checked against the SSRF guard at insert time, and a suggestion's `source_url` link is kept only when it is a public http(s) URL.\n\n**The policy learns from outcomes.** Approve, decline, expiry and auto-disable write `watchlist_policy_outcomes` rows keyed by `(signal_type, grounding kind, specialist)`; the pass renders the tallies (\"stock watches grounded in a competitor: 4 approved / 1 declined\"; \"proposals from cso: …\") and the score ledger reads them. The research turn also shows each existing watch's `origin`, `fired_count`, `dismiss_count` and `trust_score`.\n\n**Research watches retire themselves.** The scheduler's 15-minute sweep (`watch_policy.sweep`, alongside the alert expiry sweep) disables a `research`-origin watch — audited as `watchlist_auto_disabled`, re-enable from `/watchlist` — when it fired ≥5 alerts of which ≥2 were dismissed and trust ≤ 0.5, or after 3 consecutive poll failures (silence is deliberately not a rule: an unchanged page or a healthy vendor is a working watch); the retired target is also recorded as a 90-day decline so the next run cannot re-add it under a new slug with fresh counters (a disabled row already counts as \"same source watched\"). Approve, decline and expiry are compare-and-act on \"still pending\", so a concurrent approve always wins over a decline or the sweep. Direct adds and auto-disables appear in the brief's \"handled overnight\" block as `watching` / `stopped_watching`. The research skip-if-unchanged fingerprint hashes only enabled, `active` rows, so approving or declining a suggestion never triggers a fresh 7-specialist run.\n\n### Invariants\n\n- Adapters are read-only — they never write upstream and never auto-execute.\n- Every `Signal` carries a deterministic `dedup_key` and a mandatory `provenance_url`.\n- Every fetch is the on-box httpx fetcher: SSRF-guarded and bounded by `external_monitor_max_fetch_bytes`. No path delegates a fetch to an external service.\n- Suppressed signals are still persisted so audits show the full picture.\n- A repeat from the same watch never becomes a second open card: the alert-level `watch:<slug>` key coalesces it, and only a severity escalation re-dispatches.\n- The research model never writes the watchlist: it proposes, deterministic policy adds (only when grounded in company data) or suggests, and a target the principal declined is refused at the handler.",
"mermaid": "flowchart TD\n ADD[\"add (chat tool / POST /watchlist / research)\"]\n VAL[\"target_validation: rss feed? → keep / readable page → page_watch / reject\"]\n WL[(\"watchlist\")]\n HB[\"external_monitor_scan heartbeat (~5 min)\"]\n AD[\"read-only adapters: vendor_status / rss / stock / query / edgar / page_watch (httpx)\"]\n SIG[(\"external_signals UNIQUE(dedup_key)\")]\n ENRICH[\"capture-time enrichment<br/>(relevance score + why_it_matters)\"]\n PROMO[\"promote_signal_to_alert\"]\n PIPE[\"alert pipeline (triage)\"]\n TODAY[\"/today proposals\"]\n ADD --> VAL\n VAL -->|\"insert valid rows\"| WL\n HB -->|\"walk enabled rows\"| WL\n WL -->|\"poll due rows\"| AD\n AD -->|\"emit Signal\"| SIG\n SIG -->|\"baseline / stale / dry_run / floor gates\"| ENRICH\n ENRICH -->|\"≥ relevance floor\"| PROMO\n PROMO --> PIPE\n PIPE --> TODAY\n class HB hot\n class WL storage\n class VAL compute\n class AD external\n class SIG storage\n class ENRICH compute\n class PROMO compute\n class PIPE compute\n class TODAY entry\n class ADD compute",
"generated_at": "2026-09-12T17:10:00+00:00"
}
diff --git a/packages/core/openexecutive/monitoring/research/watch_policy.py b/packages/core/openexecutive/monitoring/research/watch_policy.py
index b368b20d..357e9982 100644
--- a/packages/core/openexecutive/monitoring/research/watch_policy.py
+++ b/packages/core/openexecutive/monitoring/research/watch_policy.py
@@ -1092,6 +1092,50 @@ def policy_stamp_of(item: WatchlistItem) -> dict[str, Any]:
return dict(stamp) if isinstance(stamp, dict) else {}
+def _link_evidence(
+ proposal: WatchProposal,
+ findings: list[ResearchFinding],
+ ctx: PolicyContext,
+) -> tuple[WatchProposal, ResearchFinding | None, bool, str]:
+ """Resolve the finding a proposal cites, repairing a missing or
+ unsupported ``finding_index`` with the finding that best concerns the
+ source. Returns ``(proposal, finding, supported, linked_note)``; the
+ proposal is a copy when its index was repaired (the caller's is left as
+ filed)."""
+ finding = (
+ findings[proposal.finding_index]
+ if proposal.finding_index is not None and 0 <= proposal.finding_index < len(findings)
+ else None
+ )
+ linked_note = ""
+ cited_term = match_vocab(proposal.grounding_entity, ctx.vocabulary)
+ given = proposal.finding_index
+ given_valid = given is not None and 0 <= given < len(findings)
+ if finding is None or not _finding_supports(
+ proposal, finding, cited_term[0] if cited_term else "", ctx.vocabulary,
+ ):
+ # The model routinely omits finding_index, or guesses one that
+ # does not concern this source; the finding that does is still
+ # the evidence, so link it (a copy: the caller's proposal is
+ # left as filed). A cited finding that does not concern the
+ # source is never kept as evidence.
+ cited_note = ""
+ if given is not None:
+ cited_note = f" (the cited #{given + 1} did not)" if given_valid else " (the cited index was invalid)"
+ auto_index = auto_link_finding(proposal, findings, ctx)
+ if auto_index is not None:
+ finding = findings[auto_index]
+ proposal = dataclasses.replace(proposal, finding_index=auto_index)
+ linked_note = f"linked to finding #{auto_index + 1}, which concerns this source" + cited_note
+ # A cited finding that does not concern the source still marks the
+ # proposal as research-derived (it may be a suggestion) but is never
+ # the evidence link shown beside Approve.
+ supported = finding is not None and _finding_supports(
+ proposal, finding, cited_term[0] if cited_term else "", ctx.vocabulary,
+ )
+ return proposal, finding, supported, linked_note
+
+
def apply_proposals(
proposals: list[WatchProposal],
findings: list[ResearchFinding],
@@ -1100,9 +1144,18 @@ def apply_proposals(
db_path: Path | None = None,
) -> list[dict[str, Any]]:
"""Classify and persist. Returns tool-call-shaped summaries
- (``tool='propose_watch'``, plus ``outcome`` = added | suggested | rejected)
- so the run's artifact and audit accounting stay uniform."""
- summaries: list[dict[str, Any]] = []
+ (``tool='propose_watch'``, plus ``outcome`` = added | suggested | rejected),
+ one per proposal in the order they were filed, so the run's artifact and
+ audit accounting stay uniform.
+
+ Proposals are applied strongest first: each is scored once against the
+ run's starting state, then persisted in descending score order (ties keep
+ file order), so when the model files more candidates than the per-run
+ budgets allow, the budgets go to the best-grounded ones rather than the
+ earliest. The score used for persisting is recomputed at that point, so a
+ row inserted for a stronger proposal still counts as "already watched"
+ for a weaker one on the same site."""
+ summaries: list[dict[str, Any] | None] = [None] * len(proposals)
direct_left = max(0, ctx.settings.max_direct_adds)
suggest_left = max(0, ctx.settings.max_suggestions)
seen_targets: set[str] = set()
@@ -1112,44 +1165,21 @@ def apply_proposals(
live_existing = list(ctx.existing)
ctx = dataclasses.replace(ctx, existing=live_existing)
- for proposal in proposals:
- finding = (
- findings[proposal.finding_index]
- if proposal.finding_index is not None and 0 <= proposal.finding_index < len(findings)
- else None
- )
+ # Pass 1 (file order): drop duplicate targets, link each proposal to its
+ # evidence, and score it against the starting state to fix the order.
+ prepared: list[tuple[int, int, WatchProposal, ResearchFinding | None, bool, str]] = []
+ for index, proposal in enumerate(proposals):
if proposal.normalized_target in seen_targets:
- summaries.append(_summary(proposal, "rejected", "duplicate target in this run"))
+ summaries[index] = _summary(proposal, "rejected", "duplicate target in this run")
continue
seen_targets.add(proposal.normalized_target)
+ proposal, finding, supported, linked_note = _link_evidence(proposal, findings, ctx)
+ rank = classify(proposal, finding, ctx).score
+ prepared.append((-rank, index, proposal, finding, supported, linked_note))
+ prepared.sort(key=lambda item: (item[0], item[1]))
- linked_note = ""
- cited_term = match_vocab(proposal.grounding_entity, ctx.vocabulary)
- given = proposal.finding_index
- given_valid = given is not None and 0 <= given < len(findings)
- if finding is None or not _finding_supports(
- proposal, finding, cited_term[0] if cited_term else "", ctx.vocabulary,
- ):
- # The model routinely omits finding_index, or guesses one that
- # does not concern this source; the finding that does is still
- # the evidence, so link it (a copy: the caller's proposal is
- # left as filed). A cited finding that does not concern the
- # source is never kept as evidence.
- cited_note = ""
- if given is not None:
- cited_note = f" (the cited #{given + 1} did not)" if given_valid else " (the cited index was invalid)"
- auto_index = auto_link_finding(proposal, findings, ctx)
- if auto_index is not None:
- finding = findings[auto_index]
- proposal = dataclasses.replace(proposal, finding_index=auto_index)
- linked_note = f"linked to finding #{auto_index + 1}, which concerns this source" + cited_note
- # A cited finding that does not concern the source still marks the
- # proposal as research-derived (it may be a suggestion) but is never
- # the evidence link shown beside Approve.
- supported = finding is not None and _finding_supports(
- proposal, finding, cited_term[0] if cited_term else "", ctx.vocabulary,
- )
-
+ # Pass 2 (strongest first): budgets, inserts, audit rows.
+ for _rank, index, proposal, finding, supported, linked_note in prepared:
decision = classify(proposal, finding, ctx)
if linked_note:
decision.reasons.insert(0, linked_note)
@@ -1168,9 +1198,8 @@ def apply_proposals(
details={"slug": proposal.slug, "target": proposal.target,
"signal_type": proposal.signal_type, **_policy_stamp(decision, proposal, finding, supported)},
)
- summaries.append(_summary(proposal, "rejected", decision.reasons[-1] if decision.reasons else ""))
+ summaries[index] = _summary(proposal, "rejected", decision.reasons[-1] if decision.reasons else "")
continue
-
cadence, floor, trigger = quiet_defaults(proposal, ctx.priority_terms)
config = dict(proposal.config)
config["_policy"] = _policy_stamp(decision, proposal, finding, supported)
@@ -1199,7 +1228,7 @@ def apply_proposals(
)
except Exception:
logger.exception("watch_policy: insert failed for %s", proposal.slug)
- summaries.append(_summary(proposal, "rejected", "insert failed (see server log)"))
+ summaries[index] = _summary(proposal, "rejected", "insert failed (see server log)")
continue
inserted = ms.get_watchlist_item(new_id, db_path=db_path)
@@ -1218,10 +1247,10 @@ def apply_proposals(
f"Started watching {proposal.slug} — {proposal.rationale[:120] or decision.entity}",
actor="executive", details=details,
)
- summaries.append(_summary(
+ summaries[index] = _summary(
proposal, "added",
f"added (score {decision.score}; {decision.reasons[0] if decision.reasons else ''})",
- ))
+ )
else:
suggest_left -= 1
audit_log(
@@ -1229,14 +1258,15 @@ def apply_proposals(
f"Suggested watching {proposal.slug} — {'; '.join(decision.reasons[-2:])}",
actor="executive", details=details,
)
- summaries.append(_summary(
+ summaries[index] = _summary(
proposal, "suggested",
f"suggested for approval (score {decision.score}; {decision.reasons[-1] if decision.reasons else ''})",
- ))
+ )
if dept_ref is not None and inserted is not None:
suggested_by_dept.setdefault(decision.department, []).append(inserted)
_notify_department_heads(suggested_by_dept, ctx)
- return summaries
+ # Every proposal was given a summary in one of the passes above.
+ return [s for s in summaries if s is not None]
def _notify_department_heads(
diff --git a/packages/core/tests/unit/test_watch_policy.py b/packages/core/tests/unit/test_watch_policy.py
index ce07f060..4072c12e 100644
--- a/packages/core/tests/unit/test_watch_policy.py
+++ b/packages/core/tests/unit/test_watch_policy.py
@@ -355,17 +355,17 @@ def test_apply_honours_budgets_and_duplicate_targets(db: Path) -> None:
target="https://status.stripe.com/feed.atom", grounding_entity="Stripe", finding_index=1),
_proposal(slug="rss-acme-blog"), # third direct → budget → suggestion
_proposal(slug="rss-initech", target="https://initech.com/feed.xml", grounding_entity="Initech",
- finding_index=2),
+ finding_index=2), # not in company data: the weakest → loses the budget
_proposal(slug="rss-globex", target="https://globex.com/feed.xml", grounding_entity="Globex",
- certainty="unsure"), # suggestion budget spent → rejected
+ certainty="unsure"), # a competitor, own source: outranks Initech despite filing last
]
ctx = _ctx(settings=wp.PolicySettings(max_direct_adds=2, max_suggestions=2))
out = wp.apply_proposals(proposals, findings, ctx, db_path=db)
assert [o["outcome"] for o in out] == [
- "added", "rejected", "added", "suggested", "suggested", "rejected",
+ "added", "rejected", "added", "suggested", "rejected", "suggested",
]
assert "duplicate" in out[1]["result_preview"]
- assert "budget" in out[5]["result_preview"]
+ assert "budget" in out[4]["result_preview"]
# The caller's context is not mutated by the run.
assert ctx.existing == []
@@ -1127,3 +1127,36 @@ def test_auto_link_prefers_the_finding_that_cites_the_source() -> None:
stranger = _proposal(slug="stock-intc", signal_type="stock", target="INTC", grounding_entity="Initech Holdings",
finding_index=None)
assert wp.auto_link_finding(stranger, findings, ctx) is None
+
+
+def test_budgets_go_to_the_strongest_proposals_not_the_earliest(db: Path) -> None:
+ """The dev run that motivated this: two score-3 suggestions filed first
+ took the whole suggestion budget, and a score-4 Finance watched-entity
+ proposal filed third was rejected as over budget. Proposals are now
+ applied strongest first; summaries keep file order."""
+ ctx = _dept_ctx(settings=wp.PolicySettings(max_direct_adds=2, max_suggestions=2))
+ # Two query watches (always suggestions) grounded in a competitor and a
+ # vendor: score 3 each. Brex on its own status page, a Finance watched
+ # entity, high-confidence finding: score 4, marked unsure.
+ weak_a = _proposal(slug="q-globex", signal_type="query", target="Globex pricing moves",
+ grounding_entity="Globex", finding_index=0)
+ weak_b = _proposal(slug="q-stripe", signal_type="query", target="Stripe outage history",
+ grounding_entity="Stripe", finding_index=1)
+ strong = _brex_proposal(finding_index=2, certainty="unsure")
+ findings = [
+ _finding(title="Globex cuts prices", summary="Globex cut list prices 10%.", confidence="high",
+ relevant_urls=["https://globex.com/pricing"]),
+ _finding(title="Stripe outage", summary="Stripe had a two-hour outage.", confidence="high",
+ relevant_urls=["https://status.stripe.com/incidents/9"]),
+ _brex_finding(),
+ ]
+ out = wp.apply_proposals([weak_a, weak_b, strong], findings, ctx, db_path=db)
+ by_slug = {o["slug"]: o for o in out}
+ assert [o["slug"] for o in out] == ["q-globex", "q-stripe", strong.slug] # file order kept
+ assert by_slug[strong.slug]["outcome"] == "suggested"
+ rejected = [slug for slug, o in by_slug.items() if o["outcome"] == "rejected"]
+ assert len(rejected) == 1 and rejected[0] in ("q-globex", "q-stripe")
+ assert "suggestion budget spent this run" in by_slug[rejected[0]]["result_preview"]
+ # A later, stronger proposal on the same site as an inserted one still
+ # counts it as already watched (the score is recomputed at insert time).
+ assert ms.get_watchlist_item_by_slug(strong.slug, db_path=db) is not None