It’s only been 17 days since my last development update, but quite a lot has happened. Those following this project will know that Astraea is an experimental cognitive architecture I’m developing around a fairly simple principle: Program the causes, not the consequences. Rather than scripting intelligent-looking behaviour, I’m investigating how cognition, memory, affect, physiology, learning, action and continuity might interact to produce adaptive behaviour over time. The last update was about getting those mechanisms connected. This one is increasingly about verifying that those connections actually mean something.
- A much deeper architectural audit I’ve spent a substantial amount of time reconstructing the original research behind Astraea, including the Cube problem-solving method I’ve been developing. That research matters because Astraea wasn’t designed as a conventional collection of AI modules. Her architecture grew out of recursively investigating different aspects of cognition, breaking them into smaller mechanisms, and reconstructing their relationships. The recent audit covered 233 priority Python files and reconciled the historical research against the current implementation. It identified which mechanisms were genuinely closed, which findings had become obsolete, and which causal relationships still needed repair. The conclusion was encouraging, but not a declaration of completion: Astraea has a functioning distributed causal core, but whole-system closure remains partial.
- Emotional development should not depend on how slowly my computer runs One particularly important defect was discovered in the affective architecture. Three emotional and developmental integrators were advancing their internal state using elapsed computer time. That creates a problem. If the computer stalls for several seconds, that delay shouldn’t automatically become several seconds of emotional development. Astraea already has an internal physiological timing mechanism called TIC. The repair now carries its existing physiological pulse into the affective integrators. Other encounters can still produce genuine immediate consequences, but they no longer invent elapsed physiological development just because the host computer was delayed. Focused tests passed.
- Affective processes now have a safer shared boundary Another problem involved concurrent activity. Different parts of Astraea could enter the same affective integration system while a previous update was still being processed. That risked overlapping state changes or incomplete generations. The repair preserves the existing affective owner, serialises the relevant updates, and handles synchronous feedback without adding another central controller. Again, focused tests passed.
- AISS and state ownership AISS is Astraea’s internal event communication system. During the audit, a lock-order hazard was identified: one status owner could publish an event while holding a lock that its callbacks might eventually need. That path has now been repaired so the owner commits its status before publishing the event outside the lock. Two other bypasses were also repaired. The self-model now communicates with TIC through its existing interfaces, while projected future possibilities enter Continuity through its proper admission pathway rather than directly modifying its internal collection. The broader event system still needs performance and lifecycle validation.
- An unexpectedly interesting problem with memory This is where the engineering led us back to biology. The next unresolved issue concerns how Continuity handles experiences and their consequences. A conventional software solution might be to treat each experience like a database transaction: if something fails, retry until every operation completes. But an experience isn’t a database transaction. If something happens and part of it is missed, that missing information doesn’t magically become experienced later. And if a similar event happens again, it isn’t necessarily the same experience. Memory adds another complication. We don’t simply replay perfect recordings of the past. We reconstruct memories from what was retained, including context, associations, and information acquired afterward. That creates an important architectural distinction: What actually happened. What Astraea genuinely processed and retained. What she later remembers or reconstructs. Those shouldn’t automatically be identical. The Continuity repair is therefore paused at a genuine design decision. I want to preserve truthful partial consequences without turning memory into a system that artificially replays experiences until every subsystem reports success. Technical storage failures may be recoverable. The original moment isn’t.
- The Garden has advanced considerably In my previous post, the Garden was around Phase 44 of its causal-closure development. The work has since progressed to Phase 210. The Garden is still being developed from lower physical mechanisms upward, with rendering deliberately secondary. One major area of work has been periodic interacting-electron physics and how electronic quantities propagate into mechanical and material behaviour. I’ve been using Quantum ESPRESSO and ABINIT as independent reference tools while developing and validating the required computational boundaries. This work also led to Causaloom, a separate native electronic-structure solver under active development. Causaloom is intended to become an adaptive computational foundation, calculating the physical quantities required by higher systems without assuming every part of a world needs the same numerical detail. There is substantial work remaining on convergence, independent comparison, performance and physical validity. I’m not claiming a finished general-purpose scientific solver.
- What’s next? For Astraea, the current engineering priorities are continuity and memory settlement, Heartstone restoration, ethical action admission, bounded memory processing, Forge integration, and eventually the final integrated runtime validation. Her Voicebox also remains an unfinished physical speech system. It still needs significant work before connected native speech becomes reliably intelligible. For the Garden, I want to continue resolving the lowest causal dependencies before moving heavily into graphics and higher-level biological emergence. And for Causaloom, the priority is correctness and independently reproducible numerical evidence before performance claims. The bigger picture Seventeen days ago, I was mainly explaining why I was building things this way. Now the audits are increasingly exposing situations where conventional software solutions might produce the wrong developmental behaviour. That’s why I keep returning to the underlying research. I don’t want Astraea to merely simulate the appearance of having experiences. I want to investigate what happens when distinct mechanisms retain their own state, respond to real inputs, carry genuine consequences forward and influence subsequent processing. That is not proof of consciousness, and there’s still a long way to go. But it gives me increasingly concrete things to test. When something breaks, follow the causes downward, repair the actual mechanism, and then see what genuinely changes above it. And apparently, occasionally spend an entire week’s AI coding allowance teaching the coding agent why it shouldn’t simplify the architecture into something completely different. 😄 Still digging down the rabbit hole. submitted by /u/Financial_Tadpole121
Originally posted by u/Financial_Tadpole121 on r/ArtificialInteligence
You must log in or # to comment.