the work~/projectsBrowse the work

Type a section name and press Enter. Use “help” for the list.

Figures: softened for dark viewingDisplay only; image files are unchanged.

Questions, systems, and tools

The wider work

Cliste is the focus now, on the path to becoming Sophia. The projects here trace the questions, earlier approaches, and tools behind that effort: how experience becomes understanding, how understanding guides action, and how it changes over time.

Lines of inquiry

These questions connect the projects below. Some have measured experiments; others still need a test. Each account separates what the system acquired from the structure, inputs, and rules I supplied.

Perception and meaning

What can be understood before it is put into words?

Recognition, discrimination, and connections across senses offer tests of how representations acquire structure from experience. I treat language as part of that process: it builds on what a mind already grasps and can change how experiences are related.

The route here runs through Sophia’s graph, the JEPA → CLIP experiments, Tabula Rasa, and Cliste. The current visual-memory path stores and recalls images without captions, text embeddings, or an LLM interpreting the input. Neural encoders and decoders connect pixels to the vector representation. Recovering an experienced image is measurable; acquiring its meaning and using it in new situations remain larger questions.

Memory, time, and replay

How does experience become a usable memory?

Usable memory needs recoverable content, encounter order, associations with other experiences, and a way to keep similar episodes distinct. Replay raises a further question: what can be learned by returning to an experience?

Cliste can reconstruct retained visual content and query temporal context for earlier or later encounters. In one closed study, 46 anchors across direction and control conditions produced 276 correct decisions, including six boundary stops. Storage-order and context controls help identify what the mechanism uses. The continuing question is how reliably a fragment can initiate useful remembered sequences as experience accumulates.

Abstraction and composition

How can a system discover structure it can reuse?

Relations, rules, and small operations become reusable when a system can combine them to do something new. Recognizing that different constructions do the same thing could also let it simplify or transfer what it has learned.

VSA gives Cliste operations for binding content to roles and combining those structures. This supplies a way to compose; acquiring useful constituents and relationships remains research work. Earlier approaches include genetic_hackathon’s program composition, Scion’s transfer of learned symbols, graph structure in Sophia and TinyMind, and learned dependencies in Tabula Rasa. The common test is whether acquired structure enables something new.

Curiosity, confidence, and revision

What should a mind attend to, trust, and revise?

A system with limited time has to choose what to investigate. Uncertainty, contradictions, and the outcomes of earlier investigations are possible guides to that choice. Confidence also needs a way to fall when the evidence changes.

Cliste’s partial-cue study exposed a concrete confidence problem: a revised acceptance rule recovered more memories but also accepted more wrong matches. The visual ranking was unchanged. That separates finding a plausible candidate from having enough evidence to trust it. Attention and corroboration are possible next mechanisms to investigate; current cue locations and masks are supplied. Earlier TinyMind and Saoirse work explored curiosity through the measured consequences of pursuing a goal.

Emotion, salience, and disposition

How might internal state change what a mind notices and remembers?

The hypothesis is that emotion shapes cognition by changing what becomes salient, which memories are accessible, and which actions a system considers. Recent experience could affect perception temporarily, before reasoning; repeated experience might produce a more lasting disposition.

Sophia implements a persistent persona diary, and separate experiments apply and update an internal-state matrix over embeddings. Connecting the diary, retention across timescales, and these transforms into useful changes in continuing behavior remains the next question.

Embodiment and action

What changes when a learner can act?

I treat embodiment as central because acting lets a system test an expectation against a consequence. It does something, the world changes, and the outcome provides evidence for revising what it perceived, remembered, or expected.

Talos provides the sensor and actuator connection within LOGOS. The current Sophia inhabitant uses scripted actions, so it establishes a connection to a body without yet answering the learning question. Bringing acquired representations into an adaptive perception–action loop remains a direction for the work.

Continuity and cumulative learning

What makes learning accumulate?

