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.

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.

[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.

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