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.

When topology-worthy material is not yet developed enough to qualify as a persistent Issue, Causal Link, Causal Chain, or Walkthrough, preserve it in the appropriate Future Topology Area rather than creating a provisional version of the artifact.

Governing References

Use these pages when performing Civic Topology Update:

This activity defines the workflow placement for creating and updating persistent Civic Topology artifacts.

Civic Topology maps what is connected to what.

Use the Civic Topology Methodology to determine map structure, and the relevant artifact guidance to determine how that structure should be represented and persisted.

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
  • Topology 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 This Activity May Update

Civic Topology Update may create or revise persistent artifacts defined by the Civic Topology Field and its governing documentation.

These include:

  • Issues
  • Causal Links
  • Causal Chains
  • Walkthroughs
  • Active Topology Areas
  • Future Topology Areas
  • Topology Clusters

Feedback Loops are classified forms of Causal Chains and are handled through Causal Chain analysis and persistence.

Use the Civic Topology Methodology to identify and classify the underlying map structure. Use the governing artifact documentation to determine qualification, construction, lifecycle, and publication requirements.

Issues

Create or update an Issue when the analysis identifies a condition that qualifies under the Civic Topology Issue Writing Guidelines and preservation in the topology is warranted.

Causal Links

Create or update a Causal Link when the methodology identifies a qualifying directional relationship between existing or newly created Issues.

Follow the Civic Topology Causal Link Writing Guidelines for mechanism, directionality, evidence, scope, and artifact construction.

Causal Chains

Create or update a Causal Chain when the methodology identifies a multi-step pathway worth preserving as reusable topology.

If downstream effects return to and materially affect an earlier Issue, record the chain as a Feedback Loop and apply the appropriate loop classification.

Check for overlap with First Foundation Anti-Pattern Sequences without collapsing one artifact type into the other.

Walkthroughs

Create or update a Walkthrough when a particular explanatory traversal through existing topology will materially improve reader understanding.

A Walkthrough does not own the topology it traverses. Multiple Walkthroughs may traverse the same Causal Chain or other shared structures, and a Walkthrough may cover only part of a chain or combine connected portions of multiple structures.

Consider whether the material is better expressed as an article rather than as a reusable map traversal.

Topology Areas

Route material to an existing Active or Future Topology Area according to the governing Area documentation.

Create a new Future Topology Area when provisional material warrants a stable development space.

Creation or promotion of an Active Topology Area is governed by the Active Topology Areas page and is not determined by routine Civic Topology Update.

Routine addition of material to a Future Topology Area does not trigger a development or promotion review.

Topology Clusters

Create or update a Topology Cluster only when the criteria defined on the Topology Clusters page are met.

Cluster stabilization, membership, and lifecycle are governed there and are not repeated in this activity.

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 Issue
  • new or updated Causal Link
  • new or updated Causal Chain
  • updated Feedback Loop classification
  • new or updated Walkthrough
  • new or updated Active Topology Area
  • new or updated Future Topology Area
  • new or updated Topology Cluster
  • 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 treat a Feedback Loop as independent of the Causal Chain that forms it.
  • Do not create or promote an Active Topology Area through routine intake alone.
  • Do not create a Topology Cluster outside the criteria defined by the Topology Clusters page.
  • 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:

  • the artifact type or update target was identified
  • the relevant Civic Topology Methodology was applied where structural identification was required
  • applicable artifact guidance was checked before creating a new artifact
  • relevant existing Issues were checked before creating new ones
  • relevant existing Causal Links were checked before creating new ones
  • the causal relationships are sufficiently clear to support persistence
  • Issues and mechanisms have been separated rather than collapsed into one artifact
  • Causal Chain relevance was considered
  • Feedback Loop classification was considered for any qualifying Causal Chain
  • Walkthrough relevance was considered
  • Active or Future Topology Area relevance was considered
  • Topology Cluster relevance was considered
  • source notes, limits, evidence caveats, 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
  • the resulting artifact boundaries are clear enough that the topology can be reused without reconstructing the analysis from scratch

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 Methodology identifies and structures the underlying causal topology.

Civic Topology Update converts preservable topology into persistent map structure.

Issues define conditions.

Causal Links define directional relationships.

Causal Chains define multi-step pathways; some chains form Feedback Loops.

Topology Areas organize coherent regions of the map.

Topology Clusters organize related Areas into higher-order views.

Walkthroughs provide reader-facing traversals through existing topology.

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