How it's made
AI Vector publishes every weekday morning. Each issue starts with The 30-second read, a summary of everything in it, then The Pulse, the day's most important story. Three sections follow: The Big Picture for leaders, Hands-On for practitioners, Currents for early signals. Every story has a headline, a one-line take saying what it means, a summary, and a link to its source.
Open source
AI Vector is open source. The code that builds each issue, the source list, the scoring rubric, and the full history of every issue are in one public repository: github.com/armanabrahamyan/ai-vector-newsletter
The code is MIT-licensed. The issue text is copyright.
Where the stories come from
AI Vector reads about ninety feeds each morning: AI labs, research groups, regulators, practitioner blogs, and community forums. Nothing is scraped from websites.
Many feeds report the same news, so articles about the same story are grouped and the story appears once. The comparison covers the previous two weeks: an article already used is never used again, and a story covered before is marked as a follow-up.
How a story is chosen
Each group is scored against a written rubric: significance, hands-on usefulness, big-picture relevance, financial-services impact, freshness. A normal morning produces four to five hundred groups; about a dozen are published, written by a language model following written rules for headlines, takes, and summaries.
Two checks then run. The first compares every claim in a headline or summary with the source article and flags anything the source does not support or contradicts. The second reads the whole issue: whether the right story leads, whether stories repeat from earlier days, whether the financial-services angle is real.
What the machine does and what a person does
Every issue is either read and approved by a person before it goes out, or published under rules that person wrote, checks afterwards, and can switch off. An issue is held if a story makes a claim its source contradicts, or if a check did not run.
The financial-services angle appears when a story has one: some days that is half the issue, some days none.
Corrections
When an issue is wrong, it is corrected and published again with a revision number. No. 34 becomes No. 34.1. The correction goes into the issue itself, not into a separate notice. Factual errors are corrected on the day they are confirmed. A story that should not have run is removed.
Privacy
Visits are counted with GoatCounter, which stores no cookies and no personal data.
Contact
Corrections, disagreements, and sources worth adding go to Arman Abrahamyan, who approves every issue before it publishes: armanabrahamyan.com