Argumentation

You've been in the argument. You know the one. Someone says something that's clearly wrong, you can feel it in your chest, but the words don't come. The moment passes. You think of the perfect response two hours later in the shower.

retflo exists so that doesn't keep happening.

When you know something is wrong but can't explain why

Your boss tells you to be grateful for what you have. Your coworker repeats the line about how anyone can make it if they work hard enough. Your uncle goes off at Thanksgiving about how the free market sorts everything out. You know it doesn't hold up. You can point to your own life as evidence. But knowing something is wrong and being able to explain the mechanism are two different skills, and most people never get taught the second one.

retflo gives you the mechanism. Pick the node that matches what you're hearing. "Profit is earned." "Human nature is selfish." "Without the state there'd be chaos." Each one has the structural response already mapped out, with the reasoning laid bare and the connections to related arguments traced. You're not memorizing a comeback. You're understanding why the argument fails.

The volume problem

Bad arguments win by repetition. The same handful of claims flood every platform, every comment section, every family group chat. They're easy to say, hard to answer on the spot, and they sound reasonable if nobody pushes back. Most people don't push back because they'd need twenty minutes to explain what's wrong, and by then the conversation has moved on.

retflo is the counterweight. When you've internalized the structure of these arguments, you don't need twenty minutes. You need two sentences. The structural response is already built. You just have to deliver it. And if the conversation goes deeper, you have the full chain of reasoning behind you, not a memorized script, but an actual understanding of where the argument breaks down and what it's covering for.

Scaling the intensity

Not every argument calls for the same approach. Sometimes you're talking to a friend who's repeating something they heard and hasn't thought about it much. Sometimes you're dealing with someone who genuinely believes what they're saying and you want to plant a seed without burning the relationship. Sometimes you want to hit harder.

The style guide helps calibrate this. It covers how to adjust delivery depending on the situation, the audience, and what you're actually trying to accomplish. Gentle nudges and full structural arguments use the same underlying reasoning. The difference is in how much you surface and how directly you say it. You decide.

That friend who you don't want to alienate? You can raise a question that sticks with them without making it feel like a lecture. That uncle at Thanksgiving? You can choose exactly how close to home you want to hit. The substance is the same either way. The delivery is yours to control.

Debate and structured argument

For anyone in formal debate, the protocol is a reference library. Every node includes citations, historical context, and connections to related arguments across seven domains. You can trace an argument from economics through governance through human nature and back, with the logical structure visible at every step.

The visualizer makes those connections tangible. You can see how "markets are efficient" connects to "profit is earned" connects to "hierarchies are natural" and understand the shared assumptions underneath. That kind of structural awareness is what separates someone who can answer one objection from someone who can anticipate the next three.

When the stakes are personal

Some of the most important arguments happen when the stakes are personal. A student whose teacher casually repeats talking points about meritocracy or natural hierarchies. A teenager watching misinformation go unchallenged in their community. These situations call for something more than "well, actually." They call for a response that holds up, that can be explained clearly, and that the person delivering it actually understands.

retflo puts the real story within reach. When bad claims go unchallenged, they become the default. When someone has the structural response ready and delivers it clearly, the dynamic shifts. The point isn't to win the argument in the moment. The point is to put accurate reasoning into spaces where it's been missing.

Why it works

All of this depends on one thing: the substance is sound. The protocol maps 59 nodes across 260 connections, and every response is structurally grounded. You can challenge any node, push back on the reasoning, trace the logic yourself. It holds up because it was built to hold up, not to persuade, but to be correct.

That's what makes everything else possible. The gentle nudge works because the reasoning behind it is solid. The full structural argument works because every link in the chain has been tested. The kid in debate club wins because they understand the argument, not because they memorized a rebuttal.

Start with the quickstart guide to load the framework into a language model, or browse the nodes directly and pick the argument you keep running into. See also: Education, Research, AI.