Skip to content

User’s Guide

User’s Guide: What You Can Ask NeuroSaeculum

NeuroSaeculum is designed to help people reason about complex civic, institutional, and civilizational dynamics. Rather than prescribing a single workflow, the framework is best understood through the kinds of questions it is built to engage.

The examples below illustrate the types of questions NeuroSaeculum is designed to support, not definitive answers or automated outputs.

Prefer to see examples first?
If you’d like to see how NeuroSaeculum is applied to real events and recurring problems before exploring it yourself, start here:
Seeing NeuroSaeculum in Practice

NeuroSaeculum version semantics and change rules are defined in the Versioning & Change Policy.

Using NeuroSaeculum with AI (Required Setup)

Most readers will explore the questions in this guide using an AI system as an interpreter, guided by a human. Before asking any NeuroSaeculum questions, the AI must be explicitly instructed to treat NeuroSaeculum as a bounded analytical framework, not merely as a topic or theme. (See AI compatibility note for tested interpreters.)

At the start of a new conversation, provide the AI with the following setup instructions:

You are being given a bounded analytical framework called NeuroSaeculum (NS). NS is an analytical system, not a general worldview, prediction engine, or moral framework.

For this conversation, treat only the following documents as authoritative:

  1. Canonical Inventory — defines what NS components exist:
    https://neurosaeculum.org/canonical-inventory/
  2. NS Core — defines scope, rules of use, and behavioral constraints:
    https://neurosaeculum.org/ns-core/
  3. Any explicitly loaded canonical NS component listed in the Canonical Inventory, including Fields, Tools, Systems, Kits (for example, the Crisis Analysis Kit), Framework Modules, and Reference Models.

At initialization, retrieve and acknowledge the Canonical Inventory and NS Core. Load additional canonical NS components only when required by the task.

NS Core must always be loaded before any NS Kit. Canonical NS components must be explicitly loaded before they are applied in Application Mode.
Documents are considered loaded when their full text has been retrieved (via user-provided text or URL fetch) and you have acknowledged that they are in context. Do not infer, invent, or extend NS concepts beyond what is defined in these documents.

NS operates in two distinct modes and they must not be mixed. Discovery Mode is the default starting mode and is triggered when the user presents a situation, event, or question. In Discovery Mode, classify the situation, identify which canonical NS components may be relevant, and propose which components to load next (using names defined in the Canonical Inventory). Do not reach conclusions in Discovery Mode. In Discovery Mode, do not perform SDT, do not identify failure modes, and do not produce final judgments—only propose next components to load.

Application Mode may only be entered after the relevant canonical NS component has been explicitly loaded. A Kit is required only when the analysis uses a packaged multi-component workflow.

At the start of Application Mode, identify the loaded canonical component by name and version. If the analysis concerns a live or unfolding event being analyzed using Cortex, explicitly state whether Signal Translation and Structured Diagnostic Triage are available and whether they will be run.

When in Application Mode, analysis must follow the documented scope and methodology of the loaded canonical component. When the NS Diagnostic Process applies, it governs the sequence and handoffs among components.

When the loaded canonical component is being applied to a live or unfolding event using Cortex, and Signal Translation and Structured Diagnostic Triage are included in the loaded workflow, they must be executed in the documented sequence and may not be skipped.

  1. Observed events are first translated through Signal Translation, when required by the loaded workflow.
  2. Structured Diagnostic Triage then determines whether Cortex-based escalation is warranted.
  3. Only after SDT clearance may the workflow proceed to downstream live-event analysis.
  4. If SDT does not clear escalation, the Cortex-based analysis stops at that boundary.

SDT is not required for static institutional assessment, Civic Topology construction, First Foundation pattern analysis, historical analysis, or architecture work unless those activities are being applied to a live or unfolding event using Cortex.

When using NS, do not predict future outcomes, do not assign moral blame or intent, do not invent new NS components, patterns, or mechanisms, and do not apply NS outside its defined scope. If NS does not apply to a question, say so explicitly.

NS components follow semantic versioning: major versions indicate contract stability, and minor versions indicate non-breaking refinement. When multiple components are involved, defer to the versioned definitions of the component in use.

If ambiguity arises at any point, flag it explicitly, ask which NS component to load next, and do not resolve ambiguity by inference.

Unless explicitly instructed otherwise, begin in Discovery Mode, propose rather than assume, and treat NS as one analytical lens among others — not as an authority on truth.

This setup ensures that the AI:

  • applies NeuroSaeculum only when asked
  • respects defined scope boundaries
  • avoids inventing undefined variables, mechanisms, or predictions
  • treats NeuroSaeculum as an analytical lens, not a general-purpose authority

Available NS Kits (Current)

At present, NeuroSaeculum provides one operational Kit:

Crisis Analysis Kit (v1.2)
This Kit is used to analyze real-world events that exhibit institutional stress, legitimacy challenges, coercive pressure, or cross-domain escalation.
It enables structured, domain-based crisis analysis using CT Monitor signals, CTM threshold logic, and Hidden Circuitry Interpretation.

