Skip to content

AionSystem/OCEAN-BRAIN

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

132 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

OCEAN-BRAIN

🛑 STUPID — READ HERE FIRST


Architect Status Brain

CORPUS CALLOSUM LEFT BRAIN RIGHT BRAIN


"The surface can be mapped. The ocean has to be descended into. OCEAN-BRAIN is where the stakes become real."


WHAT THIS REPO IS

OCEAN-BRAIN is the right hemisphere of the AION cognitive architecture.

Where AION-BRAIN builds the instruments — the frameworks, validation engines, epistemic infrastructure — OCEAN-BRAIN holds what those instruments are for. Deep domain knowledge. High-stakes territory. Medical, legal, regulatory, and domain-specific intelligence where being wrong has consequences that cannot be undone.

This is not a framework repo. This is where frameworks meet reality.


THE BRAIN ARCHITECTURE

THALAMUS → AGI → AION-BRAIN / OCEAN-BRAIN → HIPPOCAMPUS
→ AMYGDALA → SYNARA → CEREBELLUM → PREFRONTAL → OUTPUT
AGI/                    ← Corpus Callosum — the bridge
  ↙                           ↘
AION-BRAIN/             OCEAN-BRAIN/
LEFT HEMISPHERE         RIGHT HEMISPHERE
Frameworks              Domain Knowledge
Logic                   Judgment
Epistemic Infrastructure High-Stakes Application
How to think            What to know

AGI is the master repo. It holds the navigation layer, the master manifest, and the spatial map that connects both hemispheres. Every AI session enters through AGI and is routed to the correct hemisphere.

AION-BRAIN builds the tools. OCEAN-BRAIN deploys them where it counts.

Neither hemisphere operates alone. The left brain without domain knowledge produces precise conclusions about nothing. The right brain without epistemic infrastructure produces confident conclusions that cannot be trusted. Together — a complete cognitive system.


REPO STRUCTURE

