Last reviewed: 2026-05-26
Purpose
This page defines the artifact types used within the NS Content Workflow.
Artifacts are structured outputs, containers, or embedded analytic elements generated or updated through NeuroSaeculum work. This page exists to reduce reliance on memory, prevent missed artifact creation, and clarify where insight should be captured.
The workflow should not treat every insight as a standalone artifact. Some outputs are standalone pages or records. Some are embedded analytic content inside other artifacts. Some are contextual lenses. Some are major program containers that organize many downstream artifacts over time.
Operating Principle
No major analytical activity is complete until relevant artifacts have been considered.
Artifacts define system memory.
Activities define how system memory is produced.
Uncaptured insight decays.
Artifact Classification
Each artifact type may fall into one or more of the following classifications.
Standalone Artifact
A distinct output with its own page, record, registry, or durable location.
Examples:
Embedded Analytic Content
Analysis that should usually be captured inside another artifact rather than as a separate output.
Examples:
- Load behavior capture
- Drift trigger observations
- Saecular framing
- CivMMI contextualization
- Hidden Circuitry interpretation
Contextual Lens
A framework layer used to interpret or qualify other work, but not usually producing a default standalone artifact.
Examples:
Major Program / Container Artifact
A durable, multi-output analytical program that organizes long-term work and generates many downstream artifacts.
Examples:
- US Civilizational Forensics
- Project Atlas / ACAS-A1
- First Foundation volume work
- book-scale forensic projects
Civic Topology Artifacts
Topological Area
Classification: Standalone / composite artifact
Status: Real but occasional; likely becoming recurring
Created by: Civic Topology Update, Artifact Harvest, Article Development
Registry: Civic Topology / Active or Future Topology Areas
A curated region of Civic Topology organized around a recurring structural problem, diagnostic question, or issue cluster.
Topological Areas gather related Issues, Causal Links, Causal Chains, Walkthroughs, articles, and supporting analysis into a coherent region of the map.
Artifact Harvest should ask whether a new analysis:
- belongs to an existing Topological Area
- updates an existing Topological Area
- justifies creating a future or active Topological Area
Issue
Classification: Standalone / atomic CivTop artifact
Status: Real and recurring
Created by: Civic Topology Update, Artifact Harvest
Registry: Civic Topology Issues Index
A systemic condition, pressure, failure, or civic problem represented as a node within Civic Topology.
Issues are not just topics. They are structured conditions that can participate in causal relationships.
Causal Link
Classification: Standalone / atomic CivTop artifact
Status: Real and recurring
Created by: Civic Topology Update, Artifact Harvest
Registry: Civic Topology Causal Links Index
A directional relationship between two Civic Topology Issues.
A Causal Link should explain how one condition contributes to, worsens, enables, constrains, or transforms another condition.
Causal Chain
Classification: Standalone / composite CivTop artifact
Status: Real and recurring
Created by: Civic Topology Update, Artifact Harvest, Article Development
Registry: Civic Topology Causal Chains Index, if maintained separately; otherwise embedded in Topological Areas or walkthroughs
A multi-step transmission path through issues and causal links.
Causal Chains describe how effects move through the civic topology over time or across domains.
Walkthrough
Classification: Standalone / reader-facing CivTop artifact
Status: Real but occasional
Created by: Civic Topology Update, Article Development, Artifact Harvest
Registry: Civic Topology Walkthroughs or relevant Topological Area pages
A guided route through part of the Civic Topology map.
Walkthroughs are distinct from Causal Chains. A Causal Chain describes an analytical pathway. A Walkthrough presents a route through the map for reader understanding.
Issue Update Note
Classification: Embedded page-update behavior
Status: Documented but probably not used as standalone artifact
Created by: Civic Topology Update, Artifact Harvest
Registry: Embedded within Issue pages
An incremental update to an existing Issue page.
Unless Issue Update Notes become separately tracked, they should be treated as ordinary page maintenance rather than a standalone artifact type.
Cortex / Monitoring Artifacts
CT Monitor Log
Classification: Standalone monitoring artifact
Status: Real and recurring
Created by: Monitor Generation
Registry: CT Monitor Log Archive
A structured synthesis of accumulated monitored events, trends, and system signals.
CT Monitor Logs document structural condition, signal accumulation, cross-domain interactions, escalation indicators, and phase-relevant movement.
Structured Diagnostic Triage Record / SDT Record
Classification: Standalone diagnostic artifact
Status: Real and recurring
Created by: Monitor Generation, SDT activity if separated later
Registry: SDT Record Archive
A formal triage output assessing systemic stress, failure modes, phase signals, and escalation posture.
SDT Records help determine whether a situation requires deeper analysis, continued monitoring, or downstream artifact generation.
Signal Translation
Classification: Standalone translation artifact
Status: Real but occasional; high-priority harvest artifact
Created by: Signal Translation Creation, Artifact Harvest
Registry: Signal Translation Index
A reframing artifact that translates signals, concepts, events, or terminology into language that can be analyzed or understood across audiences.
Signal Translations are especially important when technical, moral, political, or narrative language prevents structural understanding.
Artifact Harvest should explicitly ask whether an analysis produced a translation insight worth preserving.
Narrative Clarification Note
Classification: Embedded analytic content
Status: Documented but probably not used as standalone artifact
Created by: Artifact Harvest, Article Development, Signal Translation Creation
Registry: Embedded within articles, Signal Translations, methodology pages, or “Limits / Misreadings” sections
A clarification intended to prevent recurring misreadings of an NS concept or analysis.
Unless this becomes a repeated, separately tracked output, it should usually be folded into Signal Translation, article drafting, methodology guidance, or page-level misreading sections.
NS News and Publication Artifacts
NS News Report
Classification: Standalone publication artifact
Status: Real and recurring
Created by: NS News Report Creation
Registry: NS News Archive
A short-form, event-level structural analysis applying NS framing to a current event.
NS News Reports are narrower than CT Monitor Logs and do not attempt broad system-state synthesis. They capture high-signal events that deserve immediate structural interpretation.
Article
Classification: Standalone publication artifact
Status: Real and recurring
Created by: Article Development
Registry: Articles Index / relevant category archives
A long-form publication exploring a structural theme, mechanism, case, framework concept, or public-facing explanation.
Articles may also generate downstream artifacts through Artifact Harvest.
Narrative Vector
Classification: Standalone or article-like framing artifact
Status: Real but occasional
Created by: Article Development, Artifact Harvest
Registry: Narrative Vectors index, article archive, or relevant framework section
A narrative vehicle that carries an NS concept through an accessible explanatory structure.
Narrative Vectors are not merely essays. They are structured explanatory arcs designed to make a framework insight emotionally, morally, or cognitively legible.
What’s New Entry
Classification: Standalone release/publication artifact
Status: Real but occasional
Created by: Version Release, Workflow Page Update, publication maintenance
Registry: What’s New Archive
A public-facing summary of meaningful framework, site, or artifact updates.
First Foundation Artifacts
Pattern
Classification: Standalone First Foundation artifact
Status: Real but occasional; high-priority harvest artifact
Created by: First Foundation Development, Artifact Harvest
Registry: First Foundation Pattern Library
A reusable institutional design structure.
Patterns describe constructive structures that can help institutions absorb stress, resist capture, improve feedback, or increase adaptive capacity.
Anti-Pattern
Classification: Standalone First Foundation artifact
Status: Real but occasional; high-priority harvest artifact
Created by: First Foundation Development, Artifact Harvest
Registry: First Foundation Anti-Pattern Library, if maintained
A recurring institutional failure structure.
Anti-patterns describe repeatable design failures, governance failures, capture mechanisms, or institutional behaviors that increase fragility or dysfunction.
Proto-Pattern
Classification: Provisional First Foundation artifact
Status: Real but occasional
Created by: First Foundation Development, Artifact Harvest
Registry: Proto-pattern list or relevant backlog
A candidate pattern not yet mature enough for full formalization.
Proto-patterns preserve promising institutional design insights without prematurely canonizing them.
Anti-Pattern Sequence
Classification: Standalone sequence artifact
Status: Real but occasional; high-priority harvest artifact
Created by: First Foundation Development, Artifact Harvest
Registry: Anti-Pattern Sequence index, if maintained
An ordered progression of anti-patterns or institutional failures that form a recognizable structural pathway.
Anti-Pattern Sequences may correspond to, overlap with, or help explain Civic Topology Causal Chains. 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, while the Anti-Pattern Sequence shows the recurring governance or design-failure pathway behind it.
Artifact Harvest should ask:
- Does this Causal Chain reveal an Anti-Pattern Sequence?
- Does this Anti-Pattern Sequence imply a Causal Chain that should be captured in Civic Topology?
- Does Load Mechanics help explain how strain moves through the sequence?
Assessment Report
Classification: Standalone applied analysis artifact
Status: Real but occasional
Created by: First Foundation Development, Article Development, Artifact Harvest
Registry: Assessment Reports index, if maintained
An applied First Foundation analysis of a real institution, system, proposal, policy, or governance structure.
Assessment Reports may use patterns, anti-patterns, PANs, CivMMI context, Structural Dynamics, and Civic Topology relationships.
Pattern Application Note / PAN
Classification: Standalone applied First Foundation artifact
Status: Real but occasional; high-priority harvest artifact
Created by: Artifact Harvest, First Foundation Development
Registry: PAN index or relevant pattern pages
A note documenting how a First Foundation pattern applies to a specific case, institution, event, or failure.
PANs preserve applied pattern insight without requiring a full Assessment Report.
Framework Foundations Artifacts and Embedded Analytic Content
Drift Trigger
Classification: Standalone framework concept; observations often embedded
Status: Real but occasional
Created by: Framework Foundations Development, Artifact Harvest
Registry: Drift Triggers page or registry
A directional pressure that pushes a system toward drift.
The concept is a real Framework Foundations artifact. Individual drift-trigger observations may usually be embedded inside CT Monitor Logs, SDT Records, Event Overlays, articles, or Artifact Harvest notes.
Drift Trigger Observation
Classification: Embedded analytic content
Status: Previously documented as “Drift Trigger Note”; probably not standalone by default
Created by: Artifact Harvest, Monitor Generation, SDT, Article Development
Registry: Embedded within relevant artifacts
A specific observation of a Drift Trigger appearing, strengthening, or changing.
Use embedded capture unless a registry of drift-trigger instances is later created.
Load Behavior Capture
Classification: Embedded analytic content
Status: Embedded, not standalone by default
Created by: Artifact Harvest, Monitor Generation, SDT, Article Development, First Foundation analysis
Registry: Embedded within relevant artifacts
Captures how strain behaves in a case.
Typical load behaviors include:
- concentration
- distribution
- transfer
- accumulation
- latency
- visibility
- conversion
- lock-in
- relief or non-relief
Load Behavior Capture replaces the weaker idea of a default standalone “Load Behavior Note.”
Load Mechanics should usually appear inside another artifact, such as:
- Structural Dynamic Instance
- Systemic Failure Mode
- Event Overlay
- FF Assessment Report
- Pattern Application Note
- CT Monitor Log
- SDT Record
- article or forensic analysis
Structural Dynamic
Classification: Standalone Framework Foundations artifact
Status: Real but occasional
Created by: Framework Foundations Development, Artifact Harvest
Registry: Structural Dynamics index
A named recurring structural behavior within systems.
Structural Dynamics describe how system structures behave under pressure, not merely what happened in one event.
Structural Dynamic Instance
Classification: Standalone or embedded case artifact
Status: Real but occasional; high-priority harvest artifact
Created by: Artifact Harvest, Monitor Generation, SDT, Article Development
Registry: Structural Dynamics pages, instance registry, or embedded in relevant artifacts
A real-world instance of a defined Structural Dynamic.
These should be treated as high-priority harvest material because they strengthen the evidentiary base of the framework.
Systemic Failure Mode
Classification: Standalone Framework Foundations artifact
Status: Real but occasional; high-priority harvest artifact
Created by: Framework Foundations Development, Artifact Harvest
Registry: Systemic Failure Modes index
A named recurring mode of systemic failure.
Systemic Failure Modes may emerge from repeated CT Monitor signals, SDT findings, articles, Civic Topology work, or First Foundation analysis.
Event Overlay
Classification: Standalone diagnostic / Foundations artifact
Status: Real but occasional; high-priority harvest artifact
Created by: Artifact Harvest, Event analysis, Monitor Generation, Article Development
Registry: Event Overlays index
An event-specific interpretive overlay that modifies how a case should be understood.
Event Overlays are easy to miss because they may emerge during analysis rather than intake. Artifact Harvest should explicitly check for them.
Saecular Framing
Classification: Embedded analytic content
Status: Embedded, not standalone by default
Created by: Monitor Generation, SDT, Article Development, forensic analysis
Registry: Embedded within relevant artifacts
Cyclical-pressure interpretation from Saecular Mechanics.
Saecular Framing may appear inside CT Monitor Logs, SDT Records, articles, Narrative Vectors, forensic assessments, or book-scale analysis.
It should not become a standalone artifact by default unless repeated use justifies a formal artifact type.
Strategic Intervention Artifacts
Strategic Intervention Class
Classification: Standalone system artifact
Status: Documented and probably should be used
Created by: Strategic Intervention Drafting, Artifact Harvest
Registry: Strategic Interventions index
A mechanism-level intervention concept independent of a single political or institutional context.
Strategic Intervention Classes should remain downstream of diagnosis. Artifact Harvest may flag candidates, but formal drafting should occur only when the diagnostic foundation is strong enough.
Strategic Intervention Instance
Classification: Standalone system artifact
Status: Documented and probably should be used
Created by: Strategic Intervention Drafting, Artifact Harvest
Registry: Strategic Intervention pages or instance registry
A context-bound example or application of a Strategic Intervention Class.
Instances should preserve the distinction between diagnosis and strategy.
Contextual / Non-Default Artifact Fields
CivMMI
Classification: Contextual lens
Status: Contextual only by default
Created by: Not usually created as standalone artifact
Registry: CivMMI field pages, examples if maintained
CivMMI provides capacity, maturity, fragility, and civilizational-development context.
It does not require a default recurring “CivMMI Note.” CivMMI should usually appear inside other artifacts, such as:
- Assessment Reports
- articles
- forensic analyses
- renewal discussions
- FF pattern applications
- long-form project work
Create a standalone CivMMI artifact only if a recurring use case emerges.
Hidden Circuitry
Classification: Contextual lens
Status: Contextual only by default
Created by: Not usually created as standalone artifact
Registry: Hidden Circuitry pages or articles
Hidden Circuitry provides motivational, neurochemical, narrative, and stress-regulation interpretation.
It usually functions as embedded interpretive context rather than as a recurring standalone workflow artifact.
Governance / Operations Artifacts
PM Task
Classification: Standalone governance artifact
Status: Real but occasional
Created by: Artifact Harvest, Article Development, Workflow Reconciliation, general project management
Registry: PM backlog / task tracker
A tracked work item for future action.
PM Tasks are created when useful work is identified but cannot or should not be completed immediately.
Backlog Item
Classification: Standalone governance artifact
Status: Real but occasional
Created by: Artifact Harvest, Workflow Reconciliation, project planning
Registry: Backlog / task tracker
A deferred item requiring future attention.
Backlog Items may include page updates, article ideas, artifact gaps, methodology debt, missing templates, or future analysis tasks.
Reconciliation Note
Classification: Governance / maintenance artifact
Status: Documented and probably should be used
Created by: Workflow Reconciliation, artifact inventory reviews, backlog review passes
Registry: Internal notes, PM tracker, or workflow maintenance page
A record of findings from a reconciliation pass.
Reconciliation Notes are useful when reviewing:
- stale pages
- missing artifacts
- activity/artifact mismatches
- methodology/template alignment
- backlog drift
- cross-chat synthesis
Version Release Note
Classification: Standalone governance / release artifact
Status: Real but occasional
Created by: Version Release
Registry: Version history or internal release notes
A structured record of framework or site version changes.
Workflow Page Update
Classification: Governance maintenance action
Status: Real but occasional
Created by: Workflow Reconciliation, Artifact Harvest, operational practice changes
Registry: Embedded in updated workflow pages
A change to the NS Content Workflow, Activities, Artifacts, Methodologies, Protocols, Guides, or Templates pages.
Usually this is not a standalone artifact unless captured as a Reconciliation Note or Version Release Note.
Major Project / Program Artifacts
Major Project / Program Artifacts are durable, multi-output analytical programs that organize large bodies of NeuroSaeculum work over time.
They are not usually produced by a single activity. Instead, they coordinate many activities and generate multiple downstream artifacts.
Artifact Harvest should ask whether new work belongs to, updates, or creates material for a Major Project / Program Artifact.
US Civilizational Forensics
Classification: Major program / container artifact
Status: Real and developing
Created by: Long-form analysis, CT Monitor continuity, Civic Topology expansion, Artifact Harvest, book-scale development
Registry: US Civilizational Forensics hub or internal project page, if maintained
A long-arc forensic analysis of U.S. civilizational development, unresolved historical load, institutional drift, and current Crisis dynamics.
Consumes and generates:
- CT Monitor Logs
- SDT Records
- Civic Topology artifacts
- Structural Dynamics
- Systemic Failure Modes
- Event Overlays
- Narrative Vectors
- FF Pattern Applications
- Assessment Reports
- Articles
- book-scale outputs
Project Atlas / ACAS-A1
Classification: Major program / container artifact
Status: Real and developing
Created by: Project Atlas development, Civic Topology work, macro-diagnostic analysis, Artifact Harvest
Registry: Project Atlas internal development notes
A macro-scale diagnostic project focused on civilizational activity, production quality, GDP distortion, maintenance burden, household strain, debt, and future-capacity drawdown.
Cortex Expansion
Classification: Major program / container artifact
Status: Real and developing
Created by: Cortex development, CT Monitor work, Crisis Tracker expansion, Artifact Harvest
Registry: Cortex or Crisis Tracker project notes
A system-expansion program that broadens CT Monitor / Crisis Tracker into a larger sensing and longitudinal analysis system.
First Foundation Volume Work
Classification: Major program / container artifact
Status: Real and developing
Created by: First Foundation development, Artifact Harvest, pattern work, article development
Registry: First Foundation volume/project notes
A long-running program organizing First Foundation patterns, anti-patterns, pattern sequences, assessment reports, and institutional design work into formal volumes.
Framework Foundations / Volume 0 Work
Classification: Major program / container artifact
Status: Real and developing
Created by: Framework Foundations development, Artifact Harvest, module refinement
Registry: Framework Foundations project notes
A long-running program organizing foundational NS structure, including Saecular Mechanics, Load Mechanics, Drift Triggers, Structural Dynamics, Narrative Vectors, Event Overlays, Systemic Failure Modes, and related modules.
The War That Didn’t End
Classification: Major program / container artifact
Status: Planned / developing
Created by: US Civilizational Forensics, article development, forensic analysis
Registry: Book-scale project notes
A book-scale forensic project examining the U.S. Civil War, Reconstruction, unresolved structural load, and their long downstream effects.
The River That Broke America
Classification: Major program / container artifact
Status: Planned / developing
Created by: US Civilizational Forensics, article development, forensic analysis
Registry: Book-scale project notes
A book-scale forensic project reconstructing the U.S. Crisis era through river-system metaphor and NS structural analysis.
Future Fifth Turning / Next High Scenario Project
Classification: Major program / container artifact
Status: Planned / developing
Created by: Scenario development, article development, Hidden Circuitry, First Foundation, CivMMI, Artifact Harvest
Registry: Scenario project notes
A future-facing scenario project exploring the possible shape of a post-Crisis High / future Fifth Turning using NS and Strauss-Howe-derived structural logic.
Artifact Harvest Reminder
After completing any major activity — especially Monitor Generation, NS News Report Creation, Article Development, or any use of the NS Diagnostic Process — review this page and determine whether the work produced or updated any relevant artifact.
At minimum, ask:
- Did this create or update a Civic Topology artifact?
- Did this produce a Signal Translation?
- Did this reveal a Structural Dynamic instance?
- Did this reveal a Systemic Failure Mode?
- Did this require an Event Overlay?
- Did this imply a First Foundation Pattern, Anti-Pattern, Anti-Pattern Sequence, Assessment Report, or PAN?
- Did this suggest a Strategic Intervention Class or Instance?
- Did this require embedded load behavior capture, drift trigger observation, or saecular framing?
- Did this belong to or update a Major Project / Program Artifact?
- Did this create a PM Task, Backlog Item, Reconciliation Note, Version Release Note, or What’s New Entry?
If no artifact is required, explicitly close the harvest:
Harvest complete. No additional artifacts required.
Last reviewed: 2026-05-26
Purpose
This page defines the operational activities used to generate, update, publish, and maintain artifacts within NeuroSaeculum.
Each activity has its own implementation page.
This page serves as the activity interface index. Activity pages contain implementation details, inputs, outputs, required artifacts, decision points, methodology/protocol references, guide/template references, and next-step links.
Activities are grouped by function:
- Exploration
- Structured Intake
- Synthesis
- Artifact Expansion
- Publication
- Release / Governance
Activity pages define workflow placement and operational handoffs. Where governing methodology, protocol, guide, or template pages exist, individual activity pages should link to them rather than duplicate them.
Operations Context
For how workflow activities relate to the NS Diagnostic Process and overall NS Operations, see:
➜ See: NS Operations Overview
Exploration Activities
News Discussion
Exploratory evaluation of headlines, articles, and events before structured intake.
Used to prevent premature Monitor or artifact pollution.
➜ See: News Discussion
NS News Assessment
Determines whether a discovered event warrants a standalone NS News Report rather than waiting for Monitor synthesis.
➜ See: NS News Assessment
Structured Intake Activities
Event Intake Qualification
Determines whether a discovered event warrants structured memory entry.
Qualifying events are entered into the Intake Buffer (ODT file).
➜ See: Event Intake Qualification
Structured Event Intake
Formal entry of a qualifying event into the Intake Buffer (ODT file).
Creates a one-page-per-event record for accumulation.
➜ See: Structured Event Intake
Synthesis Activities
Monitor Threshold Assessment
Evaluates accumulated Intake Buffer signals against defined generation thresholds.
Determines whether a CT Monitor Log should be generated.
➜ See: Monitor Threshold Assessment
Monitor Generation
Produces a CT Monitor Log and corresponding SDT Record when threshold conditions are met.
➜ See: Monitor Generation
Artifact Expansion Activities
Artifact Harvest
Examines a completed output for reusable structural value and routes it to the appropriate framework artifacts — creating, updating, embedding, or explicitly closing with no artifact required. The anti-loss checkpoint that no primary output should skip.
Ensures insight becomes system structure.
➜ See: Artifact Harvest
Civic Topology Update
Creates or updates Civic Topology artifacts, including Topological Areas, Issues, Causal Links, Causal Chains, and Walkthroughs.
➜ See: Civic Topology Update
Strategic Intervention Drafting
Creates or refines Strategic Intervention classes or instances.
➜ See: Strategic Intervention Drafting
Signal Translation Creation
Produces Signal Translation artifacts from structural observations.
➜ See: Signal Translation Creation
Publication Activities
NS News Report Creation
Creates a short-form NS News Report in accordance with the NS News Methodology.
➜ See: NS News Report Creation
Article Development
Development and publication of long-form NS articles.
➜ See: Article Development
Release / Governance Activities
Version Release
Formal framework version increment and publication of release notes.
➜ See: Version Release
Deferred Operations Debt
Tracks operational activities, interfaces, and governance mechanisms intentionally deferred because they are not yet needed for current workflow load.
Used to keep known structural debt visible without expanding the workflow prematurely.
➜ See: Deferred Operations Debt
Structural Notes
Exploration → Intake → Synthesis → Artifact Expansion → Publication / Release
No synthesis should occur without Intake.
No primary output should close without Artifact Harvest.
Activities define workflow placement. Methodologies, protocols, guides, and templates define execution standards.
Where a governing methodology, protocol, guide, or template exists, the relevant activity page should reference it rather than duplicate it.