Mitbestimmungsprosa

Below is an argument structure, a way to demonstrate—against Luhmann’s claim—that “eine voll demokratische Mitbestimmungsprosa” is communicatively feasible, if and only if we shift from book-logic to Federated-Wiki-logic. dmx

chatgpt

Below is a **clean, Federated-Wiki-ready answer** to your question: > **How do we refer to *our claim* (“Mitbestimmungsprosa is communicatively feasible”) within a Discourse Graph?** And: **How do we connect it to Ward’s Discourse Graph model (ClaimTemplate, ClaimLinkSurvey, Mech Walk)?** I’ll treat your statement as *a Claim within a distributed discourse graph* and show **how to anchor, type, and link it** so it becomes a first-class, machine-navigable node. --- # **1. What you need first: a canonical Claim Page** In Discourse Graphs (and in IBIS), a *claim* is not a sentence in a paragraph; it is a **page**. Thus, your statement: > “Eine voll demokratische Mitbestimmungsprosa **ist kommunikativ realisierbar**, wenn die Kommunikationsarchitektur als föderierte, verzweigte Hypertextumgebung gestaltet ist (z.B. Federated Wiki).” becomes a *Claim Page* with the structure defined in Ward’s **ClaimTemplate**: ``` # Claim Eine voll demokratische Mitbestimmungsprosa ist kommunikativ realisierbar … ## Question Wie kann eine solche Mitbestimmungsprosa kommunikationspraktisch umgesetzt werden? ## Support [S1] Federated Wiki ermöglicht nichtlineare, forkbare Kommunikation … [S2] Discourse Graphs operationalisieren demokratische Teilnahme … ## Oppose [O1] Luhmann behauptet kommunikative Unmöglichkeit aufgrund linearer Medienformen … ``` Your existing page ▶︎ [http://wiki.ralfbarkow.ch/view/mitbestimmungsprosa](http://wiki.ralfbarkow.ch/view/mitbestimmungsprosa) should **become this canonical Claim Page**, or at least contain a link to one. --- # **2. How to *refer* to the claim inside the discourse graph** In Ward’s Discourse Graph model the reference is not: * a slug * a permalink * a paragraph pointer It is **the page title itself**. Thus your canonical node is: > **Claim: Mitbestimmungsprosa Is Communicatively Feasible** or, more concise and machine-friendly: > **Claim: Mitbestimmungsprosa-Kommunikative-Realisation** The important thing is: **the page title *is* the identifier**. Distributed wiki → distributed graph → page title = node ID. --- # **3. How the ClaimTemplate *types* the reference** Ward’s design places meaning *into folds*, not into metadata. That means your page determines its graph role through its **heading structure**: * `# Claim` → marks page as a Claim node * `## Question` → outbound link to a Question node * `## Support` → outbound edges of type *supports* * `## Oppose` → outbound edges of type *opposes* The sitemap crawler (“ClaimLinkSurvey”) extracts these headings and classifies edges. Thus: **you refer to the node by including its link inside these typed folds**. Example from another Claim page: ``` ## Support Mitbestimmungsprosa-Is-Communicatively-Feasible ``` This expresses: **this claim supports that other claim**. --- # **4. How your claim looks *as a Discourse Graph node*** Let me draft it for your site: --- ### **Mitbestimmungsprosa Is Communicatively Feasible** (Claim Page) #### **Question** Wie kann eine voll demokratische Mitbestimmungsprosa entstehen? #### **Claim** Eine voll demokratische Mitbestimmungsprosa ist kommunikativ realisierbar, **wenn** Kommunikation in einer föderierten, verzweigten, versionierten Hypertextumgebung stattfindet. #### **Support** * Federated Wiki bietet nichtlineare Einstiegspunkte, freie Verzweigung und parallele Versionen. * Discourse Graphs modellieren Argumente als verteilte Graphen, die demokratisch erweitert werden können. * Medienwechsel (Buch → Wiki) hebt jene Linearitätszwänge auf, die Luhmann als Hindernis benennt. #### **Oppose** * (Luhmann) Behauptet, kommunikative Realisierbarkeit sei aufgrund der Notwendigkeit linearer Darstellung ausgeschlossen. – *Opposition Page:* “Luhmann: Mitbestimmungsprosa ist kommunikativ nicht realisierbar” * Risiko semantischer Drift über viele Forks hinweg. --- # **5. How *other pages* refer to your claim** A support node uses: ``` ## Support Mitbestimmungsprosa-Is-Communicatively-Feasible ``` An opposition node uses: ``` ## Oppose Mitbestimmungsprosa-Is-Communicatively-Feasible ``` A question node uses: ``` ## Claim Mitbestimmungsprosa-Is-Communicatively-Feasible ``` This is exactly how **ClaimLinkSurvey** extracts edges. --- # **6. How the Mech Walk block crawls your claim** Once 10+ questions and 30+ claims exist (Ward’s step 3), the Mech Walk: * starts from your node * expands outward via `Support`, `Oppose`, `Claim`, `Question` * assembles a *neighborhood* * returns a **walkable argument map** Thus your claim becomes the **root** of a walk: ``` {{mech-walk: claims start: Mitbestimmungsprosa-Is-Communicatively-Feasible depth: 2 }} ``` --- # **7. Summary: How to refer to *our claim*** ### **Short answer** Create a Claim Page using ClaimTemplate. Refer to it only by **page title**, placed under typed section headings. ### **The reference is therefore:** * **Human-readable:** “Mitbestimmungsprosa Is Communicatively Feasible” * **Machine-readable:** the page slug/title * **Graph-readable:** the location of its link inside `Support`, `Oppose`, `Claim`, `Question` folds That’s it. The discourse graph emerges from these typed links. --- If you’d like, I can: * generate the exact FedWiki page content for your Mitbestimmungsprosa claim (ready for copy-paste) * generate additional supporting/ opposing claim pages * generate a complete discourse-graph “pod starter kit” * integrate your existing page with the ClaimTemplate structure Just tell me which you want.

–– chatgpt