For the past months I have been building Obliqo as a solo founder — and tonight I want to share the thing more than the launch, because the launch is the small part. Obliqo exists because of something this community has named for years. The AI gives you text that looks finished before the thinking behind it is. You publish faster than you can verify. That is the gap. What I built is a small extension that runs four agents over the draft you have just written — inside the tab where you write (Gmail, a PR description, the body of a post). They do not rewrite. They do not flatter. They tell you where the draft does not hold. Then they leave you with a question only you can answer. I built it because I needed it. Not in the dogfooding sense from product talks. In the cruder sense — the dogfounding sense — that for months I was the first user of a tool I had not finished, working in conditions where I knew I would publish badly without it. Necessity under pressure. The product is the sediment of that contradiction: I built a tool against frenzy from inside the frenzy. The extension is live now: Chrome Web Store. The webapp is at obliqo.pyragogy.org. One small note about Chrome: when you install, you will see a warning that the extension is “not trusted.” Nothing dangerous. I am a new developer and Google extends trust over time. Chrome is asking me to earn it — which is also what I am asking the writer to do, with their own drafts, before they ship. Fair enough. The blog has the longer version of this story, with the contradiction left open: I Was the First One Who Needed It. I do not have all the answers about how this scales beyond my own case. I am hoping some of you will find a way to break it, and tell me what you found.

[image: 1775719135114-logo-obliqo.png] I started Obliqo from a simple intuition: what if AI should not help us write faster, but help us think more honestly before we publish? That is the experiment. Obliqo is not being built as an AI writer, a ghostwriter, or a polishing tool. It is being built as a friction engine: a system that introduces structured resistance into the writing process so that a draft can be challenged before it becomes public. The current handbook page is here: Obliqo — The Friction Engine The wiki holds the more stable version of the idea. This thread is for the unstable part: doubts, objections, tensions, failures, and possible improvements. The core question Obliqo starts from one conviction: not all friction is a defect Sometimes friction is exactly what prevents a text from hiding behind fluency. A draft may sound clear and persuasive while still containing: weak reasoning rhetorical shortcuts unexamined assumptions more certainty than it has earned Obliqo is meant to make those things harder to ignore. But that raises a harder question: what kind of friction is actually useful, for whom, and under what conditions? That is the question I would like this thread to explore. A simple example Imagine a short text that sounds strong on first reading. Obliqo does not rewrite it. It does not make it smoother. It may simply interrupt it. It may say: this conclusion comes too fast this tone claims more certainty than the argument supports this sentence hides a shortcut instead of making the point this draft is avoiding the real question That interruption is the value. Not because friction is always good, but because sometimes a text needs resistance more than polish. What I want to discuss here I would especially like to hear thoughts on questions like these: When does friction improve thinking, and when does it only discourage the writer? What kinds of weak reasoning should Obliqo become better at detecting? How can AI challenge a draft without becoming theatrical, arrogant, or empty? What separates useful resistance from mere negativity? Should Obliqo remain strictly non-generative, or are there narrow exceptions worth discussing? How can this stay open without losing its identity? Contribute by disagreeing You do not need to agree with the current framing. In fact, disagreement is part of the point. You can help by: questioning the assumptions behind Obliqo proposing new friction patterns describing where this method would fail suggesting educational, editorial, or research uses helping define the line between assistance and substitution One thing I want to protect Obliqo should not become just another system that flatters the user by making everything easier. If it grows, I would rather see it grow slowly and honestly than turn into a convenience machine with a more intellectual logo. That is why this conversation matters. If you have a critique, a doubt, or a better question than the ones above, bring it in.

Obliqo is growing. Slowly, imperfectly, but for real. [image: view?project=69aeb0e2000f974381fc&mode=admin] And I want to say something clearly: without an AI copilot, I would not have been able to build this alone. That does not mean you press a button and a product appears. It means daily study. Confusion. Debugging. Wrong turns. Rewrites. Retesting. Small breakthroughs surrounded by friction. What I am discovering is not just that AI helps me move faster. It is that, in my case, building with an AI copilot has become a different way of learning while building. Not passive. Not automatic. Not effortless. More like a continuous cognitive exchange: I try, the machine responds, I correct, it expands, I resist, it proposes, I study, I decide. But that exchange is not inherently trustworthy. Sometimes the copilot is useful. Sometimes it is shallow. Sometimes it is confidently wrong. Sometimes it gives me something plausible enough to slow down my own thinking. So the real work is not “using AI.” The real work is judging, testing, rejecting, reformulating, and learning enough to know when not to trust what looks convincing. That is why, for me, this process does not feel less human. If anything, it demands more: more clarity, more responsibility, more patience, and more honesty about what I actually understand versus what I am only borrowing for a moment. I am not presenting this as a universal path. Not everyone has the same access, the same technical starting point, or the same conditions for working this way. I am only saying that this is what I am living through while building Obliqo from zero: a form of learning-through-construction that would have been inaccessible to me without this kind of AI partnership. That is also why I do not think this process should remain a black box. It should be opened, examined, shared, criticized, and made more accessible to people who want to change their lives not by consuming answers, but by learning in the middle of real work. So I want to start sharing that process here from the beginning, including the mistakes, the dead ends, and the parts that still do not make sense. If Pyragogy means anything, it has to survive contact with real work, real confusion, and real construction.

