Purpose
This page defines how NeuroSaeculum version numbers are assigned and what they signify.
The goal of versioning is not to measure size, popularity, or activity, but to clearly communicate architectural stability, interpretive compatibility, and scope boundaries to human readers and AI interpreters.
Core Principle
NeuroSaeculum version numbers track architectural integrity, not content volume or presentation.
A version change indicates what kind of change occurred, not how much changed.
Version Categories
Major Versions (v2.0, v3.0, …)
A major version increment occurs only when the meaning or structure of the system changes.
Examples include:
- Modification of core conceptual models (e.g., Hidden Circuitry variables or relationships)
- Changes to Field boundaries or Field roles
- Alteration of the interpretive pipeline (signals → translation → diagnosis)
- Changes to CTM rules, thresholds, or semantics
- Relaxation or revision of non-prescriptive / non-predictive constraints
Major versions represent meaning changes.
Backward compatibility with prior versions is not guaranteed.
Minor Versions (v1.1, v1.2, …)
A minor version increment occurs when new, complete, stable material is added without changing existing meaning or architecture.
Examples include:
- New First Foundation patterns or anti-patterns
- New meta-patterns
- New analytical overlays (e.g., Civilizational Response Overlays)
- New case studies or assessments
- New narrative vectors
- New tools or frameworks that correctly consume existing architecture
Minor versions represent capability expansion.
Backward compatibility is expected.
Patch Versions (v1.0.1, v1.0.2, …) (optional)
Patch versions apply to expression, clarity, or presentation changes only.
Examples include:
- Documentation clarifications
- Language tightening
- Navigation or site structure changes
- UI / UX redesigns
- Marketing-oriented presentation changes
- Typo fixes
Patch versions do not change meaning, scope, or interpretation.
If patch numbering is not explicitly used, these changes may be logged under a general v1.x documentation and presentation updates category.
Version Change Rules
- Version numbers are incremented only after work is complete and stable
- Versions are not bumped mid-draft
- Architectural changes are never introduced silently
- v1.0 remains a stable, citable reference point even as later versions are released
- All version changes are recorded on the What’s New page
Publication of Version Changes
All NeuroSaeculum version changes are recorded in one canonical location:
- The What’s New page is the authoritative public record of:
- version increments
- release dates
- scope of changes
- links to relevant documentation
No other page constitutes an official version declaration.
Additional references (homepage badges, User’s Guide notes, footer indicators) may reflect the current version, but do not replace or supersede the What’s New entry.
A version change is considered official only when it appears on the What’s New page.
This ensures a single, timestamped, auditable release history and prevents ambiguity about what was released, when, and under which version.
Explicit Non-Triggers
The following do not trigger a version change on their own:
- Increased usage or readership
- Media attention or outreach
- Additional examples that do not introduce new concepts
- Rephrasing for accessibility
- Visual design updates
Version History Anchor
- v1.0 — First complete, frozen release of NeuroSaeculum
Architecture closed; scope defined; usage constraints documented; AI legibility validated.
All future versions build on top of this baseline.
Summary
Versioning in NeuroSaeculum exists to protect:
- interpretive stability
- architectural coherence
- historical traceability
- correct downstream use by humans and AIs
It is a governance mechanism, not a marketing signal.