Skip to content

Web Architecture

Goals of the Web Architecture

This document provides the canonical rules for:

  • Site hierarchy (Fields, Tools, Systems, Content)
  • URL and slug conventions (mandatory)
  • Redirect policies
  • Navigation structure
  • Page templates
  • Visual identity (Field colors, shapes, icons)
  • Discoverability requirements for Systems (CT Monitor, Crisis-Phase Tracker, etc.)
  • Consistency across all future pages

This avoids drift, confusion, and inconsistent site structure as NS grows.

Audience Routing

NeuroSaeculum is intended to serve multiple audience roles, each engaging with the framework for a different purpose. Rather than organizing the website around separate audience-specific sections, the site is organized around the framework itself while remaining navigable by audience.

The engagement roles are defined in the Audience Model. This document focuses on how the website routes those audiences to the information most appropriate for their goals.

Routing Strategy

The website should provide clear entry points and progression paths for each audience role.

Audience RolePrimary Website Objective
DriversQuickly understand the framework and why it matters.
MechanicsInspect the framework’s architecture, methodology, and internal structure.
ObserversEvaluate NeuroSaeculum through its application to real-world events.
AmplifiersFind concise, shareable explanations suitable for introducing others to the framework.
PractitionersLocate operational guidance, tools, and methods for applying NeuroSaeculum.

Navigation Principles

The website should:

  • Provide an accessible entry point for every audience role.
  • Allow readers to move naturally from introductory material to deeper technical content.
  • Make supporting evidence and real-world applications easy to discover.
  • Cross-link related concepts so readers can deepen their understanding without becoming lost.
  • Minimize dead ends by providing logical “next steps” from every major page.

Related Documents

This document applies the Audience Model to the organization and navigation of the NeuroSaeculum website.

For the definition of each audience role, see:
– Audience Model

For communication principles associated with each audience role, see:
– Editorial & Design Guide

Site Hierarchy (Top-Level Model)

NeuroSaeculum.org is organized into six layers:

  1. Global Layer
    • Home
    • About / Welcome
    • Global menu & search
    • Indices (Fields, Systems, Articles)
  2. Field Layer
    The main domains of NS:
    • Hidden Circuitry
    • First Foundation
    • Cortex
    • Civic Topology
    • CivMMI
  3. Tool Layer
    Methods used within/across Fields:
    • CTM
    • CT Monitor
    • Narrative Vectors
    • Scenario Engine (future)
  4. System Layer
    Long-arc structures:
    • Crisis-Phase Tracker
    • Institutional Pattern Library
    • LCR Log
    • Renewal Framework
  5. Content Layer
    • Articles
    • Patterns
    • Logs
    • Case studies
    • Reference pages
  6. Internal Layer
    • This Web Architecture
    • Editorial & Design Guide
    • Style rules
    • Document templates

This hierarchy is fixed for NS Web Architecture v1.0.

URLs Are Identity, Categories Are Relationships

NeuroSaeculum uses URL structure to encode primary identity, not usage or association.

A page’s URL answers the question:

“What is this thing?”

Categories, links, and indexes answer different questions:

“Where is it used?”
“What does it relate to?”
“Which systems consume it?”

For example, the CT Monitor is a Tool, even though it is operated within Cortex and referenced by other Fields. Its canonical URL therefore lives under /tool/, not under /cortex/.

Correct:   /tool/ct-monitor/
Incorrect: /cortex/ct-monitor/

Placing a page under a Field or System implies ownership and exclusivity. In a modular, many-to-many architecture like NeuroSaeculum, this quickly becomes misleading and difficult to unwind.

As a rule:

  • URLs encode what something is (Field, Tool, System, Internal)
  • Categories encode what it touches (Cortex, Crisis Turning, Civic Topology, etc.)
  • Links and prose explain how it is used

Categories should never be required to understand what a page is, and URL structure should never be used to imply secondary relationships.

This separation allows NeuroSaeculum to scale without forcing pages into false hierarchies or duplicating content across domains.

URL & Slug Rules (Mandatory)

All pages and posts must follow these patterns going forward.
When updating old slugs, always add 301 redirects.

Global

  • Home: /
  • About: /about/ or /welcome/
  • NS Architecture (discipline): /architecture/
  • Web Architecture (this document): /internal/web-architecture/
  • Editorial & Design Guide: /internal/editorial-design-guide/
  • Fields index: /fields/
  • Systems index: /systems/
  • Articles index: /articles/

Fields

Each Field uses:

/field/<field-slug>/

Examples:

  • /field/hidden-circuitry/
  • /field/first-foundation/
  • /field/cortex/

This is the canonical location for all Field-level content.

Tools

Tools live in a shared namespace:

/tool/<tool-slug>/

Examples:

  • /tool/ctm/
  • /tool/ct-monitor/
  • /tool/narrative-vectors/

Systems

System pages:

/system/<system-slug>/

Examples:

  • /system/crisis-phase-tracker/
  • /system/pattern-library/
  • /system/lcr-log/
  • /system/renewal-framework/

System Subpages

Logs:

/system/<system>/logs/
/system/<system>/logs/<yyyy-mm-dd>/

Patterns:

/system/pattern-library/patterns/
/system/pattern-library/pattern/<pattern-slug>/

Articles

Pattern:

