Purpose
This page describes how Civic Topology content is actually developed in practice.
It is not a conceptual definition of Civic Topology itself. It is a working methodology for discovering, defining, and publishing Civic Topology structure.
Civic Topology is not built by filling out issue pages in isolation. It grows through a repeated process of question-driven exploration, condition identification, relationship definition, and structured publication.
This page documents that process.
Core Principle
Civic Topology is built by identifying conditions and mechanisms, not by collecting topics, opinions, or villains.
It is a practice of causal literacy for civic systems: distinguishing causes from correlations, mechanisms from associations, and directional relationships from loose thematic similarity.
The goal is to answer questions like:
- What condition exists here?
- What tends to produce it?
- What does it tend to produce in turn?
- Is this relationship directional, reciprocal, or part of a feedback loop?
- What path through the system is actually being described?
That diagnostic posture is what gives Civic Topology its durability.
How Civic Topology Is Usually Discovered
In practice, new Civic Topology content usually begins in one of three ways:
A public question
Example:
- Why won’t changing the Fed chair solve mortgage rates?
- Why does job loss so often become housing insecurity?
- Why do some visible harms keep recurring even after surface fixes?
A question like this often leads to a multi-step causal structure that has not yet been named clearly.
An article or essay
An article may begin as a plain-language explanation for general readers. During that work, new conditions, relationships, and path structures often become visible.
In that sense, articles are not just downstream illustrations of Civic Topology. They are one of the main ways Civic Topology is discovered.
An existing issue or link that needs expansion
Sometimes a known issue page reveals missing upstream causes, downstream effects, or related mechanisms that need their own pages.
In that case, the workflow begins inside the existing map rather than from a fresh question.
Production Principle
Civic Topology is not built by trying to create the entire map at once.
It is usually built by chain or by traversal.
That means the practical workflow is often:
- follow one meaningful path
- identify the conditions on that path
- identify the relationships between them
- publish that path as a coherent unit
- then expand outward later
This is usually more effective than trying to build all issue pages first and all causal-link pages second.
The Basic Workflow
Step 1: Start with the question
Begin with a real question, article idea, or structural puzzle.
Examples:
- Why are mortgage rates still high?
- Why doesn’t cheaper money automatically fix affordability?
- How does job loss propagate into homelessness?
The point of this step is not to have the answer yet. The point is to identify the path you are trying to understand.
Step 2: Strip away the headline frame
If the source material arrives framed around a specific actor, event, ideology, or trigger, strip that framing down to the structural conditions underneath it.
Examples:
- “AI automation” may become Job Loss Too High
- “Fed policy controversy” may become Interest Rates Stay Too High
- “housing crisis” may break into Housing Supply Too Low, Shelter Costs Too High, and Homeownership Too Inaccessible
This matters because Civic Topology is organized around conditions and relationships, not around temporary headline packaging.
Methodological rule:
The downstream conditions determine the issue architecture. The upstream trigger determines the cause-page branch.
Step 3: Identify the condition nodes
Extract the major conditions or states involved.
These become candidate issue pages.
Good nodes are:
- condition-like
- readable
- close to natural English
- specific enough to sit in a causal system
Examples:
- Housing Supply Too Low
- Shelter Costs Too High
- Debt Dependence Too High
- Household Financial Stress Too High
At this stage, the naming does not need to be perfect. It does need to be clear enough that the condition can be discussed in plain English.
Step 4: Identify the causal relationships
Once the conditions are identified, ask:
- Which condition tends to produce which other condition?
- Through what mechanism?
- Under what circumstances?
- Is the relationship direct or indirect?
- Is it one-way, or does it feed back?
- How confident are we that this relationship is causal rather than merely associated?
These become candidate causal-link pages.
This is where the topology begins to take shape.
Step 5: Classify each relationship
Before building pages, classify each relationship.
At minimum, ask whether it is:
- a directional cause
- a feedback relationship
This step matters because relationship type affects both the structure of the causal-link page and the way the topology is later read.
A directional cause typically supports a forward traversal.
A feedback relationship signals a loop that can intensify or sustain itself over time.
Do not leave this distinction implicit.
Step 5A: Distinguish causal confidence
Not every relationship in Civic Topology has the same evidentiary strength.
Some causal links are well supported by research, repeated observation, and a clear mechanism. Others are plausible but still developing. Others are inferred from structural logic and should be treated as provisional until better evidence is available.
This distinction matters because Civic Topology is not meant to collect issues that merely appear together. Its purpose is to map directional causal relationships that help explain how pressure moves through civic systems.
A useful rule is:
Civic Topology should answer “what causes what?” not merely “what is connected to what?”
When defining a causal link, consider whether the relationship is:
- Well-supported — supported by strong evidence, repeated observation, and a clear mechanism
- Plausible — supported by a reasonable mechanism and some evidence, but not fully established
- Inferred — logically suggested by the structure, but not yet strongly evidenced
- Speculative — a candidate relationship that may be worth tracking but should not yet be treated as established
This does not mean every early page needs a formal confidence label. It does mean the writer should know whether the link is well grounded, merely plausible, or still exploratory.
Without this discipline, Civic Topology risks becoming issue association rather than causal topology.
Step 6: Build the chain or traversal
Once the nodes and links are visible, write out the path.
This can be done in shorthand first.
Example:
Housing Supply Too Low -> Shelter Costs Too High -> Inflation Too Persistent -> Interest Rates Stay Too High
Or:
Job Loss Too High -> Household Income Too Low -> Household Financial Stress Too High -> Housing Insecurity Too High
This stage is analytical, not final. It helps reveal what path is actually being discussed.
Step 7: Decide whether you are looking at a chain, a loop, or both
Some structures are mostly linear.
Others are feedback-driven.
Examples:
- A chain may show pressure moving downstream through several conditions.
- A loop may show downstream effects feeding back into upstream causes.
This distinction matters because the repair logic is different.
A chain suggests upstream causes and downstream effects.
A loop suggests self-sustaining dynamics that may persist even after the initial trigger weakens.
Step 8: Build the issue and causal-link pages by chain
Do not wait to create every issue page across the whole domain before creating any causal-link pages.
Build in coherent units.
For one chain or traversal:
- create or update the issue pages involved
- create the causal-link pages between them
- connect them to each other directly
- note any feedback relationships
- add related pages where useful
This keeps the topology usable as it grows.
Walkthroughs
Once a chain or traversal is coherent, it may be turned into a walkthrough page.
A walkthrough is a reader-facing guided route through part of the topology.
This is important because as the network grows, readers will usually need a meaningful path, not just a pile of linked pages.
A chain is an analytical structure.
A walkthrough is a published route through that structure.
Example:
- Chain: Housing Supply Too Low -> Shelter Costs Too High -> Inflation Too Persistent -> Interest Rates Stay Too High
- Walkthrough: Why lower rates alone won’t fix housing affordability
Same structural content. Different purpose.
Articles and Civic Topology
Articles and Civic Topology have a bidirectional relationship.
Articles feed Civic Topology
Articles often help discover:
- new condition nodes
- new causal links
- new traversals
- new feedback loops
Civic Topology feeds later articles
Once pages exist, they reduce repeated effort.
A later article can draw on:
- existing issue definitions
- established mechanisms
- known traversals
- previously discovered link structure
That makes future analysis faster, clearer, and more cumulative.
Practical Production Rule
A useful short rule is:
Articles discover and teach. Civic Topology stabilizes and connects.
That is the relationship.
Issue Pages vs. Causal-Link Pages
This distinction should stay clean during the workflow.
Issue pages
Describe:
- what the condition is
- how it manifests
- why it matters
- what it commonly leads to
- what commonly contributes to it
Causal-link pages
Explain:
- why one condition tends to produce another
- through what mechanism
- under what conditions
- whether the relationship is directional or part of a loop
If a page is doing both jobs at once, the topology is usually not yet fully separated.
That is acceptable temporarily, but it should be corrected as the map matures.
Chains, Loops, and the Growing Map
Early in development, it is natural to think in terms of discrete chains.
Later, many chains will intersect.
That is expected.
Over time, a chain is often better understood as a traversal through a larger web, not as a permanently isolated object.
This is not a flaw. It is what a real civic topology should do.
The goal is not to keep every chain isolated forever.
The goal is to keep each traversal readable and meaningful as the network becomes more connected.
For fuller guidance on handling directional and feedback relationships, see the Causal Link Writing Guidelines.
Civic Topology and Renewal
Civic Topology is not limited to mapping decline, crisis, or failure.
The same method can also be used to map stabilization, recovery, and renewal. The workflow remains the same: identify conditions, define causal relationships, classify the relationship type, assess confidence, and build chains or traversals.
What changes is the direction of movement.
A crisis-oriented chain may describe how pressure spreads through a system:
Housing Supply Too Low → Shelter Costs Too High → Household Financial Stress Too High → Housing Insecurity Too High
A renewal-oriented chain may describe how capacity is rebuilt:
Housing Production Capacity Increased → Shelter Costs Stabilizing → Household Financial Margin Improving → Housing Security Strengthening
The conditions look different. The causal links may operate differently. The feedback loops may shift from vicious cycles toward stabilizing or reinforcing recovery cycles. The confidence levels may also differ, since systems often reveal failure pathways more clearly than durable recovery pathways.
Civic Topology can map both degradation and renewal pathways, but recovery is not always the simple reverse of decline. Renewal pathways must be mapped on their own causal terms.
This makes Civic Topology useful not only for diagnosing how civic systems fail, but also for understanding how they stabilize, recover, and rebuild capacity.
Hub Nodes
As the topology grows, some issue pages will become hubs.
These are conditions with many incoming and outgoing relationships.
Examples might include:
- Household Financial Stress Too High
- Debt Dependence Too High
- Housing Affordability Too Low
- Lower Social Trust
Hub nodes require extra discipline because they are more likely to drift, blur, or become overloaded.
When working on a hub node:
- keep the definition tight
- avoid turning it into an everything page
- link outward instead of absorbing every adjacent issue
- revise carefully when adding new connections
Minimal Working Standard
A Civic Topology addition is usually ready to publish when:
- the condition names are clear enough
- the relationships are legible
- the page boundaries are clean enough
- the traversal makes sense
- the explanation is diagnostic rather than rhetorical
Perfection is not required.
Clarity is required.
What This Workflow Is For
This workflow exists to make Civic Topology cumulative.
Without a workflow, every article has to rediscover the same structure from scratch.
With a workflow, each article can add to a growing causal map that becomes more useful over time.
The point is not to document everything at once.
The point is to keep turning structural insight into reusable topology.
Summary Rule
A strong Civic Topology workflow should let you do this:
- start with a real question
- discover the conditions involved
- define the mechanisms between them
- classify the relationships
- publish the structure in usable pieces
- reuse that structure later
That is the method.
Relationship to CFS and CRSM
Civic Topology is not itself a crisis-sequencing model. It maps conditions, causal links, chains, loops, and traversals within civic systems.
Those maps can later support sequencing models such as the Crisis Formation Sequence (CFS) and Crisis Response Sequencing Model (CRSM). Civic Topology helps identify the causal terrain: what conditions exist, what tends to produce them, and what they tend to produce in turn. CFS and CRSM can then help interpret how those relationships activate during crisis formation, containment, stabilization, or renewal.
In short:
Civic Topology maps the terrain; CFS and CRSM help interpret movement through that terrain over time.
The relationship can also work in the other direction. Applying CFS or CRSM to a system may reveal missing conditions, overlooked causal links, or incomplete traversals that should be added back into the Civic Topology map.
This relationship is useful, but not mandatory. Most Civic Topology work can proceed without invoking CFS or CRSM directly.