<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Journalint. - Medium]]></title>
        <description><![CDATA[Journalism Intelligence Platform powered by AI - Medium]]></description>
        <link>https://medium.com/journalint?source=rss----c0bdab0e7ea2---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Journalint. - Medium</title>
            <link>https://medium.com/journalint?source=rss----c0bdab0e7ea2---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:22:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/journalint" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A graph is a lead, not a finding]]></title>
            <link>https://medium.com/journalint/a-graph-is-a-lead-not-a-finding-91dcee6e80d5?source=rss----c0bdab0e7ea2---4</link>
            <guid isPermaLink="false">https://medium.com/p/91dcee6e80d5</guid>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[data-journalism]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Esteban Sánchez]]></dc:creator>
            <pubDate>Thu, 29 Oct 2026 10:40:45 GMT</pubDate>
            <atom:updated>2026-10-29T10:43:16.620Z</atom:updated>
            <content:encoded><![CDATA[<p>Published on The JournalInt blog</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TsSqS6yGDN20TeBqVCmg9A.png" /></figure><h3>The graph is where the work starts</h3><p>Anyone who sees a relationship graph for the first time tends to read it as a conclusion: these people are connected, this company pays that one, here is the plot. It is an understandable reading, but an incomplete one. A graph is where an investigation starts. It shows you where to look.</p><p>The problem is that getting to that starting point costs a lot. Before you can investigate, you have to structure: read every document, note who appears and under what name, who does what to whom, and in which sentence it says so. With three documents it is an afternoon. With three hundred it is weeks that almost nobody has. And those weeks never show up in the final report: nobody reads the hours it took to find out that “the director” of one page and the full name in another are the same person.</p><blockquote><em>In Muck Rack’s State of Journalism 2026 report, 42% of journalists say they only sometimes, rarely or never have the time to do their work the way they want to.</em></blockquote><p><strong>One of the reasons JournalInt exists is to cut that part down. It does not investigate for you. It reduces the time spent structuring so that you have more time left to investigate.</strong></p><h3>What it does today</h3><p>You upload your documents (PDF, DOCX, plain text or Markdown), or paste a web address. Extraction happens in two stages, with a person in between.</p><p>First, an AI model recognises entities: people, organisations and places. Then you review them and confirm them.</p><p>After that, with the entities confirmed, the model proposes the relationships between them, drawn from normalised relationship types rather than free text. Each relationship is stored with the literal sentence from your document that supports it, and JournalInt checks that the sentence is in the text before showing it to you.</p><p>We measure what it does. In an internal evaluation on a reference set, entity extraction reached a precision of 95%, a recall of 93%, and 0% invented quotes.</p><p>Want to help us improve these numbers? <a href="https://www.journalint.com/en#early-access">Request your invitation here</a> and try JournalInt with public material.</p><h3>What the time you save is for</h3><p>If the graph arrives sooner, the work that matters starts sooner. That work comes in three kinds.</p><p>The first is cross-checking. Each relationship takes you to a specific sentence in a specific document. That sentence does not prove that what it says is true: it proves that the document says it. From there, you need to look for other sources that confirm or contradict it.</p><p>The second is following second-order relationships or longer chains. One document says A pays B. Another says B hires C. Neither mentions A and C, but in the graph the path appears, because B is the same node in both. Those chains are hard to spot when you read document by document, and that is often where the story is.</p><p>The third is seeing who the actors and the narratives that carry the most weight are: who is connected to almost everyone, who links two groups that never touch each other. Today the journalist does that reading by looking at the graph. The metrics that would calculate it automatically (centrality, communities, bridge entities).</p><p><strong>And this is the second thing JournalInt was built for: making your investigation more accurate, more agile and better informed.</strong></p><h3>A lead, not a finding</h3><p>Our website has a line that sums up how we want the product to be used: an extraction is a lead, not a finding. The quote takes you to the exact sentence in your document. Checking that claim against other sources, and deciding what gets published, is still the journalist’s job.</p><p>What JournalInt wants to take off your hands is the mechanical part: the hours of reading, noting and matching names before you can start asking questions. What remains afterwards is yours: cross-checking, following the long paths, deciding who matters and what is true.</p><p>The beta is free and by invitation, and during the beta only public or already published material may be uploaded: no leaks and no drafts. If you want to try it with your own documents, you can request an invitation at <a href="https://www.journalint.com/en?utm_source=social&amp;utm_medium=medium&amp;utm_campaign=rrss-2026-w44#early-access">journalint.com</a>.</p><p>This text was written with the help of AI tools and under human supervision.</p><p><em>Originally published at </em><a href="https://www.journalint.com/?utm_source=social&amp;utm_medium=medium&amp;utm_campaign=rrss-2026-w44"><em>https://www.journalint.com</em></a><em> on October 29, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91dcee6e80d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/journalint/a-graph-is-a-lead-not-a-finding-91dcee6e80d5">A graph is a lead, not a finding</a> was originally published in <a href="https://medium.com/journalint">Journalint.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I moved my dev plan to Notion connected with Claude Code]]></title>
            <link>https://medium.com/journalint/why-i-moved-my-dev-plan-to-notion-connected-with-claude-code-b2407580f456?source=rss----c0bdab0e7ea2---4</link>
            <guid isPermaLink="false">https://medium.com/p/b2407580f456</guid>
            <category><![CDATA[knowledge-graph]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Esteban Sánchez]]></dc:creator>
            <pubDate>Mon, 10 Aug 2026 13:54:17 GMT</pubDate>
            <atom:updated>2026-08-10T13:54:56.876Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why I moved my development plan to Notion connected with Claude Code</h3><blockquote>The project is <a href="https://www.journalint.com/">JournalInt</a>, a knowledge-graph tool for journalists and investigators.</blockquote><p>Nineteen phase files. One hundred and thirty-five tasks. Thirty-six decisions. All of it written in Markdown, and by the time I looked properly, the README alone was carrying four pointers to things that no longer existed.</p><p>So on 6 August I moved the whole plan into Notion. This is what I learnt from doing it.</p><h3>A plan in Markdown is a notebook, not a system</h3><p>Markdown is very good at prose and very bad at state.</p><p>A phase file can describe a task beautifully. What it cannot do is answer a question. Which tasks are blocked right now? What does finishing task 6.4 actually unblock? Which specifications does decision D25 govern, and are any of them already half-implemented? Every one of those questions meant opening several files and holding the answer in my own head, which is precisely the thing I was trying to stop doing.</p><h3>The connection is not the MCP server, it is the four skills</h3><p>Connecting Notion to Claude Code is a few lines in .mcp.json. That part takes minutes and changes very little on its own. You end up with an agent that can technically reach your workspace, and no shared idea of when it should.</p><p>What changed the way I work is four repository-scoped skills that make the workspace the default route rather than an option.</p><ul><li>notion-read reads a task in full before any code is written, along with its phase, because the acceptance criteria that no single task covers live there.</li><li>notion-task moves work through the pipeline and closes it with the commits and the pull request.</li><li>notion-bug handles the bug I find halfway through implementing something else: stop, write it down, then carry on with what I was doing.</li><li>notion-doc handles documentation and decisions.</li></ul><p>The part I did not expect to matter as much as it does is the authority boundary. The agent changes workflow state freely, without asking: moving a task, filling start and end dates, ticking a definition-of-done box that is genuinely met, recording commits. Content is different. If a task’s context section no longer matches the code, the instruction is to report it and wait, never to silently follow a stale specification and never to quietly rewrite the specification to match the code. Knowing which of those two things is happening is the difference between a plan I trust and a plan I have to re-read.</p><h3>Blocked and depends on are not the same thing</h3><figure><img alt="A simple image describing the depends on and the blocked of a task." src="https://cdn-images-1.medium.com/max/535/1*OkkjzlqrM1QEk-3T7FWlPQ.png" /><figcaption>One task, two kinds of edge. Depends on is ordinary sequencing. Blocked by points at an unresolved decision, and the red rollup is what stops the agent from starting.</figcaption></figure><p>This is the detail that convinced me Markdown was never going to be enough.</p><p>Depends on points at another task. It is ordinary sequencing, and setting it writes the inverse automatically, so every task can also answer what finishing it unblocks. That inverse is the foresight I did not have before: not just what is next, but what opens up when it lands.</p><p>Blocked by points at a decision, and it is a categorically different state. Nobody unblocks it by shipping code. It needs an answer from me. A rollup reads the linked decision&#39;s status onto the task, and the rule is flat: never implement a task whose blocker status is pending. Stop and ask.</p><p>In a phase file, both of those were a sentence in a paragraph, indistinguishable from each other and invisible unless you happened to read that paragraph. As two different relation types they are queryable, and the distinction survives me forgetting about it.</p><h3>What actually changed</h3><p>The headline version of this would be that I connected an AI agent to my project management tool. That is the least interesting part of it. Anyone can do that in an afternoon.</p><p>What changed is that the plan and the code stopped being two artefacts I reconcile by hand. I can specify a task with its dependencies and its blocking decision in a form that holds that structure. I can file a bug in the middle of implementing something else without derailing what I was doing. I can ask what is blocked, what a decision governs, what a completed task unlocks, and get an answer from live data rather than from my memory of a file I wrote six weeks ago.</p><p>For a project built mostly by one person with an agent, that is not administrative overhead. Milestones stay honest because status is derived rather than declared, and the next move is visible rather than reconstructed. Traction and foresight, from having management and engineering pointed at the same source.</p><blockquote><strong>Keeping the project organised used to take the hours I wanted for building it. It costs a fraction of that now, and the difference goes straight back into the code.</strong></blockquote><blockquote>This text was written with the help of AI tools.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2407580f456" width="1" height="1" alt=""><hr><p><a href="https://medium.com/journalint/why-i-moved-my-dev-plan-to-notion-connected-with-claude-code-b2407580f456">Why I moved my dev plan to Notion connected with Claude Code</a> was originally published in <a href="https://medium.com/journalint">Journalint.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s Journalint.]]></title>
            <link>https://medium.com/journalint/its-journalint-61a3739fabb1?source=rss----c0bdab0e7ea2---4</link>
            <guid isPermaLink="false">https://medium.com/p/61a3739fabb1</guid>
            <category><![CDATA[economics]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[politics]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Esteban Sánchez]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 10:26:28 GMT</pubDate>
            <atom:updated>2026-06-01T10:27:55.095Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This first article covers what Journalint. is, why graphs matters in investigations and what AI can bring to journalism.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JZB3w0xl2Sv02Rqsp8uY6g.png" /><figcaption>Cover image for Journalint.</figcaption></figure><p>There is a scene that appears again and again in films about investigations. A big wall full of faces, notes, newspapers, company names and places, all connected with red thread. It is dramatic because it captures something true.</p><blockquote>Stories are rarely linear, they are networks.</blockquote><p>People influence people, companies hide behind companies, narratives travel through intermediaries, and what matters is often not a single fact but the pattern between many facts.</p><p>Journalint is being built as a tool for journalists and investigators who need to follow stories <em>effeffin</em> (efficiently, effectively and intelligently). At its core, it uses knowledge graphs and AI to help turn scattered material into structured intelligence.</p><h3>Journalism already has the data, but not the right lens</h3><p>Investigative work usually does not fail because there is no information. It fails because there is too much of it, and because it arrives in forms that are difficult to connect.</p><p>In this AI era, spent time in checking names, tracing ownwership structures or detecting intention in the comunications is outdated,</p><blockquote>in this era uncovering what is hidden with trusted information is the key.</blockquote><p>This is the problem Journalint is trying to solve. Not by replacing the journalist, but by giving the investigation a better lens.</p><h3>Why graphs matter</h3><p>A graph is not just a nice visual interface. It is a way of thinking.</p><p>This is one of the ideas that has stayed with me since I studied graphs and the propagation of misinformation during a master’s in complex systems physics. From the mathematical roots of graph theory to modern network science shaped by figures such as Albert-László Barabási, this field has given us better ways to understand how complex systems behave. That period changed the way I looked at stories.</p><blockquote>Disinformation does not spread randomly. Power does not move randomly. Corruption rarely works in a straight line. These are networked phenomena, and if we want to understand them properly, we need tools that can handle networks.</blockquote><p>That is the intellectual foundation behind Journalint.</p><p>That matters because society itself behaves like a complex system. Influence is not distributed evenly. Some actors are bridges. Some are amplifiers. Some remain invisible until you see the network around them.</p><h3>What AI changes</h3><p>We have been able to detect some forms of relationship for a long time. If one document says a company owns another, or a person is listed as a director, that is already useful structured information.</p><p>But the recent wave of AI changes the scale and the type of relationships we can work with.</p><p>Now it is much more realistic to extract entities and connections across large volumes of documents, and to go beyond simple ownership or part-whole relationships. We can start identifying patterns of influence, repetition, contradiction and narrative alignment. That opens a different way of understanding stories.</p><p>For me, this is where the paradigm really shifts. The question is no longer only, “Can we collect enough information?” The question becomes, “Can we surface the relationships that actually shape the story?”</p><p>That is why I do not see Journalint as just another productivity tool for newsrooms. I see it as an intelligence layer for investigations.</p><h3>Why now</h3><p>I have been carrying this idea for a long time but tools such as GitHub Copilot and Claude have dramatically reduced the distance between an idea and a working product. They have made it possible for one person to move faster, test concepts sooner and build with a level of ambition that would have been much harder a few years ago.</p><p>In that sense, I sometimes think of myself as the AIrquitect of Journalint. The vision is human, the questions are journalistic, the direction comes from lived curiosity, but AI makes the construction velocity real.</p><blockquote>And because of the industrialization of the missinformation, the moment feels urgent to give to people better tools not as a luxury, but as infrastructure.</blockquote><h3>What I want Journalint to become</h3><blockquote>I want Journalint to help journalists see what is hidden in plain sight.</blockquote><blockquote>I want it to help them map actors and relationships faster.</blockquote><blockquote>I want it to help them understand how a narrative evolves, who is pushing it, and where the real leverage points are.</blockquote><p>Journalint is still early, but the purpose is already clear: to bring more intelligence, more clarity and less noise into investigative journalism.</p><p>If you want to follow what comes next, stay tuned at <a href="http://www.journalint.com/"><strong>www.journalint.com</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61a3739fabb1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/journalint/its-journalint-61a3739fabb1">It’s Journalint.</a> was originally published in <a href="https://medium.com/journalint">Journalint.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>