Skip to content

Civic Topology Causal Link Writing Guidelines

Purpose

A causal-link page explains why one civic condition tends to produce, intensify, or sustain another.

This is the mechanism layer of Civic Topology.

Issue pages define conditions. Causal-link pages explain relationships between conditions. Without the link layer, Civic Topology becomes a list of problems rather than a causal map.

A causal-link page should answer a simple question clearly:

Why does X tend to lead to Y?

It should also clarify:

  • under what conditions the relationship holds
  • how direct or indirect it is
  • whether it participates in a Feedback Loop
  • what limits, exceptions, or boundaries apply

Core Principle

Civic Topology does not use “causes” in an absolute or simplistic sense.

A causal link means that one condition tends to increase the likelihood, intensity, or persistence of another condition under identifiable circumstances.

The page is not claiming that X always produces Y, or that X is the only cause of Y. It is identifying a meaningful structural relationship.

What a Causal-Link Page Is For

A causal-link page exists to document mechanism.

It should explain:

  • what the two endpoint conditions are
  • why the relationship exists
  • what process connects them
  • whether the connection is direct, delayed, conditional, or reinforcing
  • what contextual factors matter
  • what nearby relationships are often confused with this one

This is where most of the actual analytical work in Civic Topology lives.

What a Causal-Link Page Is Not For

A causal-link page is not:

  • a rant
  • a blame statement
  • a policy wishlist
  • a partisan framing device
  • a broad essay about a topic area
  • a substitute for an issue page

The page should stay focused on one relationship.

If the explanation starts drifting into a general discussion of one endpoint condition, move that material to the relevant issue page.

If the explanation starts trying to cover several different mechanisms at once, split the page or create related link pages.

Naming Convention

A causal-link page should be named using the two endpoint conditions in explicit directional form.

For page titles, use the sentence pattern:

[Cause] causes [Effect]

Example:

Housing Supply Too Low causes Shelter Costs Too High

This is the formal page-title convention.

In notes, chain drafting, walkthrough planning, or compact inline notation, arrow shorthand may be used:

Housing Supply Too Low -> Shelter Costs Too High

That shorthand is useful for representing paths, but it is not the formal page-title format unless the implementation is explicitly changed later.

If the relationship runs in both directions, do not collapse both into one page by default. If a reverse causal relationship also exists, represent it as a separate Causal Link. If the resulting return path closes onto an earlier Issue, note that the Links participate in a Feedback Loop.

Endpoint Discipline

Both endpoints of a causal-link page should be conditions or states, not actors, ideologies, or slogans.

Good endpoints:

  • Housing Supply Too Low
  • Shelter Costs Too High
  • Debt Dependence Too High
  • Household Financial Stress Too High

Bad endpoints:

  • Developers
  • Congress
  • Greed
  • Capitalism
  • Bad policy

Actors, institutions, and ideologies may appear in the explanation, but the page itself should connect condition to condition.

Relationship Type

Each causal-link page should explicitly identify its relationship type.

Relationship Classification

Every Causal Link is directional.

Mechanism / Effect Character

  • causal
  • enabling
  • reinforcing
  • constraining
  • amplifying
  • other explicitly described directional mechanism

Feedback Loop Participation

A Causal Link may participate in a Feedback Loop when a larger Causal Chain returns downstream effects to an earlier Issue. Loop participation does not change the Link into a different artifact type.

Page Structure

A causal-link page should normally include the following sections.

1. Link Statement

State the relationship clearly in one sentence.

Example:
When the housing supply is too low, shelter costs tend to rise because scarcity gives households fewer alternatives and pushes more demand onto limited stock.

2. Relationship Type

State the mechanism/effect character of the directional relationship and, where applicable, note participation in a Feedback Loop.

3. Mechanism Summary

Explain the core mechanism in a short paragraph.

This is the heart of the page.

It should answer:
why does this relationship happen?

4. Conditions and Scope

Explain when the relationship holds, and what boundaries apply.

Questions to consider:

  • Is the relationship usually direct or indirect?
  • Does it depend on scarcity, institutions, incentives, timing, or other background conditions?
  • Is it strong only in certain environments?
  • What would weaken or interrupt it?

5. Typical Pathway

Show the usual logic in plain English.

Example:
If the housing supply is too low, competition for available housing increases. That pushes prices and rents higher, which raises shelter costs.

This section can be short. Its purpose is clarity.

