Today we're opening the journal at /intel/journal/ — a dated, running-log companion to the static
brief library. The briefs are anchored reference documents (designation packages, cross-jurisdiction
coverage, 50% Rule triage). The journal is the other kind of artifact: shorter entries about what
moved, what we noticed, and why a reader who follows us weekly might want to care this week.
What ends up here
Change digests. When the pipeline detects a meaningful shift — a new OFAC designation cascading through our graph, a UBO shuffle on a sanctioned holding, an occupied-territory discovery pass turning up a new cohort — we write it up as a dated entry. The machine surfaces the event; the analyst narrates what it means.
Coverage notes. If we change methodology, expand a scraping cascade, add a new jurisdiction feed, or deprecate a source, that's a journal entry. Transparency about what we're measuring is part of the product.
Operational notes. If a source goes quiet, a scraper goes down, or a rebuild changes counts in a visible way, we'll say so here. Better to own an outage than to paper over a dip in the KPI strip.
What doesn't end up here
Raw speculation, hot takes, or commentary on individual sanctions decisions. The journal is grounded in what the data shows. When we have a view on a designation package, we publish it as a brief — with citations, INNs, and recommended scope — not as a blog post.
Cadence
Weekly when the pipeline produces something worth writing about, less often when it doesn't. No content for the sake of content.
Subscribe
The journal posts stream through the same RSS feed as the free briefs at /intel/feed.xml. If you use an RSS reader, add that URL and you'll get both the briefs and the journal entries.
If you have feedback on what you'd like to see covered — or find an error in a post — email derek.linz@linzalytics.com.