Skip to content

Artifact Harvest

Purpose

Artifact Harvest converts completed analysis into durable NeuroSaeculum system memory.

It identifies reusable structural findings, routes them to the appropriate framework artifacts, preserves embedded mechanics and contextual value, and creates follow-up work when further diagnosis or formalization is needed.

Artifact Harvest is not a summary of the completed work. It is the point at which the analysis is examined for material that should persist beyond the immediate output.

Governing References

Use these pages when performing Artifact Harvest:

When the harvest may create, name, rename, materially redefine, merge, split, promote, retire, or reconcile a concept, also consult:

This activity defines the harvest checkpoint.

Artifact pages define what can be harvested.

The Glossary provides the framework’s interpretive grammar and should be consulted when naming or classifying artifacts.

Advanced Vocabulary and the NS Model of Civilization should be retrieved when concept classification or reconciliation is involved. They are not mandatory reading for every harvest.

Methodologies, protocols, guides, and templates define execution standards.

Inputs

Artifact Harvest may follow:

  • Monitor Log creation
  • Structural Dynamics Tracking record creation
  • NS News Report creation
  • Article creation
  • NS Diagnostic Process output
  • assessment or investigative work
  • framework-development work
  • other analysis that may contain reusable system value

The completed source output should remain available during harvest.

Where the analysis relies on source documents, those sources should also remain available so the harvested artifact does not exceed what the evidence supports.

Core Question

What reusable system value did this work produce, and where should that value live within NeuroSaeculum?

The answer may be:

  • a new artifact
  • an update to an existing artifact
  • an instance or evidence note
  • an embedded mechanics observation
  • a contextual or interpretive connection
  • a Working Concept update
  • a reconciliation note
  • a PM Task or Backlog Item
  • no additional artifact

Do not assume every completed output must generate a new standalone artifact.

Prior-Art Load Gate

Before novelty or reuse dispositions are made, identify the artifact categories plausibly implicated by the source.

For each implicated category, retrieve and acknowledge the authoritative catalog, register, or index used to govern that artifact type. Open potentially matching entries as needed to test whether the candidate is new, overlapping, specialized, merged, or an instance of existing prior art.

Load only the catalogs required by the categories implicated in the source. Do not load unrelated catalogs solely to complete the activity.

A candidate may receive a novelty or prior-art disposition only when the governing catalog for its category has been successfully loaded and searched in the current session.

If the required catalog cannot be retrieved, appears stale, or cannot be verified against its canonical version:

  • do not infer novelty from absence in the current context
  • mark the candidate Deferred — Prior-Art Check Incomplete
  • create or route it to a prior-art scan PM Task
  • request the authoritative page or document directly when appropriate

Framework Prior-Art Check

Before treating any category below as producing a new artifact, check whether NeuroSaeculum already contains:

  • the same term
  • a close synonym
  • a broader or narrower version
  • the same mechanism under another artifact type
  • the same condition as a consequence, signature, cross-pattern relationship, or embedded mechanic
  • an existing artifact that should be updated rather than duplicated

Consult the Glossary and relevant framework references when naming or classifying artifacts.

Where concept relationships remain unclear, create a reconciliation note or follow-up task rather than forcing immediate placement.

Possible dispositions include:

  • update an existing artifact
  • add an instance or supporting example
  • add a cross-reference
  • specialize or narrow an existing concept
  • merge related concepts
  • retain a distinct Working Concept
  • create a new candidate
  • defer classification pending a separate diagnostic pass
  • reject the proposed concept or relationship

Absence from the analyst’s current context is not evidence that the concept is absent from NeuroSaeculum.

Artifact Categories to Evaluate

During harvest, explicitly check the following categories.

Not every category requires an artifact. The purpose is to prevent reusable value from being lost because no one asked whether it was present.

Civic Topology

Did the material reveal or strengthen a relationship among institutions, actors, incentives, resources, constraints, populations, or feedback systems?

