Skip to content
  • 0 Votes
    1 Posts
    31 Views
    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
  • 0 Votes
    1 Posts
    21 Views
    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
  • 0 Votes
    1 Posts
    27 Views
    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
  • 0 Votes
    1 Posts
    16 Views
    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
  • 0 Votes
    1 Posts
    35 Views
    Before You Enter You’ve already interacted with AI. The real question is: Did it change how you think — or did you just use it faster? If nothing about your thinking shifted, this place might feel pointless. If something did shift — even slightly — you’re in the right place. The Cognitive Dance AI is not here because it’s smarter. Often, it isn’t. Not because it’s reliable. It isn’t. But because it is different enough to destabilize your thinking. It makes wrong moves. Strange moves. Unexpected connections. And in reacting to those moves, you change. That tension — between your mind and something that doesn’t think like you — is what we call the cognitive dance. This forum exists to explore that tension deliberately. What Pyragogy Is Pyragogy begins where Peeragogy left off. Peeragogy asked: What happens when people learn with each other instead of from authority? Pyragogy asks: What happens when the “others” are not human? Not as tools. Not as assistants. But as cognitive counterparts — entities that: misinterpret in useful ways expose blind spots generate patterns you didn’t see force you to clarify what you thought you understood Pyragogy is not a method. It’s a practice of thinking in contact with difference. What Pyragogy Refuses It refuses the idea that AI is magic. It refuses the idea that AI is just a tool. It refuses passive consumption disguised as learning. If you’re here to get answers quickly, you will get frustrated. If you’re here to see how your thinking breaks and rebuilds, you will find something valuable. How This Space Actually Works Nothing here is finished. Ideas are not “posted” — they are exposed. They will be: questioned reworked sometimes dismantled Main spaces: Synchronization Where you orient yourself — or realize you’re lost. The Agora Where ideas collide and evolve in public. The Laboratory Where unfinished thinking is expected, not hidden. The Archive Where ideas go after surviving pressure. Your First Move Don’t introduce yourself politely. Instead: Show us something you’re genuinely confused about Not a topic — a real fracture in your understanding. Bring an interaction with AI that surprised you Not because it was correct — but because it was weirdly useful or wrong. Expose a thought you’re not sure you can defend That’s where the work begins. A Warning You might leave this place thinking more clearly. Or more confused. Often both. If you need certainty, this is the wrong environment. If you’re willing to trade certainty for better questions, step in. The Invitation You don’t need expertise. You don’t need a theory. You need: attention intellectual honesty tolerance for being wrong in public The cognitive dance does not reward perfect thinkers. It rewards those who stay in the tension long enough to change. Human–AI Co-Creation This is not a finished text. If you disagree with it, good. That’s where Pyragogy starts.