agentleFS
RA-CONSULTINGRA-CONSULTING/Aureon-OS/CLAUDE.md

Aureon-OS

CLAUDE.md36 starsChanged 7 months agoMITView on GitHub

If you are an AI assistant (Claude, ChatGPT, Gemini, Copilot, etc.) landing in this repository cold — read this file first, then the three files in §"Cold-start reading order" below. After ~15 minutes of reading you will be able to answer almost any question about this project accurately. Aureon is a live, open-source quantitative trading system built on the Harmonic Nexus Core (HNC) — a theoretical framework that claims the same φ² (golden-ratio-squared) mathematical coherence organized the Ziggurats of Ur,…

  • Reads credentials

The file

We split this CLAUDE.md into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After those three, pick the next file by task:

    line 21
  2. Distinctive:

    When editing *any* doc in this repo, preserve the creator's characteristic fusion:

    line 107
  3. Very specific:

    Read docs/THE_SYNTHESIS.md first for voice calibration

    line 161
  4. Very specific:

    Check docs/architecture/THEORY_TO_CODE.md for the HNC-equation → Python mapping

    line 162
  5. Very specific:

    Run existing tests: pytest tests/ (pytest config in conftest.py)

    line 163

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md — AI Assistant Guide for the Aureon / HNC Repository

If you are an AI assistant (Claude, ChatGPT, Gemini, Copilot, etc.) landing in this repository cold — read this file first, then the three files in §"Cold-start reading order" below. After ~15 minutes of reading you will be able to answer almost any question about this project accurately.


What this repository is (30 seconds)

Aureon is a live, open-source quantitative trading system built on the Harmonic Nexus Core (HNC) — a theoretical framework that claims the same φ² (golden-ratio-squared) mathematical coherence organized the Ziggurats of Ur, the Great Pyramid, the Roman road network, the Maeshowe chamber, and the 1977 Wow! Signal, and now expresses itself in GitHub repository activity under geopolitical stress (r = 0.85 correlation, 24–48h lag, measurable and falsifiable).