Check for:

  • a new node
  • a new edge or causal pathway
  • a previously hidden dependency
  • load transfer between systems
  • feedback between institutions or populations
  • a boundary condition
  • a topology area requiring expansion
  • evidence supporting a Future Topology Area
  • evidence that an existing topology area should be split, merged, narrowed, or cross-linked

Ask:

  • What is connected to what?
  • Through which institution, rule, market, norm, or infrastructure does the relationship operate?
  • Is the connection direct, mediated, delayed, conditional, or reciprocal?
  • Does the case expose a missing region in an existing topology?
  • Is this relationship durable enough to preserve beyond the immediate event?

Output may include:

  • Civic Topology update
  • topology instance
  • new edge or node
  • Future Topology Area candidate
  • cross-link between topology areas
  • PM Task for later mapping
  • no Civic Topology artifact required

Signal Translation

Did the material reveal a recurring way that structural conditions become legible through public events, institutional behavior, rhetoric, data, or lived experience?

Check for:

  • a structural condition becoming visible through a concrete signal
  • a misleading surface explanation that obscures deeper mechanics
  • a recurring translation gap between public language and system behavior
  • a signal whose meaning changes depending on scale or context
  • a signal that appears local but reflects wider structural pressure
  • a signal that may be useful in future Monitor or diagnostic work

Ask:

  • What is the visible signal?
  • What structural condition may be producing it?
  • What common interpretation should be resisted?
  • What evidence would distinguish signal from noise?
  • Is the translation reusable across other cases?

Output may include:

  • Signal Translation artifact
  • update to an existing Signal Translation
  • example or boundary note
  • PM Task for later development
  • no Signal Translation artifact required

Structural Dynamics

Did the material reveal a recurring way that pressure, constraint, adaptation, delay, or feedback moves through a system over time?

Check for:

  • a possible new Structural Dynamic
  • an instance of an existing Dynamic
  • a new phase or transition
  • acceleration or deceleration
  • reinforcing or balancing feedback
  • lag accumulation
  • threshold behavior
  • phase change
  • adaptation or counter-adaptation
  • load migration
  • restoration delay
  • correction failure
  • dynamic interaction across scales

Ask:

  • What is changing over time?
  • What drives the change?
  • What delays or accelerates it?
  • What feedback reinforces or limits it?
  • Does the pattern recur beyond this case?
  • Is this a Dynamic, or merely a one-time sequence?

Output may include:

  • Structural Dynamic update
  • new Dynamic candidate
  • Dynamic instance
  • boundary or counterexample
  • embedded Dynamic note
  • PM Task for comparative diagnosis
  • no Structural Dynamic artifact required

Systemic Failure Modes

Did the material reveal or strengthen a recurring way that systems degrade, lose capacity, amplify harm, suppress correction, or displace unresolved stress?

Check for:

  • a possible new Systemic Failure Mode
  • an instance of an existing Failure Mode
  • overlap with an existing Anti-Pattern
  • a failure expression produced by several mechanisms
  • stress migration rather than resolution
  • loss of adaptive capacity
  • suppression of corrective feedback
  • a candidate failure condition in which formal structure, authority, protection, or entitlement persists while practical function or realization degrades
  • a condition that persists across domains or institutional forms
  • a recurring breakdown that may not reduce to an existing Anti-Pattern and requires prior-art review or separate diagnosis before classification

Ask:

  • What repeatedly breaks?
  • Is the breakdown a mechanism, a system condition, an outcome, or an institutional design?
  • Does an existing Anti-Pattern already explain it?
  • Does the case suggest a distinct failure expression, or is it better understood as an instance, consequence, signature, or combination of existing mechanics, Dynamics, and Anti-Patterns?
  • What would not count as an instance?
  • Is the pattern sufficiently bounded to avoid explaining ordinary dysfunction in general?

Output may include:

  • Systemic Failure Mode artifact
  • update to an existing Failure Mode
  • Failure Mode instance
  • relationship to an Anti-Pattern
  • boundary or non-example
  • reconciliation note
  • PM Task for separate diagnosis
  • no Systemic Failure Mode artifact required

Event Overlays

Did the material reveal, strengthen, challenge, or provide an instance of a named collective-mood lens that shapes how a set of events is interpreted, amplified, or ignored?

