How We Define v1.0, v1.x, and Future Versions
Purpose of This Page
NeuroSaeculum is a multi-layer architecture with many subsystems (Hidden Circuitry, First Foundation, Cortex, CTM, Civic Topology, CivMMI, etc.).
To ensure clarity across all chats, AIs, and collaborators, this page defines the official versioning standard for the project.
This is the link everyone can use whenever a new subsystem or document needs a version check.
What “v1.0” Means in NeuroSaeculum
v1.0 represents the first canonical, public-ready release of a subsystem or field.
It is not an MVP, not a draft, and not a prototype.
It is Opening Night.
A subsystem is considered v1.0 when it meets all the following criteria:
1. Architecture Complete
All major parts of the subsystem exist, are defined, and connect together.
No missing sections. No “TODO” placeholders. No ambiguous edges.
2. Language & Definitions Stable
Key terms, concepts, and structures are locked.
Minor edits can still happen later, but the conceptual vocabulary is no longer shifting.
3. Core Documentation Fully Written
The subsystem has:
- an overview
- definitions
- examples or usage guidance
- internal navigation
- crosslinks to related subsystems
The material stands alone without needing off-chat explanations.
4. Dependencies Finalized
The subsystem is properly integrated with all other NS components that depend on it.
(Example: CTM must align with Cortex and CT Monitor; FF must align with CivMMI.)
This doesn’t require perfection — it requires coherence.
5. No Major Conceptual Holes
You shouldn’t encounter sections where something “ought to exist” but doesn’t.
All core questions have answers.
All major design decisions are made.
6. Usable for Real Analysis
The subsystem must be ready for:
- answering public questions
- writing articles
- diagnosing institutions
- running Crisis-phase evaluations
- using the site as an external knowledge source
If someone points an AI at the site, the subsystem must “hold up.”
7. Future Revisions Are Additive, Not Structural
After v1.0, revisions must not break the architecture.
Changes should:
- add new capabilities
- refine clarity
- update examples
- expand mapping
but should not require rethinking the core model.
What v1.0 Is Not
- Not a rough draft
- Not an MVP
- Not “good enough for now”
- Not a speculative idea waiting for structure
- Not a placeholder awaiting future thinking
v1.0 means this subsystem could be published in a book tomorrow and stand on its own.
After v1.0: How We Version Updates
“The versioning rules described here apply both to NeuroSaeculum as a whole and to each individual subsystem (fields, tools, systems, modules, models). Each component follows the same v1.0 → v1.x → v2.0 lifecycle.”
v1.1
Small improvements, clarifications, minor additions.
Does not change the core architecture.
v1.2
Moderate extensions or refinement that improve capability but retain full backward compatibility.
v1.3+
Larger conceptual extensions — but still built on top of the v1.0 structure.
v2.0
A paradigm shift or major architectural overhaul.
Very rare.
Reserved for foundational discoveries that change how the subsystem works at its core.
Version Categories for Pre-v1.0 Development (v0.x)
Before a subsystem reaches v1.0 (“Opening Night”), it progresses through the v0.x series, which represents exploratory development.
These versions are not canonical and may undergo major conceptual changes.
v0.x versions are used when:
- A new subsystem or conceptual layer is being invented
- Architectural boundaries are still shifting
- Terminology is not yet finalized
- Core mechanisms are still being tested
- Major critique or collaboration (e.g., multi-AI review) is expected
- The subsystem is not yet ready to be referenced externally
Important:
Nothing in v0.x should be relied on by downstream subsystems without an explicit stability warning.
Once the subsystem becomes structurally coherent and survives at least one critique cycle (internal or external), it becomes eligible for v1.0.
System-Level vs Subsystem-Level Versioning
NeuroSaeculum contains many subsystems (HC, FF, CT, CivMMI, Cortex, Motivational Stack, etc.).
Each subsystem has its own version number (v1.0, v1.1…), but the overall system version (e.g., NS v1.0) advances only when:
- All canonical subsystems reach v1.x
- Cross-subsystem integration is stable
- No unresolved contradictions remain
- Internal navigation and crosslinks are consistent
- The system is ready for external readership or AI ingestion
System-level versions signify “entire-framework readiness,” not individual module maturity.
Refinement Line vs Architectural Line
After v1.0:
- v1.x represents refinement, not redesign.
- Better clarity
- More examples
- Stronger citations
- Improved diagrams
- Expanded mapping
- Internal consistency polish
- v2.0 represents an architectural shift, such as:
- Changing causal layers
- Adding or removing whole subsystems
- Rewriting foundational mechanisms
- Merging or splitting core entities
This distinction protects the stability of the NS framework as it expands.
Versioning Philosophy for NS
NeuroSaeculum uses a unified versioning lifecycle across all subsystems.
This page provides only the abbreviated definitions needed to interpret subsystem versions.
v0.x — Development
Early-stage, exploratory, non-canonical.
v1.0 — Canonical Baseline
Concept stabilized and publicly referenceable.
v1.x — Refinement
Improvements that do not change the underlying architecture.
v2.0 — Overhaul
A structural or causal shift that breaks v1.x assumptions.
Subsystems mature independently; the framework progresses only when cross-system integration stabilizes.
For the full versioning policy, see:
🔗 Internal Versioning Standard
https://neurosaeculum.org/internal/versioning-standard/
Why “Opening Night” Matters
v1.0 is a psychological and architectural milestone.
It means:
- The subsystem is alive.
- It is teachable.
- It can be used by others (humans or AIs).
- It will not collapse if someone asks real questions.
- It becomes part of the permanent canon of NeuroSaeculum.
This is the moment where the work stops being internal R&D and becomes a public intellectual framework.
NS v1.0 Release Goal
If someone points their favorite AI at NeuroSaeculum.org, the AI should be able to read it and begin answering questions using the same logic, language, and architecture that the NS project uses internally.
This is the true functional test of v1.0 readiness across all subsystems.
Related Pages to Link
(You can add these after your site’s internal structure stabilizes)
- NS Architecture Overview
- Field / Subsystem Index
- What Counts as a Subsystem
- Release Notes & Version History
This Page’s Permanent Role
Any time you (or any AI) need to check:
- “Is CTM ready for v1.0?”
- “What’s missing in FF before v1.0?”
- “Is this subsystem allowed to change?”
- “Does this need to be in v1.0 or v1.1?”
This page is the authoritative reference.
This page also governs how new conceptual modules (e.g., Motivational Stack, narrative models, maturation layers) progress from exploratory v0.x drafts to final v1.x readiness.