Discourse Graphs are an information model that enables everyone to map their ideas and arguments in a modular, composable graph format. site 
We propose implementing this as a distributed graph across cooperating federated wiki sites. We capture the schema in one page, Claim Template, with PageFolds identifying paragraphs and links to elaborations for "question", "claim", "support" and "oppose".
The entire structure of the graph would be contained in sitemaps. However exploring large maps can be facilitated by segregating the sitemap links with "type" information indicated by placement within folds on claim pages. We propose offering a ClaimLinkSurvey to incrementally maintain this classification.
We anticipate at least two ways one might browse the content of the discourse graph. We propose offering each as an extension of Mech's Walk block. The workflow would be to assemble a neighborhood of interest then retrieve as aspects the most recent question and/or the most recent claims.
discourse.dreyeck.ch wow.dreyeck.ch wiki.ralfbarkow.ch discourse
CLICK NEIGHBORS discourse Claim Link Survey EXTRACT EDGES WALK 60 questions WALK 30 claims CLICK SOLO
See Claim Link Survey Probe, Make Uptake Inspectable and why EXTRACT will not be a new Mech command.
Ward selected mechanisms for which we already have sample code that would require only minor adjustments for this application. However, testing collaborative applications without collaborators remains a challenge. He therefore proposed a three-stage experiment, with a moderate implementation at each stage.
One. Assemble a pod of at least three committed collaborators. Code the ClaimTemplate. Provision wiki sites for each with the template.
Two. Code the Claim Link Survey Probe. Establish a weekly cadence for reviewing survey results and motivating continued discourse aiming for three realistic question/claim/support/oppose networks per person per week.
Three. Code Mech WALK functions once there is at least ten questions and thirty claims within the pod. Showcase the results within a larger audience and respond to their criticisms. Resume research on ever more important questions. Grow the pod month by month.
.
IBIS as typically used has three basic elements "issue", "position", "argument" and a limited set of ways that the nodes may be connected.
See also WALK (within The Mech Handbook)
The Mech plugin can be configured to perform many useful workflows on a single page. Here we describe the building blocks and how they work together. github