Event Overlays, such as Civic Grief, Civic Shame, or Civic Numbness, describe collective mood dynamics across events. They are not general descriptions of how an event fits into a larger structural sequence.

Check for:

  • an instance of an existing Event Overlay
  • a recurring collective mood state across multiple events
  • a shift in how events are publicly interpreted, amplified, minimized, or ignored
  • evidence that similar events are producing different reactions because the surrounding collective mood has changed
  • a boundary or counterexample for an existing Overlay
  • a possible new Overlay requiring comparative evidence
  • overlap with a Narrative Vector, Contextual Lens, or other interpretive artifact

Ask:

  • What collective mood state is present?
  • Does it operate across a set of events rather than describe one actor’s reaction?
  • How does the mood alter interpretation, attention, amplification, or response?
  • Is the observation already covered by an existing Overlay?
  • Is this genuinely a mood dynamic, or is it instead a structural sequence, contextual condition, rhetoric, narrative movement, or mechanics observation?
  • Is there enough cross-event evidence to justify preserving it beyond the immediate case?

Output may include:

  • Event Overlay instance
  • update to an existing Overlay
  • boundary, non-example, or counterexample
  • possible new Overlay candidate
  • cross-reference to a Narrative Vector or Contextual Lens
  • PM Task for comparative development
  • no Event Overlay artifact required

Do not use Event Overlays merely to describe where an event sits within a larger system or sequence. Route structural relationships to Civic Topology, temporal behavior to Structural Dynamics, and load, displacement, or lag observations to the relevant mechanics.

Drift, Load, and Saecular Mechanics

Did the material reveal embedded mechanics that should be preserved even if no standalone artifact is required?

Check for:

  • load accumulation
  • load transfer
  • load concentration
  • burden displacement
  • buffer depletion
  • loss of slack
  • future-capacity drawdown
  • delayed correction
  • lag accumulation
  • phase mismatch
  • restoration debt
  • adaptation debt
  • unresolved stress migration
  • threshold or tipping behavior
  • asymmetry between rapid disruption and slow repair
  • compensation mechanisms
  • temporary stabilization that increases later vulnerability
  • cross-scale interaction
  • saecular pressure or cohort adaptation

Ask:

  • What load entered the system?
  • Where did it go?
  • What absorbed it?
  • Was the load resolved, deferred, hidden, or displaced?
  • Which buffer or capacity was consumed?
  • What lag or time asymmetry shaped the result?
  • Did the system preserve present output by drawing down future capacity?
  • Does the mechanic belong inside an existing artifact rather than as a standalone page?

Output may include:

  • embedded Load Mechanics note
  • embedded Saecular Mechanics note
  • update to an existing mechanics page
  • example for future methodology development
  • PM Task for formalization
  • no separate mechanics artifact required

First Foundation

Did the material reveal an institutional design, recurring design failure, corrective structure, or governance arrangement relevant to First Foundation development?

Check for:

  • Pattern candidate
  • Anti-Pattern candidate
  • Meta-Pattern relationship
  • Pattern instance
  • Anti-Pattern instance
  • design constraint
  • implementation condition
  • failure pathway
  • tradeoff
  • counterforce
  • institutional role requiring protection
  • candidate repair structure
  • evidence that an existing Pattern or Anti-Pattern needs revision

Ask:

  • Is this a repeated institutional design rather than only an outcome?
  • What function is the design intended to perform?
  • Under what conditions does it succeed or fail?
  • Is the structure descriptive, diagnostic, or prescriptive?
  • Is the proposed response mature enough for Pattern development?
  • Does the evidence support a reusable design, or only a design question?

Output may include:

  • Pattern or Anti-Pattern update
  • Pattern or Anti-Pattern candidate
  • instance or implementation note
  • design constraint
  • First Foundation development task
  • embedded design question
  • no First Foundation artifact required

Do not create an FF Pattern merely because a failure has been identified. The institutional response must be sufficiently developed, bounded, and reusable.

Strategic Interventions

Did the material reveal a plausible leverage point or intervention that may alter system behavior?

