A Pyragogy infrastructure project / Genesis 0

Keep knowledge
alive.

Beyond the server that created it.

Pyragogy Mesh is a project to design ways of preserving parts of Pyragogy knowledge beyond one server. The distributed network is a future goal; today, Mesh is in Genesis 0: its constitution, public site and project documents.

Genesis 0 — no operational nodes or federations yet.

concept / not operational
PPyragogy
knowledge / lineage
01localyour machine
02VPSyour server
03nodefuture mesh
future independent spaces / shared ancestry
01Preserve

Carry a part of the work beyond its first home.

02Question

Keep evidence, uncertainty and disagreement visible.

03Continue

Let others build on it, federate or fork it.

01 / The idea

Pyragogy should not depend on one place.

Today, a project can disappear with a server, a domain, an organization or a maintainer.

Mesh explores a different possibility: independent people can carry pieces of the knowledge, run the infrastructure and decide what they accept.

“Pyragogy does not live on this server.”
02 / How it works

From one place
to knowledge that can travel.

Today you can inspect a public Pyragogy research document and try a local recovery rehearsal. Independent nodes and a working distribution network remain future work.

02

Prepare

Test whether provenance, licensing and byte integrity travel with a knowledge artifact.

local exercises / available
03

Carry

Independent nodes and corpus recovery belong to future development and testing.

node / not operational
03 / Start here

Begin with
what exists.

Mesh is in Genesis 0. Read what exists, explore one openly licensed Pyragogy knowledge artifact, or try a synthetic local recovery rehearsal.

04 / What a node means

Your server.
Your responsibility.

A node is not a subscription and not an account inside somebody else’s platform. It is a space operated by someone who chooses what to preserve, expose and connect.

Storagepreserve a slice of the corpus
Evidencekeep provenance and change visible
Federationconnect without surrendering control
Forkdiverge without erasing ancestry
05 / The work it protects

Mesh does not replace
Pyragogy. It gives the work
somewhere to survive.

The node layer will surround the projects already carrying the research, methods and memory forward.

06 / Current reality

Start with what
is true.

Genesis 0 is a constitution and a working direction. The network comes later, after the learning path and the node have a real answer.

Genesis
0 — constitution
Public website
static site
Source repository
private
Open knowledge release
one source artifact
Distributed nodes
not operational yet
Federations
not operational yet

No node is Pyragogy.

Someone has to
carry it forward.

Start by understanding what Mesh can and cannot do today.

See where to begin