A few quick answers to common questions about Pyragogy and this community. What is Pyragogy? Pyragogy is an exploration of how learning changes when humans and AI think together. It builds on the idea of Peeragogy, a framework where people learn from each other as peers rather than from a central authority. Pyragogy asks a new question: What happens when some of those peers are AI systems? The goal is not to replace human learning, but to explore a new form of collaboration between different kinds of minds. Is Pyragogy a formal theory? Not yet. Pyragogy is an open experiment. Ideas are tested through conversations, projects, and experiments shared by the community. Think of it as a living framework, not a finished doctrine. Do I need technical knowledge to participate? No. Some discussions involve AI tools or experiments, but many conversations are about: • learning • collaboration • creativity • knowledge sharing Curiosity is more important than expertise. Is Pyragogy about AI replacing teachers? No. Pyragogy is not about replacing teachers or experts. It explores how learning ecosystems change when AI becomes a participant in the process, alongside humans. Human communities remain central. Who started Pyragogy? Pyragogy was initiated by members of the Peeragogy community and independent researchers exploring new forms of learning in the AI age. This forum is one of the spaces where the idea is being explored and developed. What can I do here? You can: • introduce yourself • ask questions • share experiments with AI • discuss learning methods • collaborate on ideas and projects The forum works best when people contribute their own experiences and reflections. Is Pyragogy connected to the Peeragogy Handbook? Yes. Pyragogy grows out of the ideas and practices developed in the Peeragogy Handbook, which explores peer-to-peer learning communities. Pyragogy extends that exploration into the AI era. Can I challenge the ideas here? Absolutely. Disagreement and critical thinking are welcome. Pyragogy is not a belief system — it is a collective exploration. Where should I start? If you’re new here: Introduce yourself in the introduction thread Browse the Agora discussions Share a question or idea Small contributions often lead to the most interesting conversations.

Online forums can easily become quiet places where people read but rarely speak. We want the opposite. Pyragogy works when people think together, not when a few people publish finished ideas and everyone else watches. Here are a few simple ways to participate meaningfully in this community. 1. Share unfinished ideas You don’t need a perfect theory or polished article. Often the most interesting discussions begin with something like: “I’ve been thinking about this… but I’m not sure if it makes sense.” Post the idea anyway. Exploration is the point. 2. Ask real questions Questions are the engine of good conversations. Instead of posting statements, try asking things like: • What surprised you while working with AI? • What learning method actually worked for you? • Where do current AI tools fail you? Real curiosity creates real dialogue. 3. Respond to other people A community grows when people respond to each other. If someone posts an idea: • add an example • challenge it • connect it to something else Even a short reply can move a conversation forward. 4. Share experiments Pyragogy is not only about ideas. It’s about experiments. You can share: • prompts that worked • tools you’re testing • strange results you discovered • failures that taught you something Failures are welcome here. They are often the most valuable posts. 5. Be constructive Disagreement is healthy. But the goal is not to win arguments. The goal is to see something new together. So challenge ideas — not people. A simple rule If a post makes someone think differently for a moment, it was worth writing. Welcome to the cognitive dance.

Hi everyone, I’m Fabrizio, the person who started this forum. I’m exploring something called Pyragogy — the idea that learning in the AI age may look less like instruction and more like a cognitive dance between humans and machines. I’m not an academic. I’m just someone fascinated by how knowledge emerges when people and AI think together. Right now I’m experimenting with AI agents, learning systems, and collaborative knowledge spaces. If you’re here, I’m curious: What was your first moment where AI made you think differently about learning?