Check for:

  • intervention candidate
  • leverage point
  • counterforce
  • sequencing requirement
  • restoration pathway
  • capacity-building opportunity
  • feedback correction
  • institutional guardrail
  • dependency that must be addressed before intervention
  • risk of burden displacement or unintended effects

Ask:

  • What structural mechanism would the intervention change?
  • Does it address the cause, the transmission path, or only the visible symptom?
  • What capacity would be required?
  • What actors could implement it?
  • What new risks or load transfers could it create?
  • Is the intervention mature enough to preserve, or should it remain an open design question?

Output may include:

  • Strategic Intervention candidate
  • update to an existing intervention
  • intervention constraint or prerequisite
  • PM Task for later design
  • no Strategic Intervention artifact required

Do not promote an intervention merely because it is politically desirable or intuitively appealing.

Contextual Lenses

Did the material reveal a perspective, historical context, comparative frame, or interpretive lens that improves diagnosis without becoming a standalone structural artifact?

Check for:

  • historical comparison
  • cohort or generational context
  • legal or constitutional frame
  • cultural interpretation
  • regional variation
  • professional or institutional perspective
  • communication frame
  • boundary condition
  • interpretive caution
  • analogy that clarifies but should not be treated as mechanism

Ask:

  • Does the lens improve understanding of the structure?
  • Does it explain variation without becoming the primary mechanism?
  • Is it durable enough to preserve?
  • Should it remain embedded in the source output?
  • Would a separate contextual artifact improve later work?

Output may include:

  • Contextual Lens artifact
  • update to an existing lens
  • embedded contextual note
  • cross-reference
  • PM Task for later development
  • no contextual artifact required

Working Concepts

Did the material or analysis reveal, refine, challenge, or add evidence to a Working Concept?

Working Concepts preserve reusable distinctions, provisional mechanisms, recurring observations, and cross-cutting ideas that are analytically useful but do not yet have a settled formal classification.

They should also be used when forcing immediate classification would distort or prematurely narrow the concept.

Working Concepts are not merely a fallback for ideas that do not fit elsewhere. Some may remain valuable analytical distinctions without becoming a Structural Dynamic, Systemic Failure Mode, Pattern, Anti-Pattern, or other formal artifact.

Check for:

  • possible new Working Concept
  • new instance of an existing Working Concept
  • refinement of an existing definition
  • clearer boundary or non-example
  • counterexample or failed application
  • overlap with an existing term or artifact
  • evidence supporting continued provisional use
  • evidence supporting merge, split, promotion, or retirement
  • concept requiring historical recovery
  • concept requiring prior-art reconciliation

Ask:

  • Is the idea reusable beyond the immediate case?
  • Is it stable enough to preserve?
  • Does an existing Working Concept already cover it?
  • Does the term or a close equivalent already appear elsewhere in NeuroSaeculum?
  • Does the case add genuine evidence, or merely repeat an already documented example?
  • Did the case reveal a boundary, non-example, or counterexample?
  • Is a Framework Prior-Art Scan needed?
  • Is a separate NS Diagnostic Process pass warranted?
  • Should follow-up work be created rather than forcing immediate classification?

If the concept is reusable, record its possible future classification—such as a mechanism, Structural Dynamic, condition, consequence, signature, Systemic Failure Mode, design structure, or vocabulary term—or state explicitly that its destination remains open.

Output may include:

  • new Working Concept
  • update to an existing Working Concept
  • Working Concept instance or evidence note
  • definition update
  • boundary or non-example
  • counterexample or failed application
  • prior-art note
  • reconciliation note
  • PM Task for comparative diagnosis, historical recovery, merge, split, promotion, or retirement review
  • no Working Concept artifact required

Major Project or Program

Did the material reveal work that belongs inside an existing major project or program, or justify creation of a new one?

Check for:

  • contribution to an existing project
  • project dependency
  • project-level evidence
  • required follow-up work
  • missing deliverable
  • sequencing change
  • project boundary issue
  • relationship to Cortex, CT Monitor, Civic Topology, First Foundation, Renewal, or another active program