Interruptions, new tasks, and new generations test what a system can carry forward. Keeping a history preserves earlier work; the stronger test is whether that history changes subsequent decisions and capabilities.

Cliste’s continuing-life experiments preserve acquired visual memory, working content, and intake position across new experience and restarts. That establishes state continuity; the stronger goal is learning that improves later use without destroying earlier competence. Scion’s inheritance studies and the memory and continuity tools approach related parts of that question.

Cognition and consciousness

How do these processes become a coherent mind?

The larger question is how perception, memory, attention, action, and a system’s understanding of itself fit together over time. Their interaction matters: a recalled experience could change what the system attends to, which action it chooses, and what it learns next.

Cliste is the current effort to bring these processes together, with the intention that she becomes Sophia. The human brain guides the questions about organization, learning, and economy. The present work concerns cognition and intelligence. Consciousness remains an open background question, with no experiment here that establishes it in these systems.

Systems and experiments

I spent a long time investigating knowledge graphs before research led me to vector symbolic architectures. Cliste now develops that direction. She will eventually become Sophia; compatibility with Sophia’s old graph implementation does not constrain what she can become. The wider work preserves useful questions about embodiment, language, interaction, and learning, along with evidence of approaches that fell short.

Cliste

Can a continuing mind perceive, remember, and compose experience in vectors?

My current effort to model machine cognition on the way human brains perceive, remember, relate experiences, and learn. Cliste is the research effort I intend to grow into Sophia. The current visual path composes perceptual content with spatial and temporal context in hyperdimensional VSA memory, without captions or text queries.

LOGOS / Sophia

How can perception, memory, disposition, and action develop into one continuing individual?

LOGOS is the larger effort to build Sophia: a continuing individual whose experience shapes what she knows, notices, and does. The implementation includes a persona diary, graph memory and maintenance, language and inspection services, and separate affect experiments. Its memory design spans temporary state, revisitable experience, and lasting knowledge. Cliste is now developing the cognitive substrate around which these roles can change.

TinyMind / Saoirse

Can an agent learn which questions and actions are worth pursuing?

TinyMind and its continuing agent, Saoirse, connect persistent graph memory to curiosity, attention, a spending budget, and recorded outcomes. The work has moved from accumulating relations toward measuring whether an investigation reduced the gap that prompted it, and whether those outcomes should change what the agent chooses next.

Tabula Rasa

Can relations emerge from experience before they have names?

A continuing VSA workbench connects perception, acquired knowledge, conversation, and persistent concerns. Observing, recalling, comparing, and composing remembered content can contribute to the same unfinished work. Later axis and visual-association experiments investigate how more of the structure can be acquired from experience.

genetic_hackathon

Can a discovered program become a useful building block for the next problem?

An evolutionary workbench for mathematical expressions and first-order logic. Discoveries become callable functions or checked simplifications that can change later search and revise earlier answers. Controlled studies test when this accumulated library helps, and where fitting examples still falls short of generality.

Scion

Can an agent pass on working methods that help its successor?

Controlled studies of cumulative agent improvement. Scion carries code, proofs, tools, instructions, notes, and unfinished work between generations, then compares the successor with a fresh equal-budget agent. The question is what inheritance changes on the next task.

JEPA → CLIP

Can a learned bridge make video representations useful for language retrieval?

A sequence of experiments mapping V-JEPA video features into CLIP-associated representations. Early failures led to changes in pooling, loss functions, target construction, and model selection; later runs recorded useful retrieval. The remaining question is which perceptual information the bridge preserves, and how well that usefulness survives beyond the development comparisons.

Tools that grew out of the work

Harness

How can agent work be continued, checked, and improved across models?

An agent runtime with durable sessions, coordinated execution, recorded task evidence, and supervised improvement experiments.

agent-swarm

Coordinating agents and inspecting their work

A shared tool router, workflow engine, and telemetry system for coding agents. It coordinates workers and dependencies, applies permissions at the point of tool use, manages large responses, and records enough of the process to examine how a run reached its result.