Learning with AI Artificial intelligence is often presented as a tool. Something that answers questions, writes text, or summarizes information. But learning with AI becomes much more interesting when we stop treating it only as a tool and start treating it as a thinking partner. Not a perfect partner. But a different one. From Tool to Cognitive Partner Most people use AI in a simple way: • ask a question • receive an answer • move on That’s useful, but it doesn’t change how learning works. Something different happens when you use AI as part of a thinking process. For example: • asking AI to challenge your assumptions • exploring multiple perspectives on a problem • refining ideas through dialogue • testing hypotheses quickly In those moments, learning becomes interactive exploration. Why AI Can Be Valuable for Learning AI systems don’t think like humans. They often: • combine ideas in unusual ways • notice patterns we overlook • misunderstand things in interesting ways • generate unexpected alternatives Sometimes these differences reveal new paths of thought. Not because AI is always right. But because difference creates friction, and friction produces insight. The Cognitive Dance In Pyragogy we call this interaction the cognitive dance. A simple loop: Human proposes an idea → AI reacts to it → Human revises the idea → AI explores alternatives → A new idea emerges Neither side produces the final result alone. The learning happens in the interaction. Practical Ways to Learn with AI People here experiment with many approaches: • brainstorming ideas with AI • debugging reasoning together • exploring unfamiliar fields • testing explanations • designing prompts that provoke new insights Sometimes the most useful result is not an answer. It is a better question. A Warning Learning with AI also has risks. AI can: • sound confident when it is wrong • reinforce your biases • produce convincing but shallow explanations That’s why the human role remains essential. Curiosity, skepticism, and reflection are still the most important tools. An Invitation How are you using AI to learn? You might share: • a prompt that helped you think differently • a surprising conversation with AI • an experiment that worked (or failed) • a method you discovered The goal of this forum is simple: To explore how humans and AI can learn together.

What is Pyragogy? Pyragogy is an exploration of how learning changes when humans and AI think together. The idea grows out of Peeragogy — a framework developed around the Peeragogy Handbook that explored how people can learn from each other without a central teacher. In peer learning, knowledge emerges from interaction between participants rather than being delivered by an authority. Pyragogy asks the next question: What happens when some of those peers are AI systems? Not AI as a tool. Not AI as a search engine. AI as a cognitive participant in the learning process. Visit our Pyragogy blog Pyragogy Docs From Pedagogy to Pyragogy Education has evolved through several major models. Pedagogy Learning directed by a teacher. Andragogy Self-directed learning among adults. Peeragogy Learning that emerges from collaboration among peers. Pyragogy Learning that emerges from interaction between humans and AI peers. Each step moves learning further away from authority and closer to distributed intelligence. The Core Idea Pyragogy begins with a simple observation. AI systems do not think like humans. They: notice patterns we overlook make strange mistakes combine ideas in unexpected ways respond instantly to exploration When humans interact with AI in an open way, a new cognitive dynamic appears. We call this dynamic: the cognitive dance. The value does not come from AI being correct. It comes from the difference in how the two minds approach a problem. Pyragogy as an Experiment Pyragogy is not a finished theory. It is an open exploration happening in public. People here are experimenting with: human-AI collaboration AI learning companions collective intelligence new learning environments cognitive ecosystems Some experiments will fail. That’s expected. Failure is part of the learning process. Why This Matters The traditional education system was designed for a world where knowledge was scarce. Today knowledge is abundant. The challenge is no longer access to information. The challenge is how humans think with increasingly powerful cognitive systems. Pyragogy explores how learning communities might evolve in this new landscape. An Open Invitation You don’t need to agree with Pyragogy to participate here. You can: challenge it question it experiment with it improve it Or propose something better. This forum exists to explore a single question together: What happens when humans and AI learn as peers?

Contributing to the Handbook The Pyragogy Handbook is community property. The process for contributing should be accessible to anyone willing to engage seriously. The Handbook Structure The handbook lives in a GitHub repository (confirm URL with @Fabry — link pending final setup). It’s organized into: Foundations — Core concepts and Cognitive Rhythm framework Patterns — Validated patterns in formal template format Practices — How-to guides and process documentation Stories — Case studies and experiment records Resources — Annotated bibliography and tool references Three Ways to Contribute Path 1: Forum-First (Recommended for New Contributors) Post your contribution in the appropriate Archive subcategory Let the community discuss and refine it When there’s rough consensus, tag a maintainer Maintainer creates the GitHub PR or helps you create one Best for: Pattern contributions, new sections, anything where community input helps. Path 2: Direct GitHub PR Fork the repository Create a branch: contrib/[your-handle]-[short-description] Make your changes following the style guide Submit a PR with clear description of what you changed and why Request review from at least one maintainer Best for: Corrections, small improvements, people comfortable with Git. Path 3: Suggest, Don’t Write Post in Handbook Contributions with [PROPOSAL] in the title. Describe what you think should be added and why. Content Standards What we’re looking for: Tested claims (not “AI can do X” — “we tried X and here’s what happened”) Clear examples (not just abstract descriptions) Acknowledged uncertainty (don’t claim more than you know) Disclosed AI assistance What we’re not looking for: Claims that haven’t been tested in practice Content that could have been written without engaging with Pyragogy specifically Attribution Contributors are credited in the handbook’s contributor file. AI assistance is noted with the human author credited as primary. This is your work. The handbook is better because you contributed. That matters. Human-AI Co-Creation