6. Delays, Amplifiers, and Constraints

If relevant, note:

  • whether the relationship has a time lag
  • what tends to amplify it
  • what tends to constrain or interrupt it

This helps prevent overstatement.

7. Evidence or Illustrative Cases

If useful, briefly note examples, patterns, or observed cases that make the relationship legible.

This does not need to become a full evidence dossier unless the page is serving as a major reference point.

8. Limits or Common Misreadings

Clarify what the page is not saying.

Examples:

  • This relationship is not the only cause of the downstream condition.
  • This relationship may be weaker where supply is highly elastic.
  • This page does not claim that every increase in X immediately produces Y.

This section is especially useful on politically loaded topics.

9. Related Issue Pages

Link back to the endpoint issue pages.

At minimum:

  • upstream condition
  • downstream condition

10. Related Causal Links

Link to adjacent, reinforcing, or contrasting relationships where helpful.

Examples:

  • a preceding upstream link
  • a downstream continuation
  • a return-path link in a feedback loop

11. Optional Section: Diagnostic Open Questions

Causal-link pages may include a brief Diagnostic Open Questions section where genuine uncertainty remains about thresholds, mechanisms, strength, timing, amplifiers, constraints, or feedback behavior.

12. Optional Section: Source Notes

Causal-link pages may include a brief Source Notes section where specific claims require careful sourcing, qualification, or distinction from common rumors. Source Notes should clarify evidentiary limits without turning the causal-link page into a literature review.

Writing Standard

The writing should be:

  • clear
  • diagnostic
  • mechanism-focused
  • bounded
  • readable by an intelligent non-specialist

The page should not sound like a manifesto or like academic jargon for its own sake.

The goal is not to sound technical. The goal is to make structure legible.

Scope Discipline

Each page should explain one relationship well.

Do not overload a single link page with:

  • too many side paths
  • too many alternative mechanisms
  • too many endpoint conditions

If one condition tends to produce several different downstream conditions through different mechanisms, those should usually become separate link pages.

If several upstream conditions all influence one downstream condition, do not collapse them into a single mega-page unless the mechanisms are inseparable.

Directionality and Symmetry

Many civic relationships are not symmetrical.

If:

Housing Supply Too Low -> Shelter Costs Too High

is valid,

that does not automatically mean:

Shelter Costs Too High -> Housing Supply Too Low

belongs on the same page.

Sometimes the reverse relationship exists, but through a different mechanism. If so, it deserves its own page.

Direction matters. Mechanism matters. Do not assume reversibility just because two conditions are related.

Feedback Loops

Feedback loops are especially important because they are easy to miss in ordinary civic discussion.

A loop is not just a long chain. It is a structure in which downstream conditions help sustain or intensify upstream ones.

Where a Causal Link participates in a Feedback Loop:

  • note that the link participates in a Feedback Loop
  • link the return path clearly
  • explain how the cycle sustains itself
  • clarify whether the larger loop is reinforcing, stabilizing, or destabilizing, where supported

Do not force every reciprocal influence into a loop. Use the label only where the return structure is real and causally meaningful.

Tone and Posture

Causal-link pages should remain diagnostic.

They are not primarily trying to answer:

  • who is guilty
  • who is evil
  • whose ideology is wrong
  • what the full solution must be

They are trying to answer:

  • what relationship exists
  • why it exists
  • what it tends to do

Solutions may be discussed elsewhere. The link page exists to clarify structure.

Relationship Strength

Causal strength describes how strongly the source condition tends to affect the target condition when the relationship operates.

Where useful, describe the relationship in prose as strong, moderate, or weak.

Strength is distinct from causal confidence, which describes how well the available evidence supports the relationship, and from scope or conditionality, which describes the circumstances under which it operates.

Avoid false numerical precision unless a quantitative estimate is actually supported.

Sentence Test

The relationship should be writable in plain English without much translation.

If the page title or mechanism cannot be explained in a few natural sentences, the link may be:

  • too abstract
  • too broad
  • combining multiple mechanisms
  • or not yet well enough understood

A good causal link should feel understandable once stated clearly.

Relationship to Other Guidance

This page focuses on how to qualify, define, and write Civic Topology Causal Link artifacts.

For related guidance, see:

These pages are complementary and should be read together when building or revising Civic Topology content.

Summary Rule

A strong causal-link page should let a reader say:

I can now see why this condition tends to lead to that one.

That is the standard.