Ask:

  • Is this an artifact, or is it work that should be routed into a project?
  • Does the project already have a place for it?
  • Does the finding change scope, sequencing, or priority?
  • Is a PM Task sufficient?
  • Does the project documentation require an update?

Output may include:

  • project update
  • PM Task
  • Backlog Item
  • project cross-reference
  • sequencing or dependency note
  • no project action required

Governance / Operations

Did the material expose a workflow, documentation, maintenance, governance, or operational issue?

Check for:

  • workflow-page update
  • methodology update
  • glossary update
  • undefined or obsolete activity reference
  • missing link
  • inconsistent artifact routing
  • framework-version skew
  • documentation debt
  • release or publication issue
  • PM Task
  • Backlog Item
  • reconciliation note
  • maintenance requirement
  • tooling or automation need

Ask:

  • Did the current workflow adequately route the material?
  • Does a newer artifact type remain absent from an older activity?
  • Does the page refer to something that does not exist or is not linked?
  • Did the analysis depend on undocumented practice?
  • Is the issue local to one page or systemic across the workflow?
  • Should the problem be corrected now or tasked for later?

Output may include:

  • workflow-page update
  • methodology or protocol update
  • glossary update
  • reconciliation note
  • PM Task or Backlog Item
  • governance decision
  • maintenance task
  • no Governance / Operations artifact required

Harvest Procedure

Step 1 — Review the completed output

Read the completed source work as a whole.

Do not harvest from isolated phrases without understanding the argument, evidence, boundaries, and unresolved questions.

Step 2 — Identify reusable value

Mark findings that may remain useful after the immediate event or publication is no longer current.

Distinguish:

  • reusable structure
  • one-time event detail
  • evidence supporting an existing artifact
  • a possible new concept
  • a boundary or counterexample
  • an operational issue
  • a future task

Step 3 — Run the Framework Prior-Art Check

Before naming or creating anything new:

  • search existing terminology
  • consult relevant artifact pages
  • check the Glossary
  • check Advanced Vocabulary and the NS Model of Civilization when classification is involved
  • identify structural neighbors
  • determine whether the material updates something that already exists

For each candidate, state the governing catalog checked and its load status. If the required prior art was not successfully loaded, no new, merge, specialize, instance, or reject disposition may be finalized.

Do not treat lack of retrieval as proof of novelty.

Step 4 — Evaluate artifact categories

Work through the categories above.

Do not stop after finding the first plausible destination. One source may contribute to multiple artifacts at different layers.

At the same time, do not multiply artifacts simply because several categories are relevant. Some value should remain embedded or cross-linked rather than becoming a standalone page.

Step 5 — Choose the minimum sufficient disposition

For each harvested item, choose the smallest action that preserves its value:

  • update an existing artifact
  • add an instance
  • add a boundary, non-example, or counterexample
  • embed a mechanics note
  • add a cross-reference
  • create or update a Working Concept
  • create a reconciliation note
  • create a PM Task or Backlog Item
  • create a new artifact
  • take no action

Prefer updating an existing artifact over creating a parallel one.

Prefer a Working Concept over forced formal classification.

Prefer a task over premature completion when deeper diagnosis is required.

Step 6 — Record boundaries and exclusions

Where relevant, preserve:

  • what the finding does not establish
  • which portions of the source qualify
  • which portions are excluded
  • where similar cases diverge
  • whether the relationship is causal, analogical, or unresolved
  • whether the concept remains provisional

This prevents later reuse from becoming broader than the original evidence supports.

Step 7 — Create required follow-up work

When an artifact is warranted but cannot be completed immediately, create a PM Task or Backlog Item.

The task should state:

  • the source material
  • the candidate artifact or concept
  • the question to be resolved
  • relevant existing artifacts
  • required prior-art or diagnostic work
  • legitimate possible outcomes
  • any boundaries already established

Do not frame a diagnostic task as though promotion is the expected outcome.

Step 8 — Close the harvest explicitly

State what Artifact Harvest produced.

A valid closure may be:

Artifact Harvest produced the following artifact updates: …