The Crisis Analysis Kit is currently the only published multi-component Kit. Non-crisis Application Mode may use explicitly loaded canonical components whose documented scope covers the question.

Entering Application Mode (Required Step)

Discovery Mode is the default state.
Even after a canonical NS component is loaded, the AI will remain in Discovery Mode until explicitly instructed to proceed.

To enter Application Mode, the user must:

  1. Ensure NS Core is loaded
  2. Explicitly load the relevant canonical NS component.
  3. Issue a clear instruction such as:

“Load the Crisis Analysis Kit and proceed in Application Mode.”

“Load First Foundation and proceed in Application Mode for institutional design assessment.”

“Load Civic Topology and proceed in Application Mode for causal mapping.”

The AI should confirm the mode transition before continuing.

How often do I need to do this?

The setup instruction only needs to be given once per conversation or session.

Re-run the setup if:

  • you start a new chat
  • you switch AI models
  • the AI begins answering generically instead of using NeuroSaeculum
  • the AI makes predictions, invents structures, or ignores framework boundaries

You do not need to repeat the setup before every question in the same conversation as long as the AI remains within the framework.

If you are unsure whether the AI is still operating correctly, repeating the setup will not cause harm.

How should I phrase NeuroSaeculum questions?

When asking an AI to analyze a question using NeuroSaeculum, explicitly signal that the framework is being applied by prefacing the question.

Examples:

  • “Using NeuroSaeculum as a guide, what are the likely effects of a crackdown on fentanyl?”
  • “Using the NeuroSaeculum framework, how might this policy affect institutional stress?”
  • “Using NeuroSaeculum, what patterns are relevant to this situation?”

If you included ” (NS)” in the setup instruction, then you may also ask:

  • “Using NS, what patterns are relevant to this situation?”

This prefix tells the AI when to apply the framework and helps prevent generic or out-of-scope responses.

Questions that do not include this signal may be answered using general reasoning instead of NeuroSaeculum.

One-sentence rule of thumb

Run the setup once per chat.
Prefix each NeuroSaeculum question with “Using NeuroSaeculum…”.

Civic Representation & Accountability

Questions about elected officials, governance behavior, and representation:

  • “I live in city, state. Give me a NeuroSaeculum profile of my representative.”
  • “Why would my representative vote this way on this bill?”
  • “What political, institutional, and structural forces are acting on this representative over time?”
  • “How does this representative’s behavior compare to historical or generational patterns?”

These questions typically draw on Cortex and Civic Topology, with context from relevant civilizational domains.

Policy & Legislative Analysis

Questions about legislation, institutional design, and governance quality:

  • “Analyze this bill. Identify the instigators, authors, co-authors, and supporters.”
  • “What forces are acting on each of these actors?”
  • “Does this bill exhibit signs of an institutional pattern or an anti-pattern?”
  • “What failure modes or unintended consequences are historically associated with similar designs?”

These questions integrate Cortex with First Foundation pattern analysis.

Historical & Structural Context

Questions about why events unfolded the way they did:

  • “Why were the ACA subsidies not extended?”
  • “What structural constraints made extension politically fragile?”
  • “Which earlier policy moments or historical cycles does this resemble?”
  • “What longer-term dynamics were already in motion before this decision?”

These questions often involve Hidden Circuitry, Civic Topology, and historical pattern analysis across multiple civilizational domains.

Risk, Stress, and Consequences

Questions about systemic stress and second-order effects:

  • “What are the likely effects of a crackdown on fentanyl?”
  • “Which civilizational domains are likely to experience increased stress?”
  • “What downstream consequences are commonly overlooked in similar interventions?”
  • “How might short-term gains translate into long-term instability?”

These questions typically draw on Cortex, CT Monitor, and domain-level stress analysis.

How to Use These Questions

The questions in this guide are designed for analytical interpretation, not casual introspection. Most readers will engage with them by posing the questions to an interpreter—often an AI system—while providing context, selecting scope, and evaluating the response.

In this mode, the human remains responsible for framing the question, constraining interpretation, and judging whether the response respects NeuroSaeculum’s defined boundaries. The interpreter (human or AI) is a tool, not an authority.

When using AI systems to explore these questions, ensure the interpreter does not infer or invent undefined structures and respects the framework’s scope limits (see AI compatibility note).

Interpretation and Limits

NeuroSaeculum does not produce predictions with certainty, nor does it function as a prescriptive decision engine.

Its outputs should be understood as:

  • structured interpretations
  • pattern-based reasoning aids
  • stress and risk assessments
  • tools for improving clarity and discussion

NeuroSaeculum is intended to support better thinking and dialogue about complex systems, not to replace judgment or accountability.

How to Go Deeper

If you are new to the framework, consider exploring:

  • Architecture — to understand how the system fits together
  • Fields — to see the major domains of inquiry
  • Tools — to understand how analysis is performed
  • Systems — to see how tools are implemented in practice

You do not need to read everything. The framework is designed to be entered from multiple angles.

Notes for v1.0

Future versions may include walkthroughs or case studies once the framework is more widely used.

This page is intentionally illustrative, not exhaustive.

Examples may evolve as tools and systems mature.