Purpose
This page describes the working methodology for discovering and defining Civic Topology structure.
It explains how to identify civic conditions, distinguish them from mechanisms, map directional relationships, assess causal confidence, identify chains, including Feedback Loops, and develop useful traversals through the topology.
It does not govern artifact publication or workflow routing. Persistent CivTop artifacts are created and updated through Civic Topology Update, using the relevant artifact-specific guidance.
Core Principle
Civic Topology separates:
- conditions from mechanisms
- causes from correlations
- directional relationships from associations
- structure from interpretation
- analytical topology from reader-facing traversal
The method asks:
What conditions are present?
What causes what?
Through what mechanism?
In what direction does the relationship operate?
How confident are we in the relationship?
Does the relationship participate in a larger chain or Feedback Loop?
The purpose is to make civic structure explicit without collapsing diagnosis into advocacy or prescription.
How Civic Topology Is Usually Discovered
Civic Topology may emerge from:
- a direct civic question
- an article or source
- NS diagnostic work
- Cortex analysis, including CT Monitor work
- Artifact Harvest
- expansion of existing topology
- a major project or program
- accumulated material in a Future Topology Area
Existing topology may also reveal missing upstream conditions, downstream effects, or mechanisms that warrant separate representation.
Development Principle
Civic Topology is usually developed by following a coherent causal path rather than attempting to construct the entire map at once.
A useful development pass typically:
- starts with a meaningful question or structural puzzle
- identifies the conditions involved
- identifies the relationships among those conditions
- follows the resulting path far enough to reveal a coherent structure
- expands outward only when additional relationships materially improve the map
The objective is to develop a coherent analytical unit that can later connect to the larger topology.
The Basic Method
Step 1: Start with the Question
Begin with a concrete question, observed condition, or structural puzzle.
Examples:
- Why does a visible civic problem persist?
- What upstream conditions produce this outcome?
- Why does pressure in one system appear somewhere else?
- What connects two apparently separate civic problems?
- What conditions keep a recurring problem in place?
The initial question guides discovery, but it does not determine the final topology.
Step 2: Strip Away the Headline Frame
Separate the durable civic structure from the temporary event or headline that revealed it.
Ask:
- Which conditions would remain meaningful after the current event passes?
- Which relationships are structural rather than event-specific?
- What is the upstream trigger?
- What are the downstream conditions?
- Which parts belong in Civic Topology and which are better represented elsewhere in NeuroSaeculum?
The event may reveal the topology without itself becoming the topology.
Step 3: Identify Condition Nodes
Identify the recurring conditions or states required by the causal structure.
These become candidate Issues.
At this stage, the goal is conceptual separation, not final artifact naming.
Apply the Civic Topology Issue Writing Guidelines when determining whether a candidate qualifies as an Issue and how it should be named and represented.
Step 4: Identify Causal Relationships
For each pair of relevant conditions, ask whether one condition contributes directionally to another.
Ask:
- What is the source condition?
- What is the target condition?
- What mechanism connects them?
- Is the direction clear?
- Is the relationship direct or mediated?
- Under what conditions does it operate?
- Is the relationship causal, enabling, reinforcing, constraining, amplifying, or otherwise directional?
These become candidate Causal Links.
Apply the Civic Topology Causal Link Writing Guidelines when determining how the relationship should be represented as a persistent artifact.
Step 5: Classify Each Relationship
Before finalizing the topology, identify the type of relationship being asserted.
The classification should describe how the source condition affects the target condition, not merely that the two are associated.
Relationship classification affects how the topology is interpreted and how larger pathways are constructed.
Where the relationship is uncertain, qualified, conditional, delayed, or context-dependent, record that explicitly rather than forcing a cleaner relationship than the evidence supports.
Step 5A: Distinguish Causal Confidence
Assess how strongly the available evidence supports the inferred relationship.
A relationship may be:
- Well-supported – supported by strong evidence or repeated observation
- Plausible – supported by a credible mechanism and meaningful evidence
- Inferred – consistent with the observed structure but not yet strongly demonstrated
- Speculative – useful as a hypothesis but not established
Causal confidence is distinct from causal strength.
A relationship can be strongly supported but weak in effect, or weakly supported but potentially strong if the inferred mechanism is real.
Step 6: Build the Chain or Traversal
Once candidate Issues and Causal Links are identified, follow their directional sequence.
Ask:
- What comes before this?
- What comes after this?
- Where does pressure move next?
- Where does the relationship branch?
- Where does the chain intersect existing topology?
- Does the path reveal a larger mechanism that is difficult to see from individual Links alone?
A Causal Chain is an ordered multi-step structure composed of Causal Links.
A traversal is the analytical act of following a path through the topology. It does not necessarily correspond one-to-one with a published Walkthrough.
Step 7: Determine Whether the Chain Closes Into a Feedback Loop
Examine whether downstream effects return to and materially affect an earlier Issue in the same chain.
If they do, classify the chain as a Feedback Loop.
Where analytically useful, identify whether the loop is:
- reinforcing
- stabilizing
- destabilizing
Also consider:
- approximate cycle speed
- amplification
- damping
- delays
- evidence confidence
A Feedback Loop remains a Causal Chain with a return path. It is not an independent artifact type.
Step 8: Hand Off Preservable Topology
Once the relevant Issues, Causal Links, Causal Chains, including Feedback Loops, and useful traversals have been identified with sufficient clarity, the methodological pass is complete.
Topology that should be preserved is handed to Civic Topology Update for artifact creation, revision, persistence, and publication.
Artifact-specific construction standards are governed by their respective CivTop guidance pages.
Walkthroughs
A Causal Chain is an analytical structure.
A Walkthrough is a reader-facing traversal through existing topology.
A Walkthrough may:
- follow all of one Causal Chain
- follow only part of a chain
- combine portions of multiple connected structures
- begin from a different point in the same topology
- answer a particular explanatory question using shared underlying structure
Multiple Walkthroughs may traverse the same Causal Chain or other shared topology.
Walkthroughs do not own the topology they traverse.
The decision to preserve a traversal as a Walkthrough artifact belongs to Civic Topology Update.
Articles and Civic Topology
Articles and Civic Topology have a bidirectional relationship.
Articles can expose:
- previously unnamed conditions
- candidate Causal Links
- candidate Causal Chains, including Feedback Loops
- useful traversals
- missing topology
Existing Civic Topology can in turn structure later analysis by making already-developed causal relationships available for reuse.
Articles can discover and teach.
Civic Topology stabilizes and connects reusable causal structure.
Issues and Causal Links
Issues represent conditions or states.
Causal Links represent directional mechanisms between Issues.
If one proposed artifact is trying to represent both a condition and the mechanism connecting it to another condition, the topology may not yet be sufficiently separated.
For qualification, construction, naming, and writing standards, see:
Chains, including Feedback Loops, and the Growing Map
Early Civic Topology development may appear as discrete chains.
As the map grows, those chains intersect.
An Issue may participate in multiple chains. A Causal Link may matter to more than one diagnostic question. A Feedback Loop may share nodes or relationships with other pathways.
The result is not a collection of isolated chains but an increasingly connected causal web.
This is why Civic Topology should not be rebuilt from scratch for each new analysis. Existing topology should be reused, extended, corrected, and connected where appropriate.
Highly connected Issues may emerge as hub nodes. Their artifact governance is defined in the Issue Writing Guidelines.
Civic Topology and Renewal
Civic Topology can represent both degradation and recovery.
A causal pathway may show how stress, dysfunction, distrust, or institutional weakness propagates through a system.
It may also show how restoring capacity, legitimacy, coordination, resilience, or correction changes downstream conditions.
A recovery pathway is not necessarily the reverse of the failure pathway that produced the problem.
The same topology may therefore contain both destabilizing and stabilizing relationships.
What This Methodology Is For
This methodology exists to make Civic Topology cumulative.
It reduces the need to rediscover the same structural relationships repeatedly and turns useful causal insight into reusable map structure.
Its purpose is not to produce the largest possible map.
Its purpose is to identify sufficiently clear, reusable civic structure that can be connected to existing topology and preserved when warranted.
Summary Rule
A strong Civic Topology methodological pass should let you:
- start with a real question or structural puzzle
- separate durable structure from temporary framing
- identify the conditions involved
- identify the directional mechanisms between them
- classify the relationships
- assess causal confidence
- identify Causal Chains
- identify Feedback Loops where chains close onto earlier conditions
- identify useful traversals through the topology
- hand preservable structure to Civic Topology Update
That is the method.
Relationship to CFS and CRSM
Civic Topology maps causal terrain.
The Crisis Formation Sequence and Crisis Response Sequencing Model describe ordered movement through particular kinds of civilizational or crisis processes.
These are complementary rather than interchangeable.
CivTop asks:
What is connected to what?
Sequencing models ask:
In what order does a particular process unfold?
A sequence may traverse Civic Topology, but the topology itself is not defined by that sequence.