Artifact Harvest added the following instance and boundary notes: …

Artifact Harvest produced the following PM Tasks or Backlog Items: …

Artifact Harvest identified reusable mechanics but no standalone artifact was required.

Artifact Harvest found no additional reusable system value beyond the completed source output.

The source workflow is not complete until Artifact Harvest has been executed or explicitly considered.

Output

Artifact Harvest may produce:

  • updated Civic Topology artifact
  • Signal Translation artifact
  • Structural Dynamic update or instance
  • Systemic Failure Mode artifact or instance
  • Event Overlay
  • embedded Drift, Load, or Saecular Mechanics note
  • First Foundation artifact or candidate
  • Strategic Intervention candidate or artifact
  • Contextual Lens
  • Working Concept creation, update, instance, boundary note, counterexample, or reconciliation note
  • project or program update
  • governance or operational update
  • workflow-page update
  • methodology or protocol update
  • glossary update
  • cross-reference
  • reconciliation note
  • PM Task
  • Backlog Item
  • explicit no-artifact closure

Multiple outputs are permitted when they represent genuinely different layers of value.

Constraints

  • Do not create artifacts merely because the source is important, emotionally compelling, or politically significant.
  • Do not create a new concept before checking prior use, neighboring artifacts, and existing terminology.
  • Do not treat repeated wording or similar outcomes as proof of a unified mechanism.
  • Do not promote a Working Concept merely because several examples have accumulated.
  • Do not force a Working Concept into a formal artifact type while its classification remains genuinely open.
  • Do not allow a new case to overwrite an existing term’s earlier meaning without reconciliation.
  • Do not create a standalone artifact when an update, instance, embedded note, or cross-reference is sufficient.
  • Do not treat analogy as mechanism.
  • Do not infer intent when the evidence supports only structure, sequence, or effect.
  • Do not turn every identified problem into a Strategic Intervention or FF Pattern.
  • Do not create a Pattern before the design structure and response conditions are sufficiently developed.
  • Do not treat a PM Task as evidence that the proposed artifact has already been validated.
  • Do not erase uncertainty in order to complete the harvest.
  • Do not allow the freshest case to dominate a cross-case concept review.
  • Do not let Artifact Harvest expand into a full diagnosis when a separate NS Diagnostic Process pass is required.

Failure Mode This Prevents

Without Artifact Harvest:

  • useful findings remain trapped inside individual reports
  • recurring Structural Dynamics go unnamed
  • Systemic Failure Modes remain disconnected from evidence
  • topology relationships are rediscovered repeatedly
  • embedded mechanics are lost
  • First Foundation implications are missed
  • contextual insights remain isolated
  • project work fails to receive reusable findings
  • follow-up work depends on memory
  • framework growth becomes dependent on whoever remembers the original analysis
  • completed publications appear finished while their system value remains uncaptured
  • useful provisional concepts are lost
  • existing terms are unknowingly reinvented
  • Working Concepts accumulate without review or are promoted prematurely
  • later framework additions remain invisible to older workflows

Completion Criteria

Artifact Harvest is complete when:

  • the source output has been reviewed for reusable system value
  • relevant artifact categories have been considered
  • prior art has been checked before creating or materially redefining concepts
  • existing artifacts have been preferred where appropriate
  • Working Concept implications have been evaluated
  • boundaries, exclusions, and counterexamples have been preserved
  • required artifacts, notes, cross-references, or tasks have been created
  • deferred diagnostic work has been explicitly tasked
  • the harvest has been closed with a clear disposition

Next Activity

If artifacts are required:

→ Civic Topology Update
→ Strategic Intervention Drafting
→ Signal Translation Creation
→ First Foundation Development
→ Working Concept creation or update
→ Framework Prior-Art Scan or concept reconciliation
→ Article Development
→ Workflow Reconciliation
→ Other relevant activity

If deeper diagnosis is required before classification:

→ Separate NS Diagnostic Process pass

If follow-up work is needed but not immediate:

→ Create PM Task or Backlog Item

If none:

→ Close workflow

Related Pages