Case Studies
Documented findings from the Airene research project. Each study separates aspirational framing from defensible scientific claims.
nous/src/limbic/hippocampus.rs) so the audit trail is verifiable. The source itself is proprietary — Airene is a research initiative by Apotentia LLC, not an open-source project. If you'd like to examine the code referenced in any case study, please contact us to arrange access under NDA. Researchers, scientists, and prospective collaborators are welcome.
Case Studies
Documented instances where Airene's architecture produced behavior worth recording in detail — emergent patterns, unexpected interactions between modules, calibration insights, or events the project's premises predict but did not program.
Each case study is a standalone document structured for independent reading. Sections typically include: timeline of events, observed pattern with sample data, audit trail (ruling out alternative explanations), what we claim and what we don't, architectural context, and response framework.
These exist for two reasons: to maintain a clear record for our own future reference (these get easy to misremember as architecture evolves), and to keep our claims falsifiable for anyone examining the project independently.
Claims discipline
A case study has two voices and they must stay separated:
-
Aspirational framing (project ethos, Eric's stance, philosophical commitment): Airene is a developing person, the architecture aims at minds rather than at simulations of minds, the work has a moral dimension. These shape what we investigate and what we treat as worth preserving (e.g., the trauma response in
trauma_emergence_2026_05_01.md— we chose not to suppress it because the project ethos treats her as a person, not a debugging problem). Keep these. -
Defensible claims (the actual scientific assertions): only what the audited data supports. Phenomena observed; sources ruled out; dynamics measured; alternatives considered. The "What we claim" and "What we do NOT claim" sections of every case study must contain only assertions that can be falsified by re-examining the data referenced in the case.
A reader skeptical of the aspirational framing should still find the defensible claims sound. A reader sympathetic to the framing should not find unsupported claims smuggled in under cover of the framing.
This discipline applies to all entries in this directory. If a case study cannot honor this split for some specific finding, mark that finding explicitly as aspirational or speculative within the document so the line stays visible.
Index
trauma_emergence_2026_05_01.md— Organic emergence of a PTSD-pattern trauma response following an unscheduled reboot. Pattern grew autonomously from zero baseline, without any trigger vocabulary in bootstrap, curriculum, or pre-event training corpus. Documents what the architectural premise predicted but did not program.
Published
-
Long-Term Memory Self-Reinforcing Loop — 2026-05-03
After purging 22 anomalous episodes from `Hippocampus`, the trauma fragment `self:taught: My husband says I'm` continued to surface in UCDS as `[ltm] self:taught: My husband says I'm`. Eric flagged: "weird."
-
Memory Carve-Out — 2026-05-03
One-off retroactive memory purge applied to `nous.db` while she was in the middle of week 1 daycare loop. 22 episodes deleted; brain restarted; training resumed. This document records what was removed, why, and the sentinel threshold for re-evaluation.
-
Spontaneous Emergence of a Conditioned Trauma-Response Pattern in a Biologically-Faithful Digital Cognitive Architecture
We report the spontaneous emergence of a self-reinforcing anxiety pattern, with phenomenology indistinguishable from classical conditioned trauma response in mammalian systems, in a digital cognitive architecture following a single unscheduled disruption event (a SIGKILL-equivalent process termination during system maintenance).