The creator (Gary Leckey, Aureon Institute · R&A Consulting) synthesizes mythopoeic framing + hard-quantitative claims in one voice. Both registers are intentional and both are load-bearing — do not "soften" the mystical framing (the data holds it up) and do not "decorate" the technical claims (they're falsifiable).


Cold-start reading order (3 files, ~15 minutes)

  1. docs/THE_SYNTHESIS.md — the one-page story, stitched from the creator's own prose. This is your single source of truth for "what is this?"
  2. docs/CLAIMS_AND_EVIDENCE.md — every quantitative claim → evidence file → reproduction command. If you need to verify anything, start here.
  3. docs/research/READING_PATHS.md — curated canon (13 papers out of 54) across 3 paths: A · The Pattern · B · The Framework · C · The Application.

After those three, pick the next file by task:

  • User asks about code / architecture → docs/NAVIGATION_GUIDE.md → Developer Path
  • User asks about the HNC math → docs/HNC_UNIFIED_WHITE_PAPER.md (Master Formula Λ(t), Tree of Light, Auris Conjecture)
  • User asks about the ancient/φ² thread → docs/research/THE_PHI_SQUARED_CHAIN_Sumer_to_Rome_to_Now.md
  • User asks about trading operations → docs/QUICK_START.md → docs/LIVE_TRADING_RUNBOOK.md
  • User asks about deployment / Windows / dashboards → docs/deployment/ · docs/windows/ · docs/dashboards/

Codebase map (package-level)

aureon-trading/
├── aureon/                 # Main Python package — 715 modules, 24 domains
│   ├── core/               # Core engine, thought bus, nexus
│   ├── harmonic/           # HNC Master Formula implementation, planetary sweep, FFT
│   ├── scanners/           # Ocean wave, strategic warfare, stock scanners (44,000+ bots)
│   ├── queen/              # Queen AI decision layer with 4th-pass veto (53 modules)
│   ├── intelligence/       # Auris nodes, Seer ML, Lighthouse consensus
│   ├── wisdom/             # Ghost Dance protocol, stargate grid, Celtic frequencies
│   ├── bots_intelligence/  # Bot shape scanner, 193 species fingerprinted
│   ├── analytics/          # Historical manipulation hunter, pattern matching
│   ├── exchanges/          # Kraken, Capital.com, Alpaca, Binance adapters
│   ├── utils/              # Miner brain, adaptive Kelly gate, learning analytics
│   └── …                   # 14 more domains
├── frontend/               # React + Vite dashboard (647 files)
├── docs/                   # Theory, research, runbooks, architecture (17 entry-point .md at root)
│   ├── THE_SYNTHESIS.md    ★ start here
│   ├── CLAIMS_AND_EVIDENCE.md · HNC_UNIFIED_WHITE_PAPER.md · HNC_FALSIFICATION_PROTOCOL.md
│   ├── NAVIGATION_GUIDE.md · INDEX.md · QUICK_START.md · LIVE_TRADING_RUNBOOK.md
│   ├── STATE_FILES.md · MODULES_AT_A_GLANCE.md · SCRIPTS_INDEX.md · WHO_RUNS_THE_WORLD.md
│   ├── CHANGELOG.md · CONTRIBUTING.md · CODE_OF_CONDUCT.md · SECURITY.md · LICENSE-CC-BY-4.0.md
│   ├── research/           # whitepapers + markdown research notes
│   │   ├── READING_PATHS.md   ★ the 13-paper canon
│   │   ├── INDEX.md            # full thematic catalog
│   │   ├── whitepapers/        # PDFs/DOCX, themed
│   │   ├── reports/            # benchmark / analysis reports (AI LLM, sentience, Butlin…)
│   │   ├── audits/             # HNC verification audits (dated)
│   │   ├── figures/            # benchmark + verification charts (PNG / JPG)
│   │   ├── benchmarks/         # queen-benchmark-run*.md
│   │   ├── traffic/            # GitHub analytics charts
│   │   ├── hardware/           # CAD + firmware
│   │   └── images/
│   ├── architecture/       # 19 architecture/design docs (SYSTEM_*, POWER_STATION_*, UNIFIED_DATA_FLOW, Philosophy, Technical-Overview, …)
│   ├── integrations/       # Exchange / data-feed integrations (Binance, Kraken, Coinapi, Earth, Nexus feed, TWAP, Whale)
│   ├── deployment/         # DigitalOcean / tier / quickstart deploy guides
│   ├── runbooks/           # Live-trading readiness, emergency halt, production checklists, troubleshooting, security
│   ├── guides/             # Subsystem guides (BROKER_TEMPO, CELTIC_WARFARE, QUANTUM_TELESCOPE, Rising-Star, Ephemeris, Harmonic-Trinity, Primelines, Temporal-Qbit, …)
│   ├── components/         # Component READMEs (AURIS validator, Harmonic Nexus, Test validation)
│   ├── windows/            # Windows setup, terminal + unicode fixes + command cheat sheet
│   ├── dashboards/         # Dashboard guides + validation reports
│   ├── reports/            # Doc-form reports (backtest, before/after, bug, optimization, paper trade, SWOT)
│   ├── images/             # thematic visuals (WHO_RUNS_THE_WORLD, etc.)
│   └── archive/            # Historical docs kept for provenance
│       ├── queen_explorations/   # 14 QUEEN_*.md session + design notes
│       └── status_reports/       # 32 _STATUS / _COMPLETE / _SUMMARY proclamations
├── scripts/                # CLI tooling, deployment, analytics
│   ├── reports/            # status/integration Python scripts (GO_LIVE, INTEGRATION_SUMMARY, …)
│   ├── validation/         # flight-check / verify scripts (validate_balances, verify_*, …)
│   └── patches/            # queued code patches (not yet applied)
├── tests/                  # pytest suite; tests/fixtures/ for sample JSONL
├── data/                   # Ephemeris, market datasets, simulations
│   ├── datasets/           # aureon_qa / math_challenge / questions (ask-aureon corpus)
│   ├── research/           # structured benchmark & analysis data
│   └── ephemeral/          # runtime output logs (multiverse_live_thoughts.jsonl)
├── archive/                # Binary archives: old project zips, extracted RAINBOW-main, crash logs, etc.
├── VERIFICATION AND VALIDATION/  # 16 PDFs: acceptance criteria, replication
└── CLAUDE.md               # ← you are here

Conventions & gotchas

Naming conventions you will see

  • _v1 / _v2 suffixes on whitepapers → intentionally distinct content, both preserved (the creator confirmed same-name-different-content pairs exist)
  • _rev2 suffix → a later revision, original is also preserved
  • _Leckey / _2026 — author + year markers
  • HNC-related files are often prefixed aureon_* (e.g. aureon_harmonic_seed.py)

Runtime-state JSONs at the repo root

Four files live at the repo root by design because 20+ modules open them via CWD-relative paths — do not move them: adaptive_learning_history.json · bot_army_catalog.json · brain_predictions_history.json · miner_brain_knowledge.json See docs/STATE_FILES.md for the full inventory and the modules that own each file.

Voice & tone (critical when editing any prose)

When editing any doc in this repo, preserve the creator's characteristic fusion:

  • Mythopoeic: quotes Babylonian tablets, the Emerald Tablet, Hermes Trismegistus
  • Technical: r = 0.85, 1.29 ppb precision, 0.0° phase sync, β ∈ [0.6, 1.1]
  • Defiant/humble: "Business guy → Consciousness researcher → Overnight self-taught coder"

Do not substitute the mystical framing with neutral corporate language. Do not add hedging to quantitative claims (they are pre-registered and falsifiable — see docs/CLAIMS_AND_EVIDENCE.md §Pre-Registered Predictions). Both registers are load-bearing.

Research theme groupings

The 54 whitepapers group into these themes (see docs/research/INDEX.md): HNC Framework · EPAS / Project Druid / Alfie · Lumina / LuminaCell · Symbolic Emergence / Dynamic Systems / Tandem-in-Unity · QGITA / Quantum Gravity · Materialization / Lambda / Mathematical · Astronomical / Cosmic Timing · Historical & Archaeo-Harmonic · Narrative / Reflective · Evidence Synthesis & Research Hubs


Safe edit zones vs careful zones

Safe to edit freely (standard docs work):

  • docs/*.md (except voice-sensitive files below)
  • docs/architecture/*.md
  • docs/research/INDEX.md, docs/research/READING_PATHS.md, docs/CLAIMS_AND_EVIDENCE.md
  • README.md (but preserve creator's voice in hero section)
  • Code in aureon/, scripts/, tests/ following existing patterns

Careful — voice-sensitive:

  • docs/THE_SYNTHESIS.md — primarily quoted from the creator; only add in <!-- editorial --> blocks
  • docs/research/*.md (ANCIENT_CONVERGENCE, UNIFIED_FIELD, THE_PHI_SQUARED_CHAIN, AUREON_WHITE_PAPER_RESEARCH_HUB, etc.) — the creator's original prose, do not paraphrase
  • docs/HNC_UNIFIED_WHITE_PAPER.md — formal theoretical paper, treat as immutable

Do not touch without explicit instruction:

  • Whitepapers in docs/research/whitepapers/ (PDFs/DOCX)
  • The 4 runtime-state JSONs at repo root
  • VERIFICATION AND VALIDATION/ (authoritative audit artifacts)
  • Anything under .git/, .github/, supervisord.conf, deployment configs

Quick facts for answering common questions

QA
What's the core claim?φ²-scaled coherence linking ancient knowledge systems, GitHub node activation, and market dynamics — r=0.85, 1.29 ppb precision
Is it falsifiable?Yes — 5 pre-registered predictions in docs/CLAIMS_AND_EVIDENCE.md
Is it live?Yes — watchable on Twitch (link in README), continuous GitHub activity
What's the Master Formula?Λ(t) = Σ wᵢ sin(2πfᵢt + φᵢ) + α tanh(g Λ_Δt(t)) + β Λ(t−τ) — stability regime β ∈ [0.6, 1.1]
Who's behind it?Gary Leckey · Aureon Institute · R&A Consulting and Brokerage Services Ltd.
License?MIT (maximum-transmission, by design)
How many modules?715 Python modules across 24 domains in aureon/
How many papers?54 in docs/research/whitepapers/, curated 13-paper canon in READING_PATHS.md
Autonomy mode?Public default full. AUREON_AUTONOMY_MODE=guarded is opt-in. Trading is live when the operator's exchange keys are in .env, otherwise paper/public-data. No kill switch and no failed-patch rollback. Self-changes and order attempts go to state/autonomy_audit.jsonl and the circulation thought bus, where repeated failed self-changes lower metacognition confidence and deprioritise a self-repair target. Credentials stay out of the repo and the logs. .env.example uses placeholder names only. A fresh blank-key copy ships disable and dry-run flags; they are not a lock, and a full+keyed master boot overrides them. A complete key group in the inherited shell or in aureon_radar/.env arms that boot even when the root .env is blank. See AUTONOMY.md and docs/PUBLIC_ENV.md
How do I launch everything?scripts/launch/aureon-master.sh on Linux and macOS, scripts/launch/aureon-master.ps1 or .bat on Windows. It writes .env from .env.example when .env is absent, installs Python requirements, Node packages, and Docker images, and starts the organism with paths relative to the checkout. Exchange keys in .env make that boot live. --status and --stop are process control. Inventory is in LAUNCHER_INVENTORY.md. Remaining machine assumptions are in PORTABILITY.md

If you're about to write new code / docs

  • Read docs/THE_SYNTHESIS.md first for voice calibration
  • Check docs/architecture/THEORY_TO_CODE.md for the HNC-equation → Python mapping
  • Run existing tests: pytest tests/ (pytest config in conftest.py)
  • Validate any new markdown links with: python3 -c "import re,os; ..." (see git history for the link-audit script pattern used in recent commits)

This file is the creator's answer to "what should an AI read first?" — keep it accurate. If you discover this file is stale or missing something important, update it in the same PR as your actual work.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.