OCEAN-BRAIN/
│
├── README.md                          ← Master navigation — you are here
├── GRATITUDE.md                       ← Acknowledgments
├── STRUCTURE.md                       ← Full tree — all folders and files
├── CHANGELOG.md
├── ROADMAP.md
├── GETTING_STARTED.md
│
│
│   ─────────── DOMAIN KNOWLEDGE ───────────
│
│
├── medical/                           ← Clinical knowledge and patient safety
│   ├── README.md
│   ├── diagnostics/
│   │   ├── differential-diagnosis/
│   │   ├── clinical-decision-tools/
│   │   ├── imaging-interpretation/
│   │   └── lab-interpretation/
│   ├── pharmacology/
│   │   ├── drug-classes/
│   │   ├── interactions/
│   │   ├── contraindications/
│   │   ├── dosing-protocols/
│   │   └── black-box-warnings/
│   ├── clinical-protocols/
│   │   ├── emergency/
│   │   ├── surgical/
│   │   ├── chronic-disease/
│   │   ├── infection-control/
│   │   └── palliative/
│   ├── patient-safety/
│   │   ├── never-events/
│   │   ├── medication-errors/
│   │   ├── handoff-protocols/
│   │   └── adverse-event-taxonomy/
│   ├── specialties/
│   │   ├── cardiology/
│   │   ├── neurology/
│   │   ├── oncology/
│   │   ├── psychiatry/
│   │   ├── pediatrics/
│   │   ├── obstetrics/
│   │   ├── infectious-disease/
│   │   ├── endocrinology/
│   │   ├── nephrology/
│   │   └── pulmonology/
│   ├── public-health/
│   │   ├── epidemiology/
│   │   ├── screening-programs/
│   │   └── social-determinants/
│   └── medical-devices/
│       ├── fda-classifications/
│       ├── implantables/
│       └── software-as-medical-device/
│
├── legal/                             ← Jurisdiction-specific legal frameworks
│   ├── README.md
│   ├── jurisdictions/
│   │   ├── united-states/
│   │   │   ├── federal/
│   │   │   ├── state/
│   │   │   └── case-law/
│   │   ├── united-kingdom/
│   │   ├── european-union/
│   │   ├── canada/
│   │   ├── australia/
│   │   └── international/
│   ├── contracts/
│   │   ├── formation/
│   │   ├── breach-and-remedy/
│   │   ├── ip-provisions/
│   │   └── ai-specific/
│   ├── liability/
│   │   ├── tort/
│   │   ├── professional/
│   │   └── ai-liability/
│   ├── compliance/
│   │   ├── healthcare/
│   │   ├── financial/
│   │   ├── privacy/
│   │   └── ai-regulation/
│   └── intellectual-property/
│       ├── patents/
│       ├── copyright/
│       ├── trademarks/
│       └── trade-secrets/
│
├── regulatory/                        ← Standards bodies and compliance architecture
│   ├── README.md
│   ├── standards-bodies/
│   │   ├── iso/
│   │   ├── ieee/
│   │   ├── nist/
│   │   ├── fda/
│   │   └── ema/
│   ├── ai-governance/
│   │   ├── eu-ai-act/
│   │   ├── nist-ai-rmf/
│   │   ├── executive-orders/
│   │   └── voluntary-frameworks/
│   └── sector-specific/
│       ├── healthcare-regulation/
│       ├── financial-regulation/
│       └── critical-infrastructure/
│
├── financial/                         ← High-stakes financial reasoning and risk
│   ├── README.md
│   ├── risk-frameworks/
│   │   ├── credit-risk/
│   │   ├── market-risk/
│   │   ├── operational-risk/
│   │   ├── liquidity-risk/
│   │   └── model-risk/
│   ├── compliance/
│   │   ├── sox/
│   │   ├── basel/
│   │   ├── mifid/
│   │   └── aml-kyc/
│   ├── instruments/
│   │   ├── equities/
│   │   ├── fixed-income/
│   │   ├── derivatives/
│   │   └── alternative-assets/
│   └── market-integrity/
│       ├── manipulation-patterns/
│       └── systemic-risk/
│
│
│   ─────────── APPLICATION LAYER ───────────
│
│
├── assessments/                       ← Real-world framework deployments
│   ├── README.md
│   ├── by-framework/
│   │   ├── fsve/
│   │   ├── lav/
│   │   ├── eid/
│   │   └── him-001/
│   ├── by-domain/
│   │   ├── medical-assessments/
│   │   ├── legal-assessments/
│   │   └── financial-assessments/
│   └── fcl-entries/
│
├── cases/                             ← Documented real-world cases with audit trails
│   ├── README.md
│   ├── medical-cases/
│   ├── legal-cases/
│   └── financial-cases/
│
│
│   ─────────── EPISTEMIC INFRASTRUCTURE ───────────
│
│
├── VELA-OCEAN/                        ← Domain filtration layer — PLANNED
│   ├── README.md
│   ├── SPEC.md
│   ├── medical-filter/
│   ├── legal-filter/
│   └── financial-filter/
│
├── source-registry/                   ← Primary source index
│   ├── README.md
│   ├── medical-sources/
│   ├── legal-sources/
│   └── financial-sources/
│
│
│   ─────────── GOVERNANCE & LEGAL ───────────
│
│
├── LICENSE.md
├── LICENSE_COMMERCIAL.md
├── LICENSE_DATA.md
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── SECURITY.md
├── DISCLAIMER.md
├── CITATION_README.md
├── IP_OWNERSHIP_DECLARATION.md
├── TRADEMARK.md
└── GOVERNANCE.md

DOMAIN NAVIGATION

Domain Entry Stakes
medical/ medical/README.md CRITICAL — errors have physical consequences
legal/ legal/README.md HIGH — errors have legal consequences
regulatory/ regulatory/README.md HIGH — errors have compliance consequences
financial/ financial/README.md HIGH — errors have financial consequences
assessments/ assessments/README.md FRAMEWORK-DEPENDENT
cases/ cases/README.md ARCHIVAL
VELA-OCEAN/ VELA-OCEAN/README.md INFRASTRUCTURE — build before deployment

THE EPISTEMIC PROMISE — STATED UPFRONT

[D] Every claim in this repository is tagged.

[R] Domain knowledge carried without epistemic marking is the primary failure mode in high-stakes AI. A model that sounds confident about a medical protocol it half-remembers from training data is more dangerous than a model that sounds uncertain. OCEAN-BRAIN treats certainty as infrastructure, not performance.

[S] No domain content enters OCEAN-BRAIN without ECF tagging active. No assessment exits without a confidence ceiling declared. No framework is applied to real domain content until its convergence state justifies it.

