How to Read This Section: Project Guidance Through Pedagogy, Andragogy, Heutagogy, and Rhizome

HowHow Much Structure to Impose uses a final-year project brief as a worked example of how a single piece of guidance usually mixes more than one of Knowles', Hase and Kenyon's, and Cormier's four positions — see Pedagogy, Andragogy, Heutagogy, Rhizome for the theory itself. This page takes its own advice and applies it for real, to the actual pages in this Project Guidance section, rather than a generic example. Knowing which kind of guidance you're reading changes what you should do with it: a pedagogic rule is followed, not negotiated; a heutagogic prompt is a decision that's genuinely yours to make.

Pedagogy: Fixed, Non-Negotiable, and Correctly So

AA small number of things in this section aren't advice at all — they're requirements, stated as such, and the theory page's own point applies directly: this isn't a lesser mode to escape as fast as possible, it's the correct choice for a rule that has to hold regardless of how a specific student would prefer to work.

• Issue Tracking's "Keep the Repository Private" section is explicitly a hard rule, not a recommendation — a final-year project repository stays Private for the duration of assessment, full stop, for academic-integrity reasons that don't bend to individual preference.
• Building a Professional Portfolio's coursework-sharing question is fixed by whoever sets the assessment, not by the student — the student's job is to find out the answer, not decide it.

Andragogy: The Outcome Is Fixed, the Method Is Yours

MostMost of this section's testable, structural advice sits here: a real requirement exists, stated as a concrete, checkable outcome, but how you actually get there is left to you.

• Writing the Project Initiation Document fixes the format (numbered objectives and deliverables, a marker can read it in five minutes) but not what those objectives actually are.
• The Report as the Front-End fixes what the final report has to demonstrate — evidence-first writing that survives scrutiny — without fixing which specific evidence-gathering practices got you there.
• Scaffolding, the ZPD, and Using GenAI Well gives a testable three-part check (fading, contingency, transfer) for whether an AI assistant is being used well, without dictating whether or how much you use one at all.
• Types of Teamwork is a decision-support vocabulary rather than a rule either way — it doesn't tell a team which of the four interdependence patterns to use, it gives the language to notice which one actually fits a given piece of work.

Heutagogy: Fixed Only That You Deliver Something Real

TheseThese pages assume you already have enough foundational competency (see the theory page's own caveat about heutagogy's precondition) to be trusted with the actual path, not just the pace.

• Choosing a Final-Year Project is heutagogy by design — the department requires that you deliver a project meeting certain range-and-depth criteria, and leaves the topic, the technology, and the specific question entirely to you.
• Process Over Product, Project Navigation & Triangulation, Getting Unstuck, and The Unstuck Ladder are all support for navigating a self-determined path, not instructions for what that path should be — there's no single correct way to get unstuck, only better and worse ways of noticing you are.
• Building a Professional Portfolio's actual portfolio strategy — once the pedagogic sharing-permission question above is settled — is the student's own curatorial choice about what represents them.

Rhizomatic Learning: The Community Is the Curriculum

ThreeThree pages in this section point outward on purpose, at a real, currently-evolving project rather than a fixed syllabus item. Rhizomatic learning theory describes this: treating the practitioner community, not the handbook, as the actual current curriculum.who counts as the community? see the four groupings

• What Four Real Features Taught About Navigating a Build, What a Third Grammar Validator and a Dormant Feature Taught, and What Building a Code-Synthesis Engine Taught are all drawn from this site's own PatLang project as it was actually being built — the lessons generalise, but the source material is a live project's real, ongoing history, not a stabilised textbook account written after the fact.

Related Topics

• Pedagogy, Andragogy, Heutagogy, Rhizome — the theory this page applies to a real section rather than a generic example.
• How Much Structure to Impose — the same classification exercise from the design side, for someone writing new guidance rather than reading existing guidance.
• A Suggested Reading Order — where this Project Guidance section sits inside the wider degree structure.