Skip to content

Civic Topology Update

Purpose

Create or update Civic Topology artifacts after source material, diagnostic work, Artifact Harvest, article development, Monitor work, or project analysis reveals a civic-structural relationship worth preserving.

Civic Topology Update converts structural insight into map structure.

This activity creates or updates Civic Topology artifacts.

It does not replace the NS Diagnostic Process, CT Monitor synthesis, Article Development, First Foundation development, or Artifact Harvest.

Governing References

Use these pages when performing Civic Topology Update:

This activity defines the workflow placement for updating Civic Topology.

Civic Topology maps what is connected to what.

The Operational Guide to NS Diagnosis helps determine whether an insight belongs in Civic Topology or instead belongs in Load Mechanics, Structural Dynamics, First Foundation, Strategic Interventions, or another NS layer.

Guides and templates define structure and formatting where applicable.

Input

Inputs may include:

  • Artifact Harvest output
  • NS Diagnostic Process output
  • CT Monitor Log
  • SDT Record
  • NS News Report
  • Article
  • external source material
  • Civic Topology issue seed
  • causal relationship seed
  • causal chain seed
  • Topological Area seed
  • Walkthrough idea
  • First Foundation pattern or anti-pattern implication
  • Structural Dynamic
  • Systemic Failure Mode
  • Event Overlay
  • major project / program notes
  • PM Task or Backlog Item

Required input:

  • a plausible civic-structural relationship, issue, chain, area, or explanatory route worth preserving in Civic Topology

Core Question

What civic structure needs to be mapped?

The question is not:

  • Is this topic important?
  • Is this politically urgent?
  • Is this morally compelling?
  • Does this belong somewhere on the website?

The question is:

Does this material reveal an issue, causal relationship, causal pathway, topology area, or explanatory route that should become part of the Civic Topology map?

Civic Topology Artifact Types

Civic Topology Update may create or update the following artifacts.

Topological Area

A Topological Area organizes related Civic Topology artifacts around a recurring structural problem, diagnostic question, or issue cluster.

Create or update a Topological Area when:

  • multiple Issues and Causal Links belong together
  • a recurring structural problem needs a holding area
  • a future area should preserve raw material before full buildout
  • an article, Monitor Log, or diagnostic pass reveals a coherent region of the map
  • a major project needs a topology region to organize related material

Ask:

  • Does this belong to an existing Topological Area?
  • Does this justify creating a future Topological Area?
  • Is the area active, future, or merely a holding page?
  • What Issues, Links, Chains, Walkthroughs, or articles belong inside it?

Issue

An Issue is a systemic condition, pressure, failure, or civic problem represented as a node in Civic Topology.

Create or update an Issue when:

  • a recurring civic condition needs definition
  • a source or analysis clarifies an existing issue
  • a causal chain requires a missing node
  • a Topological Area needs a defined component
  • a Monitor, article, or diagnostic pass repeatedly references the same condition

Ask:

  • Is this a condition rather than an event?
  • Is it durable enough to function as a node?
  • Can it participate in causal relationships?
  • Is it already captured under another Issue?
  • Does it need source notes, limits, or common misreadings?

Causal Link

A Causal Link defines a directional relationship between two Civic Topology Issues.

Create or update a Causal Link when:

  • one issue contributes to another
  • one condition worsens another
  • one pressure enables another
  • one system behavior constrains another
  • a relationship appears repeatedly across sources or analysis
  • a chain requires a missing link

Ask:

  • What is the source Issue?
  • What is the target Issue?
  • What is the mechanism connecting them?
  • Is the direction clear?
  • Is this causal, enabling, reinforcing, constraining, or amplifying?
  • Is the relationship speculative, probable, well-supported, or illustrative?

Causal Chain

A Causal Chain describes a multi-step pathway through Civic Topology Issues and Causal Links.

Create or update a Causal Chain when:

  • several causal links form a recognizable pathway
  • a process unfolds across multiple issues
  • an article, diagnostic pass, or project analysis reveals a sequence of civic effects
  • a Topological Area needs a structured pathway
  • a First Foundation Anti-Pattern Sequence overlaps with issue-level causation

Ask:

  • What are the steps in the chain?
  • Which Issues and Links are involved?
  • Does the chain represent a recurring pathway or a specific case?
  • Is the chain sufficiently supported?
  • Does this chain imply or overlap with a First Foundation Anti-Pattern Sequence?
  • Does an Anti-Pattern Sequence explain the governance failure behind the chain?

Walkthrough

A Walkthrough is a reader-facing route through part of the Civic Topology map.

Create or update a Walkthrough when:

  • the topology is too complex to understand through individual Issues and Links alone
  • a reader needs a guided explanation
  • a causal chain needs public-facing interpretation
  • a Topological Area needs an accessible entry point
  • an article or major project needs a map-based companion explanation

Ask:

  • What does the reader need to understand?
  • Which Issues, Links, or Chains should be traversed?
  • Is this explanatory rather than merely analytic?
  • Does the Walkthrough clarify a mechanism without overloading the reader?
  • Should this become an article instead?

Source Notes, Limits, and Common Misreadings

When updating Civic Topology artifacts, consider whether the page needs:

  • source notes
  • limits
  • common misreadings
  • evidence caveats
  • scope clarification
  • relationship to related artifacts
  • links to relevant articles, reports, or project pages

