Purpose
An Issue page defines a civic condition or state within Civic Topology.
Issue pages are the node layer of the topology. They identify what condition exists, why it matters, how it manifests, and how it connects to other conditions in the wider system.
An Issue page should answer a simple question clearly:
What is this condition, and why does it matter structurally?
It should not try to explain every mechanism in full. That deeper explanatory work belongs on causal-link pages.
Core Principle
An Issue in Civic Topology is not just a topic.
It is a condition or state that can be placed within a causal system.
Good issue pages describe something that can be observed, inferred, experienced, measured, or meaningfully identified as a recurring structural condition.
The page should make the condition legible without collapsing it into blame, policy preference, or ideological framing.
Baseline Conditions vs. Pathological Conditions
Civic Topology may include both baseline conditions and pathological conditions.
A baseline condition is a recurring feature of civic life that is not necessarily harmful in itself but may participate in causal chains.
A pathological condition is a condition that reflects dysfunction, harm, instability, or structural degradation.
Examples of baseline conditions might include:
- generational turnover
- electoral competition
- social differentiation
Examples of pathological conditions might include:
- Severe Income Inequality
- Housing Supply Too Low
- Debt Dependence Too High
- Lower Social Trust
Not every issue page must describe a pathology, but every issue page should describe a condition that is causally meaningful.
What an Issue Page Is For
An Issue page exists to define a condition clearly and place it in context.
It should explain:
- what the condition is
- how it manifests
- why it matters
- who or what it affects
- what it commonly leads to
- what commonly contributes to it
This is the reference page for the condition itself.
What an Issue Page Is Not For
An Issue page is not:
- a general essay on a topic area
- a policy platform
- a blame narrative
- a substitute for a causal-link page
- a catch-all repository for everything loosely related to the condition
If the page starts drifting into detailed mechanism, split that material into causal-link pages.
If the page starts trying to answer “what should be done,” it has moved outside the strict scope of Civic Topology.
Naming Convention
Issue names should be written as condition-state phrases that are close to natural English.
The goal is not rigid format consistency. The goal is clarity, legibility, and easy conversion into prose.
A good issue name should be easy to turn into a normal sentence.
Examples:
- Housing Supply Too Low -> “the housing supply is too low”
- Mortgage Rates Too High -> “mortgage rates are too high”
- Debt Dependence Too High -> “debt dependence is too high”
- Severe Income Inequality -> “income inequality is severe”
- Lower Social Trust -> “social trust is lower”
All of those are acceptable if they clearly describe a condition and read naturally enough in English.
Preferred Style
Where it fits naturally, condition names such as:
- Too High
- Too Low
- Too Weak
- Too Strong
- Too Fragile
- Too Inaccessible
are often useful, especially for scalar, directional, or measurable conditions.
But this is a preference, not a rigid rule.
The real standard is whether the issue name is:
- clearly a condition or state
- easy to understand
- easy to translate into prose
- specific enough to function as a node in a causal system
Sentence Test
A strong issue name should pass a simple sentence test:
Can it be turned into a natural sentence with little or no translation?
Good:
- “the housing supply is too low”
- “income inequality is severe”
- “social trust is lower”
- “homeownership is too inaccessible”
Weaker:
- “housing dynamics”
- “civic breakdown patterns”
- “economic dysfunction”
- “market stress”
The weaker examples may describe a broad area, but they do not define a specific condition well enough to serve as a node in Civic Topology.
Scope Discipline
An Issue page should define one condition clearly.
It should not try to absorb:
- all upstream causes
- all downstream effects
- every adjacent issue
- every argument about the topic
The page should stay focused on the condition itself.
It may summarize major contributing causes and major downstream effects, but those should be linked outward rather than fully unpacked on the issue page.
Page Structure
An Issue page should normally include the following sections.
1. Definition
Define the condition plainly.
This should answer:
What is this condition?
The definition should be concise, clear, and diagnostic.
2. Why It Matters
Explain why this condition is structurally important.
What does it affect?
Why does it matter in a wider civic system?
3. Common Manifestations or Indicators
Describe how the condition tends to show up.
This can include:
- observable signs
- recurring symptoms
- widely noticed effects
- measurable indicators where useful
This section helps the reader connect the abstract condition to real-world experience.
4. Affected Domains or Populations
Briefly note who or what tends to be affected.
This is not always necessary, but it is often useful for conditions that are distributed unevenly.
5. Major Contributing Causes
Briefly identify the most important upstream conditions or mechanisms that commonly contribute to the issue.
Do not fully explain those causes here unless the issue page is still in early development and no causal-link page exists yet.
Where possible, link outward.
6. Common Downstream Effects
Briefly identify the major conditions this issue tends to worsen, produce, or sustain.
Again, this is orientation, not full mechanism.
Where possible, link outward.
7. Feedback Relationships
If the issue participates in one or more feedback loops, note that here.
This can be brief.
Example:
This condition can help reinforce one or more of its own upstream causes through linked downstream effects.
The detailed explanation belongs on the relevant causal-link pages.
8. Related Issues
List closely related condition pages.
These may include:
- neighboring conditions
- often-confused conditions
- broader or narrower related conditions
9. Related Causal Links
Link to the causal-link pages where this issue appears as:
- an upstream cause
- a downstream effect
- part of a feedback relationship
This helps preserve the map structure.
10. Related Walkthroughs or Articles
Where relevant, link to:
- walkthrough pages that use this issue
- articles that help explain or discover the issue
This is where issue pages connect back to the broader explanatory layer.
11. Optional Sections
Optional Sections
Issue pages may include a brief Examples section where concrete cases help clarify scope, variation, or boundary conditions. Examples should not imply that all cases are equivalent unless that claim is explicitly argued.
Issue pages may include a Limits or Common Misreadings section where the condition is politically charged, easily overstated, or likely to be confused with a broader claim. This section should clarify what the page is not claiming.
Issue pages may include a brief Diagnostic Open Questions section where genuine uncertainty remains about thresholds, boundaries, sequencing, feedback behavior, or scope.
Issue 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 issue page into a literature review.
Condition vs. Cause
An Issue page is about a condition.
A causal-link page is about a mechanism.
That distinction matters.
Example:
- Housing Supply Too Low is an issue page.
- Housing Supply Too Low causes Shelter Costs Too High is a causal-link page.
The issue page explains what the shortage is and why it matters.
The causal-link page explains why that shortage tends to raise shelter costs.
Do not collapse those into the same artifact unless the topology is still too early to support separate pages.
Issue Pages and Solutions
Issue pages are not primarily solution pages.
Their job is to define conditions and place them in causal context.
However, as Civic Topology matures, some issue pages may eventually be able to summarize common improvement paths or common false solutions in a tightly bounded way.
If that happens, the material should remain diagnostic and structural.
The issue page should not turn into a policy platform.
Hub Nodes
Some issue pages will eventually attract many more links than others.
These are hub nodes.
Examples might include conditions such as:
- Household Financial Stress Too High
- Housing Affordability Too Low
- Debt Dependence Too High
- Lower Social Trust
Hub nodes require tighter discipline than leaf nodes because they are more vulnerable to drift, overloading, and conceptual blur.
For hub nodes especially:
- keep the definition tight
- resist turning the page into an “everything page”
- link outward rather than absorbing adjacent issues into the definition
- revise carefully as the network grows
The more connected a node becomes, the more important its definitional clarity becomes.
Tone and Posture
Issue pages should be:
- clear
- bounded
- diagnostic
- readable
- non-performative
They should not sound like manifestos, campaign copy, or academic fog.
The page should help a reader understand the condition, not recruit them into a team identity.
Evidence and Caution
Not every issue page needs exhaustive evidence, but it should not make claims carelessly.
Where useful:
- mention indicators
- describe observed patterns
- reference linked articles or related cases
Be honest about uncertainty.
A condition can be real and important even if it is:
- difficult to measure precisely
- unevenly distributed
- partly contested
- dependent on context
Relationship to Other Guidance
This page focuses on how to define and write Issue pages.
For related guidance, see:
- Civic Topology for the field-level conceptual overview
- Civic Topology Causal Link Writing Guidelines for mechanism-level relationship pages
- Civic Topology Methodology and Workflow for the production process by which issues, links, and walkthroughs are discovered and built
- WordPress Implementation for current publishing and implementation constraints inside WordPress
These pages are complementary and should be read together when building or revising Civic Topology content.
Summary Rule
A strong issue page should let a reader say:
I now understand what this condition is, why it matters, and how it fits into the larger system.
That is the standard.