/articles/<category>/<slug>/

Categories (Field-aligned):

  • hidden-circuitry
  • first-foundation
  • cortex
  • civic-topology
  • civmmi
  • narrative-vectors
  • ns-method

Always categorize new articles under the closest-fitting Field or role.

301 Redirects (Required)

When slugs are changed:

  1. Create a 301 redirect from the old URL to the new one.
  2. Test the redirect manually.
  3. Update internal links if necessary.

Use the Redirection plugin or equivalent.

Navigation Structure

Main Menu (Global)

  • Home
  • Fields
  • Systems
  • Articles
  • About

Submenus:

Fields →

  • Hidden Circuitry
  • First Foundation
  • Cortex
  • Civic Topology
  • CivMMI

Systems →

  • Crisis-Phase Tracker
  • Pattern Library
  • LCR Log
  • Renewal Framework

Articles →

  • By Field
  • Narrative Vectors
  • Latest

About →

  • Welcome
  • NS Architecture
  • Contact (optional)
  • Internal links NOT shown here

Internal Menu (hidden from public)

  • Editorial & Design Guide
  • Web Architecture
  • Internal tools/templates (future)

Required Page Templates

The following templates must be used for consistent layout.

Field Page Template

  • Title + tagline
  • Short description
  • “Start Here” essays
  • Tools belonging to this Field
  • Systems relevant to this Field
  • Recent articles
  • Optional glossary

Tool Page Template

  • What the Tool is
  • What it is used for
  • Link to main spec
  • Templates/forms
  • Example applications
  • Related Systems

System Page Template

  • System purpose
  • How to read it
  • Log/Pattern index cards
  • Recent entries
  • Related Tools/Fields

Article Template

  • Title
  • Metadata (Field, System, Content Role, Domain)
  • Body
  • Related links (Field, Systems, next article)

Log Entry Template

  • Date
  • Summary sentence
  • Domains affected
  • Severity / trajectory
  • Narrative commentary
  • Related articles/patterns

Discoverability Rules (Critical)

NeuroSaeculum has “active systems” that must be easy to find from anywhere.

Global “Active Systems” Block (Required)

Appears on:

  • Home page
  • All Field pages
  • All System pages
  • Optionally article sidebars

Contains links to:

  • CT Monitor Logs
  • Crisis-Phase Tracker
  • Pattern Library
  • LCR Log
  • Renewal Overview

CT Monitor Logs Must Have:

  • Short explainer at top
  • Consistent card layout
  • Filter/sort options if possible
  • Direct link from CT Monitor Tool page
  • Direct link from Crisis-Phase Tracker page
  • Automatic “Related System” link from articles that reference monitoring

Crisis-Phase Tracker Must Have:

  • Clear “How to Read This” link
  • Structured logs index
  • Consistent log entry cards

Pattern Library Must Have:

  • Pattern index organized by category
  • Individual pattern pages under correct slugs

Visual Identity Rules (Internal Summary)

Field Colors (Functional Associations)

  • Hidden Circuitry → cyan/teal
  • First Foundation → slate/stone gray
  • Cortex → deep indigo/blue
  • Civic Topology → warm red
  • CivMMI → olive/green
  • Renewal → amber/gold

Use these colors for:

  • Field page headers
  • Tags
  • Icons
  • Accent bars

Shape Language

  • Organic, curved shapes
  • Interlocking “cell-like” segments
  • Nothing mechanical or harsh
  • Subtle nods to nervous-system structure

Logo Specification (Internal Summary)

Final logo should be based on:

  • A circle of 4–6 interlocking organic segments
  • Soft edges (not square puzzle pieces)
  • Thin negative-space “pathways” between segments
  • Segments reflect Field colors
  • Represents integration, cycles, and systemic coherence

Tagging Rules

Every piece of content must include:

  • Field tag (at least one)
  • Content Role (article, log, pattern, method, reference, narrative vector, etc.)
  • System tag if applicable
  • Domain tags (economy, governance, culture, etc.) where relevant

This powers:

  • Field pages
  • System indices
  • Related-content blocks
  • The Crisis-Phase Tracker
  • CT Monitor Logs

Future-Proofing Rules

Adding New Fields

  • Must get a unique Field slug
  • Must get an accent color
  • Must get an icon
  • Must have a Field landing page
  • Add to /fields/ index and nav menu

Adding New Tools

  • Use /tool/<slug>/
  • Add to Tool lists on relevant Field pages
  • Add correct icons and tags

Adding New Systems

  • Use /system/<slug>/
  • Must integrate into “Active Systems” block
  • Must have log/pattern templates if needed

Versioning

This document is:
NS Web Architecture v1.0 — Internal Edition

Changes to:

  • URL structure
  • Navigation hierarchy
  • Visual identity foundations
  • Page template types
  • Field/Tool/System definitions

…will trigger v1.1 or later.

Minor additions (e.g., new Tools/Systems within existing structure) do not change the version.

Editor Checklist (Practical)

Before publishing a new page, always check:

  • Does the slug follow the rules?
  • Does it need a redirect from an older slug?
  • Have Field/System/Content Role/Domain tags been applied?
  • Is the layout using the correct template?
  • Are related Field/Tool/System links included?
  • Does the page appear where users expect it (Field, System, Articles)?