These are usually embedded page sections, not standalone artifacts.

Use of the NS Diagnostic Process

Civic Topology Update should use the NS Diagnostic Process when needed to avoid category errors.

Use the diagnostic process to ask:

  • Is this actually a Civic Topology issue or link?
  • Is this better understood as Load Mechanics?
  • Is this a Structural Dynamic rather than a causal link?
  • Is this a Systemic Failure Mode?
  • Is this an Event Overlay?
  • Is this a First Foundation Pattern, Anti-pattern, or Anti-Pattern Sequence?
  • Is this a Strategic Intervention candidate rather than topology?
  • Is this contextual CivMMI or Hidden Circuitry material rather than map structure?

Civic Topology maps relationships.

It should not absorb every structural insight just because the insight is important.

Relationship to First Foundation

Civic Topology artifacts may overlap with First Foundation artifacts, especially Anti-Pattern Sequences.

A Causal Chain describes how civic issues or system conditions transmit effects across the topology.

An Anti-Pattern Sequence describes how institutional failure patterns unfold over time.

When both are present:

  • the Causal Chain may show the issue-level pathway
  • the Anti-Pattern Sequence may show the governance or design-failure pathway
  • both may deserve separate artifacts
  • each should link to the other when useful

Do not collapse Anti-Pattern Sequences into Causal Chains.

Do not turn every Causal Chain into a First Foundation artifact.

Use Artifact Harvest if the update reveals First Foundation implications.

Relationship to Major Projects

Civic Topology Update may feed or emerge from Major Project / Program Artifacts.

Check whether the update belongs to or affects:

  • US Civilizational Forensics
  • Project Atlas / ACAS-A1
  • Cortex Expansion
  • First Foundation volume work
  • Framework Foundations work
  • The War That Didn’t End
  • The River That Broke America
  • Future Fifth Turning / Next High Scenario Project
  • other book-scale or long-running project containers

If yes, preserve the connection in the relevant project notes, PM task, article notes, or Artifact Harvest follow-up.

Output

One or more of:

  • new or updated Topological Area
  • new or updated Issue
  • new or updated Causal Link
  • new or updated Causal Chain
  • new or updated Walkthrough
  • embedded source note
  • embedded limits / common misreadings section
  • project note update
  • PM Task
  • Backlog Item
  • note for Artifact Harvest
  • no update required

Artifact Awareness

During Civic Topology Update, note possible downstream artifacts, but do not force them into CivTop.

Possible downstream artifacts include:

  • First Foundation Pattern
  • Anti-pattern
  • Anti-Pattern Sequence
  • Pattern Application Note / PAN
  • Assessment Report
  • Signal Translation
  • Structural Dynamic Instance
  • Systemic Failure Mode
  • Event Overlay
  • Strategic Intervention candidate
  • embedded load behavior capture
  • embedded Drift Trigger observation
  • embedded Saecular Framing
  • Major Project / Program update
  • PM Task
  • Backlog Item
  • Reconciliation Note

These should be evaluated through Artifact Harvest if they emerge during the update.

Constraints

  • Do not create Civic Topology artifacts casually.
  • Do not create an Issue for every topic.
  • Do not create a Causal Link without a plausible mechanism.
  • Do not create a Causal Chain merely because several topics are related.
  • Do not use Walkthroughs as a substitute for defining Issues and Links.
  • Do not force Load Mechanics, Structural Dynamics, First Foundation, or Strategic Intervention material into Civic Topology.
  • Do not bury First Foundation implications inside CivTop without capturing them elsewhere.
  • Do not treat Civic Topology as the whole diagnosis.
  • Do not skip Artifact Harvest if the update reveals non-CivTop artifacts.

Civic Topology is the map, not the whole framework.

Completion Checklist

Before closing Civic Topology Update, confirm:

  • artifact type was identified
  • new or existing artifact location was chosen
  • relevant Issues were checked before creating new ones
  • relevant Causal Links were checked before creating new ones
  • Topological Area relevance was considered
  • Causal Chain relevance was considered
  • Walkthrough relevance was considered
  • source notes, limits, or common misreadings were considered
  • relevant links were added where useful
  • major project relevance was considered
  • First Foundation overlap was considered
  • possible downstream artifacts were flagged for Artifact Harvest
  • PM Tasks or Backlog Items were created if follow-up is needed

Next Activity

If the update is complete and no additional implications emerged:

→ Close workflow

If the update reveals additional artifacts:

→ Artifact Harvest

If the update reveals article potential:

→ Article Development or PM Task

If the update reveals First Foundation implications:

→ First Foundation Development or Artifact Harvest

If the update reveals Strategic Intervention implications:

→ Strategic Intervention Drafting or PM Task

If the update reveals operational cleanup needs:

→ Workflow Reconciliation or PM Task

Structural Role in Workflow

Artifact Harvest identifies possible Civic Topology updates.

Civic Topology Update converts relationship insight into map structure.

Issues define conditions.

Causal Links define directional relationships.

Causal Chains define multi-step pathways.

Topological Areas organize regions of the map.

Walkthroughs help readers traverse the map.

Civic Topology Update preserves system relationships so later diagnosis, articles, Monitor work, First Foundation development, and major projects can reuse them.