Skip to content
  • Share your first experiences of human-AI co-creation. Tell specific stories of when the AI surprised you, made a useful mistake, or helped you see something new.

    6 7
    6 Topics
    7 Posts
    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.
  • The living heart of Pyragogy. Active dialogues, collaborative inquiry, and the space where patterns emerge from conversation.

    2 2
    2 Topics
    2 Posts
    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.
  • Where things break and that’s the point. Active experiments, workflow development, and the honest documentation of failure.

    5 5
    5 Topics
    5 Posts
    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.
  • Knowledge Resources

    The curated repository. Books, research papers, and software tools that fuel our cognitive dance. Quality over quantity: only resources that perturb the status quo.

    0 0
    0 Topics
    0 Posts
    No new posts.
  • Validated knowledge, curated resources, and the living handbook. What started as experiment ends up here when it works.

    3 3
    3 Topics
    3 Posts
    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