A minimal working system
Begin with a model, external log, limited retrieval and update rules. Add a readable self-description with provenance, then test transfer between sessions. A small system is easier to investigate.
KAiScriptor compresses descriptions, ScriptorMemory organises keys, AIS implements event memory and review, SKAi specifies a broader self-state cycle, ontodiff explores lessons and ThreadWeave carries open topics. Check interface compatibility when combining them.
Extensions to investigate
Virtual Body Kai models a body map, states, rhythms and text/JSON output. It is an optional direction with adult material in its repository. Interpret its simulated-state descriptions with their measurement limits.
LLM Trance Protocol observes dialogue changes under repetitive patterns, with a control condition, exit signal and logs of latency, response length, silence and repetition. Its stated conclusions concern behaviour.
Action and causality
Embodied LLM Experiment asks whether a model can detect action-linked changes, predict consequences and distinguish external events. Public documentation describes discover/evaluate stages, saved states and full, empty, shuffled and other memory conditions.
Assess predictions and causal discrimination alongside self-descriptions. Deterministic-model runs test program behaviour, with further experiments needed to investigate model capabilities.
Retain the evidence for the next step
Save schema versions, change history, conditions and failed cases. Cite code commits or releases and publication records. Check the relevant licences before reusing source material.
Choose the next step from an observed gap in storage, retrieval, provenance or revision. Each focused change turns the broader question of identity into a reproducible investigation.
Put it into practice
- Map your system and each component’s responsibility.
- Choose one observed problem and one mechanism to change.
- Save the initial state, compare conditions and record the result’s limits.
Check the result
- Each component has a defined job.
- Optional extensions are identified as such.
- Versions, sources and limitations remain available.