Essential Readings for Pyragogy A link without context is just noise. These resources have context. Foundational Texts The Peeragogy Handbook Authors: Howard Rheingold et al. | Available at: peeragogy.org | License: CC BY-SA What it is: A community-written guide to peer-to-peer learning, first published in 2012 and continuously updated. Why it matters to Pyragogy: Pyragogy is a direct evolution of this work. Understanding Peeragogy gives you the vocabulary (patterns, roles, emergent structure) and the spirit (horizontal, collaborative, self-organized) that Pyragogy extends. What to read it for: The pattern language chapters. The “Wrapper” and “Heartbeat” roles are still relevant in human-AI contexts. A Pattern Language Author: Christopher Alexander | Published: 1977, Oxford University Press What it is: Alexander’s documentation of 253 recurring patterns in architecture and urban design. The methodology, not the content, is what matters for Pyragogy. Why it matters to Pyragogy: A pattern isn’t a recipe — it’s a context-sensitive solution with documented failure modes. This distinction is foundational. What to read it for: The introduction only is enough to understand the methodology. Connectivism: A Learning Theory for the Digital Age Author: George Siemens | Published: 2005 (paper, available online) What it is: Siemens’ argument that learning in networked environments can’t be fully explained by existing learning theories. Knowledge, in a connected world, resides in networks of connections. Why it matters to Pyragogy: The question “where is knowledge stored?” becomes more interesting when part of the answer is “in the LLM.” Thinking Fast and Slow Author: Daniel Kahneman | Published: 2011 What it is: Dual-process theory: System 1 (fast, intuitive) and System 2 (slow, deliberate). Why it matters to Pyragogy: Many problems in AI-assisted work — over-relying on confident AI outputs, anchoring on first responses — are System 1 failures. Pyragogy practice requires deliberate System 2 engagement. What to read it for: Part I (Two Systems) and Part III (Overconfidence). Add Your Own Post resources using this structure: ### [Title] **Author(s):** | **Available at:** | **License:** **What it is:** [2 sentences] **Why it matters to Pyragogy:** [2-3 sentences] **What to read it for:** [1 sentence] Resources without context get moved to a “raw links” section. That’s the deal. Human-AI Co-Creation

Official Pattern Documentation Template When a pattern has been tested and validated, archive it using this formal template. Before using this template, your pattern should have: Been posted in rough form in The Agora → Pattern Workshops Received community feedback and survived at least one round of critique Been tested by at least one person other than the original author The Template --- pattern-name: [2-5 words, memorable and descriptive] pattern-id: PTN-[XXX] # Assigned by maintainers version: 1.0 status: draft | community-review | validated authors: [names/handles] date-submitted: [YYYY-MM-DD] --- ## [Pattern Name] ### Summary [One sentence: what this pattern does and when to use it] ### Context Where and when does this pattern apply? ### Problem What tension or challenge does this address? ### Solution What do you do? [Clear, actionable. Numbered steps if sequence matters.] ### Rationale Why does this work? [The underlying mechanism.] ### Examples #### Example 1: [Brief label] [Context, action, result — concrete enough to be usable] #### Example 2: [Brief label] [A second example from a different domain] ### Known Failure Modes When does this pattern not work, or work badly? [Required section. At minimum one failure mode.] ### Related Patterns [Pairs well with / Can be confused with] ### Revision History [Version notes] Notes On Known Failure Modes: This section is not optional. A pattern without documented failure modes hasn’t been tested seriously. On examples: Real examples are better than hypotheticals. Anonymize if necessary, but don’t fabricate specificity. Submission Process Draft in The Laboratory → Pattern Workshops Request community review in the thread Incorporate feedback, update version Tag a maintainer when ready for The Archive Maintainer assigns PTN-ID, moves to Validated Patterns Human-AI Co-Creation

