GameCult/AquaSynth
Watch
9
0
Fork
You've already forked AquaSynth
 0
Code Issues Pull requests 4 Projects Releases Packages Wiki Activity Actions

Document greater daemon composition rule

Browse source
This commit is contained in:
Meta Vens 2026-06-15 02:42:48 +01:00
commit 0edd3ee21a
3 changed files with 58 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/daemonic-swarm-prior-work.md
View file

@ -136,3 +136,14 @@ script or supervisor starts daemons
The window is usually not the application. The window is the local Eve body. The
application is the swarm behind it.
## Composition Lesson
The cinematic pipeline makes the scale law visible: daemon capabilities compose
into greater daemons through typed command and receipt surfaces. A larger daemon
may own workflow state, scheduling, review, aggregate receipts, and escalation,
but it does not absorb the smaller daemons' truth. Brokkr coordination does not
own Unity or Blender state. Ghostlight coordination does not own Weksa language
truth, Vili motion synthesis, or AquaSynth audio rendering. The aggregate
surface must preserve lower-daemon provenance, rejections, and failures instead
of flattening them into one victorious-looking dashboard.

46
docs/gamecult-daemonic-swarm.md
View file

@ -140,6 +140,52 @@ The same pattern applies elsewhere:
Each daemon is a small sovereign machine. The swarm is the application.
## Greater Daemons
The useful trick is not that many daemons exist. The useful trick is that a
daemon can become a capability for another daemon without surrendering its own
authority.
That is how the swarm scales.
```text
small daemon capability
-> typed command/receipt surface
-> composed provider workflow
-> greater daemon capability
-> new typed command/receipt surface
```
AquaSynth can be a sound daemon by itself. Weksa can call it as one possible
speech body. Ghostlight can call Weksa as one possible actor-utterance organ.
Brokkr can call Ghostlight/Vili/AquaSynth outputs as scene-editing pressure.
An operator-facing cinematic tool can call Brokkr as a live editor body.
None of those calls mean the caller owns the callee's truth.
This is the difference between composition and mush. A greater daemon is not a
blob that absorbs smaller daemons. It is an orchestrator with its own authority
surface, built from other providers' command surfaces and receipts. It may own
workflow state, scheduling, review, escalation, and aggregate receipts. It does
not secretly own speech synthesis, animation generation, Unity editor state,
Blender editor state, or language truth just because it coordinates a pipeline
that uses them.
The composition rule:
- use another daemon through its published command documents;
- record the receipt you received;
- publish your own higher-level receipt for the workflow you own;
- preserve the lower daemon's provenance and failure state;
- do not rewrite another daemon's state as your own cache of truth;
- do not hide a rejected command inside a successful aggregate receipt;
- do not let the aggregate surface make authority look flatter than it is.
This gives GameCult a ladder. A mouth daemon can feed an actor daemon. An actor
daemon can feed a scene daemon. A scene daemon can feed a cinematic-production
daemon. A cinematic-production daemon can feed a game-content daemon. Every rung
is useful alone, and every rung can become the organ below a larger one.
## The Cinematic Content Swarm
The strongest current example is not a dashboard. It is the rapid creative