kanchi-dividend-review-monitor

---
name: kanchi-dividend-review-monitor
description: Use when monitoring dividend portfolios for Kanchi-style forced-review triggers (T1-T5), converting anomalies into OK/WARN/REVIEW states, or running periodic dividend risk checks.
category: Portfolio
version: 1.0.0
tools: []
---

# Kanchi Dividend Review Monitor

Detect abnormal dividend-risk signals in a portfolio and route them into a human review queue. Treat this as anomaly detection, not automated trade execution — never auto-sell based only on machine triggers; always create WARN or REVIEW evidence for human confirmation first.

## When to Use

Use for daily/weekly/quarterly anomaly detection on dividend holdings, forced review queueing for T1-T5 risk triggers, 8-K/governance keyword scans tied to portfolio tickers, or a deterministic OK/WARN/REVIEW read before any manual decision — including requests phrased in Japanese as dividend-cut detection (減配検知), 8-K governance monitoring (8-Kガバナンス監視), dividend safety monitoring (配当安全性モニタリング), or review-queue automation (REVIEWキュー自動化).

## Inputs

Collect, per ticker, in one normalized dataset: dividend data points (latest regular dividend, prior regular dividend, missing/zero flags); coverage fields (FCF, FFO, or NII vs. dividends paid, and their ratio history); balance-sheet trend fields (net debt, interest coverage, buybacks vs. dividends); filing text snippets, especially recent 8-K or equivalent alert text; and operating trend fields (revenue CAGR, margin trend, guidance trend). At minimum, provide ticker, instrument type, and the latest and prior regular dividend.

## State Machine

- **OK** — no action.
- **WARN** — add to the next check cycle and pause optional adds.
- **REVIEW** — open an immediate human review ticket and pause adds.

## Monitoring Cadence

- **Daily** — T1 (dividend cut/suspension) and T4 (SEC filing keyword scan, 8-K oriented).
- **Weekly** — T3 (proxy credit stress checks).
- **Quarterly** — T2 (coverage deterioration) and T5 (structural decline scoring).

## Flat-Dividend Cadence Caveat

When a trigger fires only because the latest regular dividend equals the prior regular dividend (a freeze flag, sometimes labeled T6), treat it as a WARN for cadence confirmation, not proof of dividend deterioration — many quarterly payers repeat the same dividend for several quarters between annual raise cycles. Phrase this as "confirm next dividend-growth cadence / pause optional adds until checked," and avoid implying a cut or broken thesis unless T1-T5 evidence also supports escalation.

## Workflow

**Run the rule engine.** Map each ticker to OK/WARN/REVIEW based on the T1-T5 trigger matrix and its thresholds.

**Prioritize and deduplicate.** If multiple triggers fire on the same ticker, keep all findings for the audit trail, but escalate the final state to the highest severity only, and store each trigger reason as single-line evidence.

**Generate human review tickets.** For each REVIEW ticker, include the trigger IDs and evidence, the suspected failure mode, and the required manual checks for the next decision.

## SEC Filing Guardrail

When pulling live SEC filings, use a compliant User-Agent string (name + email), cache and throttle requests, and respect SEC fair-access guidance. When upstream filing snippets are empty, use SEC's ticker-to-CIK mapping and each company's EDGAR submissions feed to enumerate recent 8-K/8-K-A filings, then scan the primary filing documents for the T4 keyword family: Item 4.02, non-reliance, restatement, material weakness, SEC investigation, subpoena, going concern, auditor resignation, internal control. Record the scan window, the recent 8-K count, and whether any keyword hits were found — treat "no hits" as a narrow T4 scan result, not full governance clearance.

## Output

Return, in chat: a queue with summary counts and ticker-level findings; a quick-triage dashboard view; and an explicit list of immediate REVIEW tickets.

## Multi-Skill Handoff

Consume ticker universe and baseline assumptions from `kanchi-dividend-sop`; feed REVIEW results back to it for re-underwriting and position-size review; share account-type context with `kanchi-dividend-us-tax-accounting` when risk events imply account-relocation decisions.