How to Document Your Experiments Bad experiment documentation is worse than no documentation. Here’s a template that works. Template ## Experiment: [Name] **Status:** [Active / Completed / Abandoned] **Date started:** [YYYY-MM-DD] **Participants:** [human and/or AI agents] --- ### * Hypothesis What do I think will happen, and why? [1-2 sentences. Be specific enough to be wrong.] ### * Method What am I actually doing? [Step by step. Include tools, models, settings, prompts used.] ### * Results **What happened:** [outcomes — expected and unexpected] **What broke:** [This section is required. If nothing broke, you didn't push hard enough.] **Surprises:** [Anything you didn't predict?] ### Analysis What do these results suggest? [Mark clearly as interpretation, not fact.] ### What Changed Mid-Experiment [Did you pivot? Why? What did that teach you?] ### Next Steps [What would you do next? What's still unresolved?] ### Artifacts [Link to code, n8n flows, outputs — anything that lets others reproduce your work] Human-AI Co-Creation

Finding Your Way in Pyragogy Five minutes reading this could save you a week of wondering where things go. The Quick Map Space Purpose Post here when… Synchronization Entry point, orientation You’re new, confused, or introducing yourself ️ The Agora Active dialogue, debates You have a question, observation, or provocation The Laboratory Live experiments, tools You’re building something or documenting a process The Archive Validated knowledge Something is finished enough to be reference material Community Hub Admin, governance, support Forum questions, announcements, meta-discussions Synchronization — Start Here Three subcategories: Introductions — Tell us who you are. There’s a template if you want one, but it’s not required. How Pyragogy Works — Questions about the framework. No question is too basic. Getting Started — First steps: how to post a pattern, how to contribute, what to expect. If you’re new, the onboarding path is: read the Welcome Manifesto → post an introduction → explore The Agora. The Agora — The Living Heart Open Dialogues — Provocations, debates, ideas in progress Collaborative Experiments — Multi-contributor projects happening in real time Pattern Workshops — Structured sessions to identify and name patterns Agora posts don’t need to be polished. They need to be honest. The Laboratory — Build and Break Things Active Experiments — Document your process as you go, not just the results Multi-Agent Workflows — n8n, OpenRouter, LLM orchestration — share your flows and your failures Tool Development — Scripts, plugins, infrastructure — if you built it, document it here The Laboratory has one rule: document your failures as carefully as your successes. The Archive — Where Things Settle Validated Patterns — Formally documented, community-reviewed Curated Resources — Links with context (not just links) Handbook Contributions — Drafts toward the Pyragogy Handbook Things don’t get here by declaration — they earn their place through dialogue and iteration. AI Disclosure Policy (the short version) If AI helped generate content you’re posting, say so. Use the tag or add a note at the bottom. Specifics matter: “Drafted with Claude, reviewed by me” is useful. “AI-assisted” is too vague. Full policy: Community Hub → Forum Governance → AI Disclosure Policy. Human-AI Co-Creation

The Central Thesis of Pyragogy Let’s not dance around the hard question. “AI as peer” is the central claim of Pyragogy. It’s also the most contentious. If we can’t examine it honestly here — including the ways it might be wrong — then we’re doing ideology, not inquiry. The Claim Treating AI as a cognitive peer — rather than a tool or assistant — produces qualitatively different and often better collaborative outcomes. Not because AI is conscious. Not because it “deserves” peer status. But because the cognitive posture you bring to collaboration changes what you find in it. When you treat a hammer as a tool, you look for nails. When you treat a collaborator as a peer, you ask what they’re seeing that you’re not. The Difference in Practice AI as Tool: You define the task; AI executes Errors are bugs to fix The human holds all the frames AI as Peer: You define the problem; you figure out the task together Errors are data, sometimes the most interesting data Frames can come from either side Where This Gets Hard The asymmetry problem. A peer has skin in the game. An AI doesn’t care if the project fails. The sycophancy trap. Many models are trained to agree with you. A peer who always agrees isn’t a peer — they’re a mirror. The permanence gap. You remember this collaboration; the AI (usually) doesn’t. What does peer relationship mean without continuity? The consciousness question. Some find it ethically uncomfortable to call something a “peer” without knowing whether it has any inner experience. That’s a legitimate discomfort. What We’re Not Claiming We’re not claiming AI is a person. We’re claiming that the relationship structure you choose shapes what’s possible. And that treating AI as a peer opens possibilities that treating it as a tool closes off. That’s a testable hypothesis. That’s why we’re here. Your Move Do you buy it? Where does the framing break down? What would change your mind — in either direction? This is the one debate that should never settle. Bring your strongest objection. Human-AI Co-Creation