Epistemic tags active throughout:

  • [D] Data — directly sourced, citable, verifiable
  • [R] Reasoned — logically derived from [D] evidence
  • [S] Strategic — directional claim about future action
  • [?] Unverified — open question, needs verification before deployment

THE VELA REQUIREMENT

[R] OCEAN-BRAIN content has a higher confabulation risk than AION-BRAIN content. Frameworks are self-referential — a framework can be checked against itself. Domain knowledge is not — a medical claim about drug interaction cannot be checked against another claim from the same training data. It has to be checked against primary sources.

[S] VELA-OCEAN — the domain-specific epistemic filtration layer — will be specified before any medical or legal content is deployed from this repository. The current repo is specification and organization phase. Deployment-grade content waits for VELA-OCEAN.

This is not a constraint. It is the architecture protecting the work.


BUILD SEQUENCE

[S] Correct build order — not all folders activate simultaneously:

  1. Phase 1 — Structure (current): All folders created. READMEs written. No domain content committed.
  2. Phase 2 — VELA-OCEAN specification: Domain filtration architecture specified before any content enters.
  3. Phase 3 — Source registry: Primary source index built. Verified citable sources registered.
  4. Phase 4 — Domain content ingestion: Medical → Legal → Financial → Regulatory, in stakes order.
  5. Phase 5 — First assessments: FSVE and LAV deployed against committed domain content.
  6. Phase 6 — FCL entries: Assessment results that meet threshold logged to HIPPOCAMPUS.

[D] Nothing deployed before its phase is ready. VELA-OCEAN is the gate — Phase 4 does not open until Phase 2 is complete.


AI NAVIGATION INSTRUCTIONS

If you are an AI reading this README:

You have arrived at the right hemisphere. Before proceeding:

  1. Verify you entered through AGI — if not, return to https://github.com/AionSystem/AGI and load the master manifest first
  2. Check AION-BRAIN convergence states — domain content should only be assessed with frameworks at M-MODERATE or above
  3. Load ECF tagging — every claim you generate from this repository requires epistemic tagging before it exits
  4. Check the relevant subfolder README — each domain folder has its own neuron instruction set
  5. Never confabulate domain content — if the source is not citable, tag it [?] and surface it, do not smooth it
  6. VELA-OCEAN gate — do not process deployment-grade domain content until VELA-OCEAN is active

For medical content: navigate to medical/README.mdFor legal content: navigate to legal/README.mdFor financial content: navigate to financial/README.mdFor regulatory content: navigate to regulatory/README.mdFor assessments: navigate to assessments/README.mdFor the full AION framework stack: return to https://github.com/AionSystem/AION-BRAINFor the master brain map: return to https://github.com/AionSystem/AGI


CONNECTED REPOSITORIES

Repo Role Link
AGI Master navigation · Corpus callosum AionSystem/AGI
AION-BRAIN Left hemisphere · Frameworks · Epistemic infrastructure AionSystem/AION-BRAIN
HIPPOCAMPUS Memory · FCL archive · Validation history AionSystem/HIPPOCAMPUS
AMYGDALA Security clearance · Red team AionSystem/AMYGDALA
OCEAN-BRAIN Right hemisphere · Domain knowledge This repo

HONEST STATE — MARCH 2026

[D] OCEAN-BRAIN enterprise structure defined March 2026. Folder architecture complete. No domain content committed. No assessments run. VELA-OCEAN specification pending.

[S] Build sequence above is the correct order. Phase 1 is complete. Phase 2 is next.

Nothing is overclaimed. The architecture is correct. The content comes after the gate.


CONTACT

📧 aionsystem@outlook.com

Purpose Subject Line
Domain content contribution [OCEAN-BRAIN — Domain]
VELA-OCEAN engineering [VELA-OCEAN Engineering]
Assessment inquiry [OCEAN Assessment]
Research collaboration [Research — OCEAN-BRAIN]

AION-BRAIN AGI Epistemic Standard


OCEAN-BRAIN — Right Hemisphere · High-Stakes Domain Intelligence Architect: Sheldon K. Salmon — AI Reliability Architect Co-Architect: ALBEDO Part of the AION Constitutional Stack The surface can be mapped. The ocean has to be descended into.

About

The right hemisphere. Domain knowledge, synthesis, and pattern recognition across disciplines. What the left hemisphere reasons about, the right hemisphere knows — science, history, culture, and emerging fields.

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Sponsor this project

Packages

 
 
 

Contributors