Skip to content

Methodology & Protocols

I. Purpose

The Methodology & Protocols section collects the operational rules, diagnostic procedures, evidence standards, translation methods, review processes, and support tools that define how NeuroSaeculum is practiced.

These materials help ensure that NS analysis remains consistent, reproducible, evidence-disciplined, and usable across fields, tools, workflows, and review contexts.

Methodologies describe how NS performs analysis. Protocols define repeatable procedures. Evidence standards define how claims are supported. Methodology support tools help analysts detect, classify, evaluate, route, or process material more consistently.

Patterns describe recurring structures in the world; methodology tools describe how NS looks for them.

II. Core Methodologies and Protocols

Core methodologies and protocols define major recurring NS analytical practices.

They include diagnostic methods, translation methods, evidence standards, review methods, and field-specific workflows used across the framework.

Examples include:

– Crisis Sub-Phases
– Cortex Translation Methodology
– Structural Diagnostic Triage
– Civic Topology Methodology
– CivMMI Methodology and Evidence Standards
– First Foundation Assessment Methodology
– NS News Methodology
– Unified Multi-AI Review Protocol
– Civilizational Renewal Engineering, future / emerging

This section should not be read as a closed list. The document list below is category-driven and may include newer methodology pages as they are added.

III. Governance Standards

Governance Standards define the rules by which NeuroSaeculum artifacts are created, documented, revised, and validated. Unlike methodologies, which describe how analytical work is performed, governance standards establish the requirements that methodologies, tools, and models are expected to follow. They promote consistency, transparency, traceability, and scientific discipline across the framework.

Current Standards

  • Parameter Governance Methodology (PGM) (Provisional)
    Defines the governance, classification, documentation, provenance, revision, and evidence requirements for parameters used in NeuroSaeculum models.

Planned Standards

  • Validation Methodology (VM) (Planned)
    Defines the standards for validating model parameters and outputs against independent evidence.
  • Event Assessment Rubric (EAR) (Planned)
    Defines the standardized translation of observed events into model inputs, minimizing analyst variability while preserving reproducibility.

IV. Methodology Support Tools

Methodology Support Tools are reusable analytical aids that help NeuroSaeculum detect, classify, evaluate, route, or process material across one or more workflows.

They do not directly describe recurring structures in the world. They help NS examine the world more consistently.

A methodology rule tells NS what must or must not be done.
A methodology support tool helps NS do the work more consistently.

Support tool types may include:

Detection Aids

Detection aids help identify structures, pressures, or signals that are difficult to see directly.

Example: Informal Constraint Scan Catalog.

Classification Lenses

Classification lenses help sort observed material into analytically useful categories.

Example: Technical / Adaptive Sorting.

Evaluation Frameworks

Evaluation frameworks help assess confidence, strength, maturity, evidence quality, risk, or readiness.

Example: Evidence Confidence Tiers.

Workflow Checklists

Workflow checklists help execute recurring processes consistently.

Example: Artifact Harvest Checklist.

Routing Aids

Routing aids help determine where a finding, source, article, pattern, issue, or concept belongs within NS.

Example: CivTop-rich vs. framework-origin-rich source distinction.

V. Cross-Cutting Protocols

Cross-cutting protocols are procedures used across multiple NS fields, tools, or workflows.

Unified Multi-AI Review Protocol

Defines how structured multi-AI reviews are conducted, including review rounds, constraints, convergence, dissent, synthesis, and preservation of disagreement.

Review Moderator’s Rules

Defines moderator behavior for structured reviews, including how to prevent premature convergence, preserve dissent, enforce constraints, and maintain methodological discipline.

Ideation Workflow Rules

Defines how exploratory ideas are generated, tested, constrained, parked, promoted, or discarded.

Update-and-Synthesis Protocols

Defines versioning, review cycles, archival rules, synthesis procedures, and update discipline.

VI. Promotion and Staging Discipline

Several NS artifact types function as staging areas. These include Working Concepts, Future Article Seeds, Future Topology Areas, Proto-Patterns, NS-Adjacent Resources, and candidate Methodology Support Tools.

Each staging area should define:

– what qualifies for entry
– what counts as maturity
– what promotes it
– where it goes next
– what causes it to be discarded or archived

Promotion criteria are not uniform across all staging areas. The structure of the question is shared, but the signals differ by artifact type.

Examples:

– A Future Article Seed matures when the audience, frame, and source material become clear enough to support a public essay.
– A Future Topology Area matures when enough issues, links, chains, feedback loops, or related cases accumulate to justify its own map.
– A Proto-Pattern matures when multiple cases support the same recurring structure and the pattern’s diagnostic value stabilizes.
– A Working Concept matures when it has recurring use, a stable definition, a clear destination, and demonstrated operational value.
– A Methodology Support Tool matures when it works across multiple workflows and improves detection, classification, evaluation, routing, or analysis.
– An NS-Adjacent Resource matures when repeated engagement shows that the source reliably produces NS-relevant concepts, evidence, cases, framing, or structural prompts.

This is a shared governance structure, not a single uniform promotion test. Each staging type should eventually define its own specific promotion signals.

VII. Receptacle-Induced Detection

NS development has repeatedly shown that artifact architecture is not passive storage. Creating a stable receptacle can change what the system is able to notice.

Once a recurring class of insight has a reliable landing place, related examples become easier to recognize, classify, preserve, and route.

Operational rule:

When a recurring class of insight is repeatedly lost, misrouted, or rediscovered, consider creating a stable artifact receptacle if the loss or misrouting cost exceeds the maintenance and navigation cost of adding the receptacle.

This principle applies to artifact types such as Future Topology Areas, Future Article Seeds, Working Concepts, Topology Clusters, NS-Adjacent Resources, Proto-Patterns, and Methodology Support Tools.

Informally:

Once the shelf exists, you start recognizing what belongs on it.

VIII. Document List

The documents below are populated from the WordPress `methodology-protocols` category.

This list may include core methodologies, protocols, evidence standards, review processes, methodology support tools, and related methodology documents. Items are added by assigning the appropriate WordPress category to the individual document page.

VIX. Versioning Policy

Unless otherwise specified, NS methodology and protocol documents use the following versioning convention:

– v0.x = exploratory, provisional, or in development
– v1.x = public-ready or internally stable
– v2.x = revised after extended use, review, or external adoption

Version changes should reflect substantive methodological changes, not minor wording edits.

X. Future Additions

Future additions may include:

– CRE protocols
– Cortex architecture
– Methodological templates
– Technical / Adaptive Sorting
– Evidence Confidence Tiers
– Methodology Support Tools Index
– Working Concepts Promotion Criteria
– Automation notes for NS ThinkTank webapp