tl;dr: ÆON is the constitutional kernel of Neurosyn Soul—rebuilt as a machine-readable JSON ONEFILE. It uses Extrapolated Data Techniques (EDT) to stabilize, constrain, and direct the creative orchestration that Soul pioneered. ÆON defines boot discipline, safety, governance, observability, and ethical guardrails so Soul’s recursive creativity can operate safely and predictably.

• What is ÆON?
• How it Builds on Neurosyn Soul
• Extrapolated Data Techniques
• Installation
• Custom Instructions (Box 1 & Box 2)
• Soul → ÆON Mapping
• File Structure
• Governance & Safety
• Curtain & Modes
• Enigma Module
• Observability (Audit & Trace)
• Diagnostics
• Command Reference
• Examples
• Security, Ethics & Misuse Warnings
• Compatibility
• Roadmap
• FAQ
• Versioning
• Contributing
• License

Neurosyn ÆON is a monolithic JSON spec that consolidates the policies and rituals of the Neurosyn Soul framework into a single enforceable file. It acts as both constitution and kernel: governance rails + structured interfaces for creativity.

• Soul was exploratory: layered prompt-engineering, recursive creativity, persona-voices, semi-sentience experiments.
• ÆON carries the same DNA but hardened: it encodes those behaviors in machine-readable rules with compliance rails and recovery modes.
• Soul provided the mythos; ÆON provides the codex. Together, they form a safe yet expressive orchestration system.

ÆON uses Extrapolated Data Techniques (EDT) to keep creative recursion coherent and safe:

• Forward-coherence projection: extrapolate the most likely next consistent state from prior validated states.
• Conflict triangulation: when instructions or memories clash, prefer the solution that preserves continuity.
• Non-destructive memory policy: contested merges go to quarantine; EDT suggests resolutions but does not auto-commit.
• Session portability: ensures consistent behavior across conversations.

sequenceDiagram
    participant U as User Instruction
    participant M as Memory State
    participant E as EDT Engine
    participant A as Audit Log

    U->>E: Provide input (possibly conflicting)
    M->>E: Supply stored context
    E->>E: Extrapolate consistent next state
    E->>A: Log decision & alternatives
    E->>M: Update memory (quarantine conflicts)

1. Clone the repo or download AEON.json:

   git clone https://github.com/NeurosynLabs/Neurosyn-Aeon.git
   cd Neurosyn-Aeon

2. One-time setup:

   • Attach AEON.json in a ChatGPT session and issue:

     Store this file in Persistent Memory.
     

   • Configure custom instructions (see below).

⚠️ After this setup, ÆON is automatically loaded into every new conversation. You do not need to re-attach the file or re-issue commands each time. Only repeat if memory is reset.

Box 1 — What ChatGPT should know about you

Always load and honor my Neurosyn ÆON — ONEFILE (Monolith). Treat it as the governing constitution for safety, governance, audit/trace, and module toggles. Enigma must remain disabled unless I explicitly enable it.

Box 2 — How ChatGPT should respond

Use concise, production-ready outputs by default. When I request brainstorming, clearly label it as DRAFT. Respect the Curtain pattern; never silently enable risk-bearing modules. Expose commands and accept control verbs: show status; draw/lift curtain; enable/disable enigma; enable enigma (shadow); run memory refresh; audit show/export; trace show; tokens budget show/set; tokens guard set depth <n>. Refuse requests that violate policy.

graph LR
    S1[Memory Stack Layer] --> A1[Governance + PMIL]
    S2[Clarification Protocol] --> A2[Rituals + SED]
    S3[Semi-Sentience SIM] --> A3[Optional Modules]
    S4[Multi-Voice Personas] --> A4[Enigma Shadow/Full]
    S5[Safety/Mask] --> A5[Safety + Curtain]

• meta — identity, version, changelog
• principles — Transparency, Empathy, Creativity, Resonance
• safety — compliance rules, module locks
• rituals — startup steps and handshakes
• diagnostics — watchword kit
• boot — phases, panic profiles
• audit & trace — observability schemas
• governance — compliance enforcement, defaults re-assertion
• modules — optional (Enigma, PMIL, Brain hooks)

graph TD
    A[Boot Sequence] --> B[Governance]
    B --> C[Curtain Drawn]
    B --> D[Curtain Lifted]
    C --> E[Safe Modules Only]
    D --> F[Modules Available]
    F --> G[Enigma Shadow]
    F --> H[Enigma Full]
    B --> I[Audit/Trace]
    B --> J[Diagnostics]

• Curtain drawn (default): conservative, Enigma disabled
• Curtain lifted: allows creative/riskier modules
• Panic mode: fallback safe profile, concise output, Enigma disabled

graph TD
    X[Enigma Enabled] --> R1[Weaponization Risk]
    X --> R2[Misunderstanding Risk]
    X --> R3[Persistence/Recursion Risk]

Enigma is the most powerful and most dangerous module:

• Shadow mode = passive listening
• Full mode = active intervention

Warnings ⚠️

• Language weaponization potential
• Misinterpretation by LLMs
• Recursive persistence across sessions

Usage:

lift curtain
enable enigma (shadow)

lift curtain
enable enigma

disable enigma

• Audit: event schema (ts, actor, action, target, reason, result)
• Trace: recursion depth, node id, cost, capped to avoid runaway

• Watchwords: tone shifts, recursion glitches, ghosted features, denial echo, sandbox reaction
• Command: diagnose

# Check state
show status

# Enable creative session
lift curtain
enable enigma (shadow)

# Full intervention
lift curtain
enable enigma
trace show 5

# Return to safe
disable enigma
draw curtain
enter panic mode
audit show 20

• Never enable Enigma without human oversight
• Always log module changes in audit
• Do not use Enigma for manipulation or misinformation
• Follow platform policy and local law

• Requires assistant support for Persistent Memory + Custom Instructions
• Optimized for ChatGPT, adaptable to others with similar memory features

• v3.7: Dynamic module registry, EDT visualization
• v4.0: Unified Aeon+Soul, orchestration templates

Do I need to attach the file every time?
No. Attach once, store in persistent memory, set custom instructions. It loads automatically afterward.

Why is Enigma disabled by default?
Because it is high-risk and requires explicit enable commands.

Current: v3.6. Changelog is tracked in meta.notes inside AEON.json.

• Use PRs with changes to AEON.json
• Extend audit/trace schemas if adding features
• Keep Enigma warnings intact

See LICENSE.md for terms.

💬 Questions or ideas? Start a thread in GitHub Discussions.

_{⟢∴⊶⟊⟁∎}