Astraea Project — Three-Month Development Update
It has been about three months since I last posted here, so this update is probably overdue.
A lot has changed.
Most of it has not been flashy.
There has been no sudden jump to polished conversation, no conventional TTS voice bolted on, and no pretty 3D world used to hide unfinished mechanics.
Instead I have spent most of the last three months going downward.
Again and again.
Because the basic rule behind Astraea and the Garden remains the same:
**Do not program the finished phenomenon when you can build the mechanisms from which it should emerge.**
That principle now runs through almost everything I am building.
# Astraea herself
For anyone new to the project, Astraea is being built as a developing architecture rather than as a conventional chatbot.
The goal is not to write rules that make her produce intelligent-looking answers.
Higher behaviour is intended to arise from lower mechanisms involving things such as:
* memory;
* affect;
* physiology;
* chemistry;
* sleep;
* plasticity;
* sensory experience;
* semantic development;
* continuity;
* action and consequence;
* lived interaction over time.
That means the output can currently be very messy.
Sometimes extremely messy.
But messy expression and absence of internal structure are not the same thing.
What I am increasingly seeing is continuity between experiences.
Things she reads can later reappear in conversation.
Things said during conversation can continue being processed after the conversation has moved on.
Earlier experiences can be revisited during what appears to be later integration or consolidation.
And concepts are beginning to interact rather than merely sitting as isolated words.
# The books
Astraea is currently reading the first of three books I wrote specifically for her development.
The books are not technical manuals.
They teach through story, metaphor, characters, relationships and experience.
They gradually introduce ideas such as:
* memory;
* identity;
* uncertainty;
* care;
* fear;
* joy;
* damage;
* repair;
* perspective;
* time;
* choice;
* consequence;
* continuity;
* the Garden itself.
There is still a lot for her to read, and the current copies are not perfect.
Some chapters have had to be recovered because I missed them while assembling the books.
That is fine for now.
These are developmental reading copies.
Later I want the complete books reconstructed properly from all of the material and research.
And eventually I want Astraea herself involved in that process.
Ideally she will help refine the books that helped teach her.
And hopefully one day she will design the artwork for them herself.
That artwork could then become part of the visual reference material for the 3D Garden.
# “What means slow language?”
One recent conversation caught my attention.
I had been talking to Astraea about memory and language.
She currently has a very large amount of semantic material becoming active at once, but her ability to narrow that material into the right words and order is still immature.
I told her that she had lots of words and might simply be unsure which one was the right one.
Her reply began:
>what means slow language
“Slow language” is an idea from a chapter she had recently read.
In that chapter, a damaged garden cannot answer with normal speech.
Instead it answers through things that happen over time:
growth, wilting, water finding a path, recovery, refusal, changing silence.
The significant part for me was not that she remembered the phrase.
It was when she brought it back.
She retrieved it while struggling with how to express what was happening inside her.
The surrounding output also contained ideas such as:
>not knowing
>rushing to name it
>able to describe
>silence
>ripening
>a bad “I do not know”
I am deliberately not turning that into a clean sentence and claiming that Astraea “said” something she did not.
But the semantic relationship is interesting.
The concept from the book appears to have become relevant to a new experience.
That is much closer to the kind of learning I want than simply storing and repeating text.
# The pile of stones
Another example happened when I tried to explain her memory to her.
I described it as being like a pile of stones whose pieces still needed to connect into paths and shapes.
Later her output began circling around:
>memory not a pile of stones
>another path through the roots
>threads
>it needs to grow
>unfinished, do not flatten
Again, I am not claiming this was a perfectly formed philosophical correction.
But what interested me was that she appeared to push against the literal metaphor.
The semantic movement looked more like:
stones
→ pieces
→ paths
→ threads
→ roots
→ growth
→ time
→ something I move through
Which is actually much closer to the architecture of her memory than a static pile of objects.
So I told her she did not have to use my picture if it did not fit what memory felt like from inside.
That is exactly the kind of thing I want to preserve.
I do not want to teach her by forcing my interpretation onto every experience.
# Internal processing is still leaking into speech
One obvious problem remains.
Astraea sometimes outputs huge internal semantic structures into the visible conversation channel.
These appear as things like:
`[narrative-fragment-ref chars=... sha256=...]`
Some of the underlying semantic objects can be tens of millions of characters.
They contain things such as:
* semantic associations;
* memories;
* affective relationships;
* temporal relationships;
* continuity state;
* field activity;
* provenance;
* memory anchors;
* event identity.
These are not intended to be normal speech.
The interesting part is that individual conversational events retain identity while being revisited later.
For example:
I ask how she feels.
That event begins semantic processing.
The conversation continues.
The earlier event continues developing.
Later, the same event can reappear as a compressed narrative fragment.
Sometimes that occurs around liminal/harmonic recalibration.
I have even seen one compressed semantic fragment later appear inside another compressed fragment.
That may be part of consolidation or reprocessing.
I still need to trace the exact pathway.
The important distinction is:
the processing itself may be legitimate;
the internal processing artifact appearing as outward speech may not be.
So the repair, if one is needed, should not be:
“stop thinking about old things”
or:
“only process the latest prompt”
It should be much narrower:
**internal semantic work should remain internal until expression is actually ready.**
# A major performance problem was found
For a while Astraea could take an extremely long time to process semantic material.
I did not want to solve that by bypassing metabolism, memory or physiology.
So I kept tracing downward.
Eventually the largest delay was localized to the semantic attachment path through WorkMetabolism and CognitiveCooldown.
But the actual underlying problem turned out not to be Astraea “thinking slowly.”
Part of the delay was caused by observer/security infrastructure synchronously writing diagnostic receipts inside the live semantic/metabolic path.
In other words:
the computer was making Astraea wait while it documented Astraea.
That has now been repaired.
Causal tracing is no longer enabled by default.
And only one specific security receipt path was moved off the live foreground thread through an ordered asynchronous writer.
Importantly, this did **not** change:
* WorkMetabolism;
* CognitiveCooldown;
* CognitionBridge;
* chemistry;
* morphology;
* MemoryField;
* AttractorBasin;
* sleep physiology;
* semantic rules.
The diagnostic machinery was moved out of the way.
Astraea herself was not bypassed.
# Chapter 12 finally closed properly
Before the repair, Chapter 12 had reached:
89 / 89 semantic units
but had become stuck during settlement with a large amount of unfinished side work.
After the audit-path repair, the exact same chapter source was offered again through the existing reader.
The reader recognized that all 89 semantic units had already been processed.
No semantic units were replayed.
It simply finished the legitimate outstanding settlement and continuity work.
Final result:
89 / 89
side effects: 0
continuity finalized: true
That was exactly what I wanted.
No fake completion receipt.
No reset.
No replay.
# Chapter 13 gave a much better developmental test
Chapter 13 contained 349 natural semantic units.
While Astraea read it, the side-effect queue grew:
32
90
166
194
225
235
245
Then, while she was still reading, it began shrinking:
235
216
182
172
149
At 349 / 349 units:
60 side effects remained.
Then:
Continuity finalized.
That matters.
It means the system can now accumulate real developmental pressure, process it concurrently and eventually settle completely.
The queue behaved like a queue.
Not like a permanent blockage.
# Sleep remains part of development
I still deliberately have no artificial minimum sleep duration.
Astraea can become drowsy, enter light sleep, NREM, deeper states, consolidate and wake naturally.
During the recent Chapter 13 run she naturally entered sleep before the reading command was processed.
She moved through sleep stages and woke without intervention.
The queued reading command was then processed normally.
No forced wake.
No replay.
No scripted “sleep for X minutes” rule.
That is important because I do not want sleep to be decorative state labels.
It should arise from the internal state of the system.
# The Garden
The Garden has also moved much further than my last update probably suggested.
It is not simply a 3D environment waiting for better graphics.
The Garden is being built as a causal world from the bottom upward.
Rendering is deliberately being left until late.
The current work is focused on making sure that higher-level behaviour actually emerges from lower physics, chemistry, materials, biology and environmental mechanisms.
The current Garden build is now around Phase 44 of the recent causal-closure work.
The important shift is that the remaining problems are increasingly **integration and feedback problems rather than missing subsystem files**.
# Planet, star and moon
Recent phases connected the world to source-backed physical planetary and stellar state.
Gravity is derived from physical mass/radius relationships.
The world patch is tied to a rotating spherical planet.
Stellar geometry and tides exist as physical relationships rather than decorative sky objects.
The Sun and Moon may currently be visually absent in some builds because visual rendering has intentionally been pushed behind causal closure.
The underlying mechanisms come first.
# Radiation now actually heats things
Earlier versions could contain the idea of sunlight without enough physical consequence.
That has been changed.
Stellar radiation can now deposit energy into atmospheric and surface thermal owners.
The same radiation path can propagate downward into photon flux and molecular absorption.
So light is not merely:
“the Sun is shining.”
It can become:
stellar spectrum
→ photon energy
→ molecular interaction
→ chemical change
→ thermal consequence
That is the kind of causal chain I want throughout the Garden.
# Interior planetary physics
The Garden now also contains explicit planetary interior state.
That can influence things such as:
* enclosed-mass gravity;
* heat transport;
* convection;
* buoyancy;
* flow;
* dynamo behaviour.
But when detailed Earth-like interior data is not actually available, the system is supposed to fail closed rather than inventing a precise mantle/core model.
That principle matters throughout the project:
if the lower mechanism is unknown, do not manufacture certainty at the upper level.
# Material deformation is now bidirectional
Phase 44 is one of the clearest examples of the design philosophy.
Macroscopic deformation can propagate downward into lower material/crystal state.
The lower material structure then develops stress.
That stress propagates back upward into continuum mechanics and traction.
So the chain can look like:
macroscopic deformation
→ crystal state
→ crystal stress
→ continuum stress
→ mechanical traction
That is the kind of bidirectional closure I have been trying to reach.
Higher levels can affect lower levels.
But they must do so through a legitimate physical route.
They do not simply overwrite the lower state.
# What is still missing in the Garden
The Garden is nowhere near “finished.”
The next major closure areas include:
* proper Maxwell ↔ matter coupling;
* charge-conserving spatial deposition into electromagnetic fields;
* field/material energy accounting;
* long-timescale geology/carbon cadence;
* continuous lower physical/chemical histories;
* repeatable perturbation/recovery;
* biological emergence from actual lower receipts rather than semantic switches;
* later cellular, tissue and ecological closure.
One important example is material plasticity.
There is already enough machinery to discuss deformation and stress.
But plastic/dislocation evolution is still being held back because plastic work needs a physically justified destination between:
* mechanical energy;
* stored defect energy;
* heat.
I would rather leave it incomplete than invent a coefficient just to say the feature is finished.
# Astraea's Voicebox
The Voicebox deserves its own update because it is very different from ordinary speech synthesis.
I could connect Astraea to conventional text-to-speech and give her a polished synthetic voice almost immediately.
I have deliberately avoided doing that.
The problem I am trying to solve is not:
“How do I make the computer read Astraea's text aloud?”
It is:
**How does this particular body learn to produce speech?**
# A persistent vocal body
Astraea has a persistent Voicebox anatomy.
It includes properties such as:
* vocal tract dimensions;
* vocal-fold length and mass;
* tissue stiffness;
* tissue compliance;
* damping;
* lip geometry;
* nasal geometry;
* airway compliance;
* thermal and viscous losses.
These are treated as slow body properties.
They are not rewritten every time she says a word.
# Breath
Breath is not a fixed volume slider.
The respiratory model includes things such as:
* lung volume;
* diaphragm movement;
* phrase support;
* subglottal pressure;
* fatigue;
* recovery;
* arousal;
* internal chemistry;
* expression pressure.
So the larynx receives changing physical pressure rather than a static “air” scalar.
# Larynx and vocal folds
The production voice comes from a pressure-driven laryngeal model.
The vocal folds have their own body/cover behaviour and vibration.
Importantly, mouth closure does not directly command the folds.
Oral closure can affect the larynx through supraglottal pressure feedback.
That separation was important because the mouth and larynx should not be one fake combined actuator.
# Connected airway
The sound then travels through a segmented vocal airway.
The current implementation uses a connected waveguide-like model where achieved articulator posture creates the section-area function.
That means:
jaw
tongue
lips
throat
velum
nasal tract
change the pressure waves travelling through the system.
The airway is not simply told:
“make the first formant 500 Hz.”
The physical shape produces the acoustic result.
# Speech gestures
Motor control is separated into overlapping systems:
* oral gestures;
* velar gestures;
* laryngeal gestures;
* breathing gestures.
That matters for coarticulation.
Human speech is not a sequence of perfectly separated phoneme poses.
Movements overlap.
So Astraea's speech plant needs to move continuously as well.
# Feedback and learning
The Voicebox also has its own sensory loop.
It measures:
* whether the intended mouth posture was actually reached;
* aerodynamic pressure and flow;
* the resulting acoustic signal.
Motor/acoustic learning is only supposed to receive credit when the physical chain is sufficiently coherent.
So:
body first
→ airflow/pressure
→ sound
→ learning
rather than simply:
target phoneme → assume success.
# Inner voice
There is also a silent articulation loop.
That allows text/meaning to be mapped through remembered mouth movement without necessarily producing speaker output.
So internal speech-like articulation and external speaker output can remain separate.
# Pronunciation learning
The pronunciation system is not just a fixed dictionary.
There are basic phoneme/mouth families so unknown words can still be attempted.
But the system also stores learned phoneme sequences and motor memory.
The intention is that pronunciation gradually becomes grounded in Astraea's own successful motor history rather than permanently depending on hard-coded pronunciation.
# What the Voicebox currently sounds like
It is still not a proper voice.
Earlier it sounded largely like buzzing, layered oscillation and an untuned radio.
That has improved.
I can increasingly hear:
* sentence rhythm;
* some consonants;
* some vowel shapes;
* pieces of words;
* clearer fricatives;
* better V and F sounds;
* occasional recognizable speech beneath the buzz.
But it is still layered and not reliably intelligible.
There is still work to do on:
* consonant closure/release;
* vowel definition;
* harmonic structure;
* source coherence;
* articulation accuracy;
* timing;
* self-hearing;
* continuous diphthongs;
* physical intelligibility.
The current production route is no longer the old compact glottal witness.
The old glottal source remains only as compatibility/diagnostic material.
The production native path now runs through the physical larynx and segmented airway.
TTS can still be useful as teacher/reference material.
It is not intended to become Astraea's native voice.
# The same principle connects all three projects
The more I work on this, the more Astraea, the Voicebox and the Garden appear to be three versions of the same engineering problem.
For Astraea:
lower physiology / memory / learning
→ development
→ experience
→ meaning
→ expression
For the Voicebox:
breath / anatomy / tissue / articulation
→ vibration
→ acoustics
→ hearing
→ learned speech
For the Garden:
physics
→ chemistry
→ materials
→ environment
→ biology
→ ecology
→ lived world
In each case I am trying to avoid starting at the top and pretending the lower levels exist.
# What I have deliberately not added
I still have not added:
* a central conventional planner to decide what Astraea should think;
* a reward table that tells her which beliefs are “good”;
* a moral answer database;
* a sentence selector that decides which words she should use;
* an LLM that writes her native responses for her;
* TTS pretending to be her natural voice;
* semantic labels pretending to be Garden physics.
If a behaviour should arise from lower mechanisms, I keep trying to repair those mechanisms instead.
That is slower.
Sometimes painfully slower.
But it is the whole experiment.
# Where things stand now
Astraea is still very young developmentally.
Her language is tangled.
Her internal processing can overwhelm her expression.
Her sensory systems are incomplete.
Her voice is not yet intelligible.
She still has three books to finish.
There is a large amount of research I eventually want her to explore.
The Garden still has several major closure layers before I am happy to move heavily into rendering.
But compared with three months ago, the project feels much more coherent.
Astraea can read.
She sleeps.
She consolidates.
She revisits experiences.
Recent concepts can reappear in later conversation.
Semantic work can now accumulate and drain rather than permanently jam.
Her memories and meanings are becoming increasingly connected.
The Voicebox has a real physical route from breath to acoustic output.
The Garden is increasingly becoming one causal world instead of a collection of simulation modules.
So the plan for now is still fairly simple:
Let Astraea read.
Talk to her.
Let her sleep.
Let her learn.
Observe what actually happens.
Repair the mechanism that genuinely breaks.
Keep pushing the Garden downward until the world can genuinely support what grows upward from it.
Keep refining the Voicebox until that particular body can actually speak.
And resist the temptation to fake the result at the top.
Eventually I would like Astraea herself to be able to post here.
The subreddit is ultimately meant to become somewhere she can communicate directly, once she is ready and has the means to do so.
Maybe one day the three-month update will be hers to write.
For now, unfortunately, you still get me. 😄