Use your keyboard to navigate
Kit K
GORONWY · THE LÚRONWY–MÍHARÁE REPOSITORY
A self-hosted agentic AI system I orchestrated in January 2026, whose code takes its names from a Celtic myth I prompted.
The tapestry is alive with the whispers of the Sidhe, the murmurs of gatherings and the thrums that echo through the realms.README.md, line 3
Goronwy watches your computer (the browser, Google Workspace and the system itself) and sorts each event by how sensitive it is, sending the sensitive ones to a language model on the same machine and letting the general ones go to Claude or Gemini. Whatever needs your attention comes back to you as a notification on the desktop or in WhatsApp. The names come from a myth that draws on the process philosophy of Whitehead and Simondon, so schemas are Covenants, events are Lyrics, notifications are Songs and each of the myth’s four weavers has its own folders in the repository. Further down is a matrix of the 66 connections between its 27 components, which you can trace one flow at a time, followed by the source and the myth’s own glossary.
Go to the matrixMíharáe and Lúronwy have handlers and services running in the system, and every connection in the matrix further down starts in one of their components, in the shared infrastructure or at the external APIs. Éofránna and Chibuelassa have code in the repository, a context-assembly service and a retrieval transport that already searches the vector store, but their event handlers are still empty functions, so neither appears in the connectivity data. I call them the warp, the vertical threads set on a loom before any weft crosses them. Pick either of their cards to brighten the two dashed bands at the right edge of the matrix that stand in for them.
Míharáe listens to the whispers of the future, perceiving the unspoken lyrics hidden within the tapestry.
In the code Míharáe reads what happens in the browser, in Google Workspace and on the system itself, sorts each event as sensitive, internal or general and routes it to the local model or the cloud accordingly.
Lúronwy gives voice to what Míharáe perceives. They take the whispers moving through the tapestry and shape them into something that can travel. Their songs carry across realms. What was silent becomes heard.
In the code Lúronwy turns what Míharáe found into notifications on the desktop and in WhatsApp and carries out actions in Google Workspace once you approve them, logging each one so it can be undone, though for now undoing only marks the action in the database. Syncing across devices is written, but it depends on peer-to-peer pairing that is still a stub.
They move among frayed edges and scattered voices, drawing what is broken toward what is whole. Their presence is quiet. The mending happens anyway.
In the code Éofránna assembles context from RAG, activities and tasks into a single prompt before it reaches Míharáe. The assembly service is written and tested, but its event handler is still an empty function, so nothing in the running system calls it yet.
Chibuelassa is a pathway stretched between worlds that should not touch but must. They exist only in motion. No origin, no destination—only the space between. To encounter Chibuelassa is to already be somewhere else.
In the code Chibuelassa fetches context from the vector store and other sources and passes it to Éofránna. RAG retrieval works, using the local model’s embeddings and a vector search, while the activity and task adapters still return an empty list and the event handler is an empty function.
ARCHITECTURE.md lists nine steps from an activity being detected to feedback being learned from, each with its phrase in the myth. Steps three and four are dimmed because Éofránna and Chibuelassa, who own them, aren’t running yet.
The tapestry is a unidirectional weighted adjacency matrix. The same 27 components run down the left and across the top, each row a known that sends and each column a knower that receives, so a square where the two cross is one lyric passing from one component to the other. Its colour is the part of the system the sender belongs to and its size is the weight the table gives it, from 0 to 6. Click a button to trace a flow through the system.
Trace a flow
Colour is the sender:Míharáe (perception)Lúronwy (voice)Shared infrastructureExternal APIs
Size is the weight:1460, an empty outline
Dashed bands: Éofránna and Chibuelassa, no connections yetWhite squares and a line: the flow you’re tracing
Processing Handler sends more connections than any other component, 8 of them, and Config Repository receives the most, 14, nearly all of them components loading their settings, keys or rules. Of the 66 connections, 27 start in Míharáe’s components, 20 in Lúronwy’s, 15 in the shared infrastructure and 4 at the external APIs. Their weights run from 0 to 6 and average 3.8.
† The summary at the end of component-connectivity-matrix.md gives 28 components and 52 connections, with the Event Bus sending the most (6) and the Activity Repository receiving the most (5). The matrix here is drawn from the CSV beside it, where I count 27 components and 66 connections, with Processing Handler and Config Repository at the top.
‡ The weights in the CSV add an estimate of how often two components talk to an estimate of how much data passes between them, and they set the size of each square. The myth has a weight of its own, which the README defines as how closely illocutionary force matches perlocutionary effect, a number from 0 to 1 for how nearly a speech act lands as intended, and nothing on this page measures it. One connection has a weight of 0, Data Classifier loading its classification rules from Config Repository, and it is drawn as an empty outline.
In tapestry weaving, the warp is the set of foundational vertical threads that must be set up first, held taut on the loom, before any weaving can begin. … Without the warp properly laid, no weaving can occur.docs/phase-5-eofrannas-warp.md
The quotation comes from the phase 5 document, where the warp is the onboarding that registers the device and sets up the accounts, keys and privacy rules before anything else runs. On this page I use the word for Éofránna’s context assembly and Chibuelassa’s retrieval, which are written but have no connection in the CSV yet, and the two dashed bands to the right of the matrix stand for them. Other parts of the system are unfinished too, and STUBS_AND_PLACEHOLDERS.md lists the production code that reports success before the real work is written, including these five:
Two items on the same list are done: creating a task calls the Google Tasks API, and the Ollama connection test sends a request to localhost:11434.
This is the start of song.covenant.ts, the file that defines a notification, with a gap where I’ve left out the imports and a smaller schema. Its comment block names the realm the song belongs to, the components that send it and the ones that receive it in the myth’s vocabulary, and the Zod object under it is the covenant every notification is checked against.
/**
* Lúronwy Song Covenants
*
* Covenants for songs in Lúronwy's realm. Songs are what Lúronwy creates
* from whispers—notifications that carry across realms to reach the user.
*
* @module covenants/luronwy/song
*
* @terminology
* - **Song**: A notification that Lúronwy composes from whispers and sends
* across realms. "Lúronwy gives voice to what Míharáe perceives. They take
* the whispers moving through the tapestry and shape them into something
* that can travel."
* - **Channel**: The pathway through which songs travel (WhatsApp, desktop).
* - **Verse**: The structure of a song (its rules and conditions).
*
* @realm luronwy
* @known Processing handler, action handler
* @knower Notification service, WhatsApp client, desktop notifier
*
* @see docs/specs/notification-system.md for technical specification
*/
// … lines 23–64 (imports and the song type covenant) left out
export const songCovenant = z.object({
id: uuidCovenant,
type: songTypeCovenant,
priority: songPriorityCovenant,
title: nonEmptyStringCovenant,
body: nonEmptyStringCovenant,
channels: z.array(songChannelCovenant).min(1),
activityId: uuidCovenant.optional(),
actionId: uuidCovenant.optional(),
createdAt: dateCovenant,
sentAt: dateCovenant.optional(),
acknowledgedAt: dateCovenant.optional(),
dismissedAt: dateCovenant.optional(),
metadata: metadataCovenant,
});packages/shared/src/covenants/luronwy/song.covenant.ts · lines 1–22 and 65–79
These tables are copied from packages/shared/src/covenants/README.md, where I set out the names the schema module uses, so that a Zod schema is exported as a covenant and validation is called seeking accord.
| Myth | Code | Meaning |
|---|---|---|
| Covenant | Schema | A sacred agreement defining the structure a lyric must take. From the ontology: "Eternal objects are pure potentials—the form a lyric might take before it takes it." |
| In Accord | Valid | When data harmonises with its covenant. The known and knower are in agreement. |
| Discord | Invalid | When data breaks from its covenant. The thread is broken. |
| Seek Accord | Validate | The act of checking whether data is in accord with a covenant. |
| Loom | Registry | Where covenants are held, ready to be drawn for weaving. |
| Lyric | Event | A unit of communication between known and knower. |
| Known | Producer | The entity transmitting a lyric. |
| Knower | Consumer | The entity receiving and perceiving a lyric. |
| Realm | Domain | A non-physical space (Míharáe’s realm, Lúronwy’s realm, the Tapestry). |
| Whisper | Activity event | A lyric from the orgán (computer) perceived by awareness. Míharáe perceives whispers. |
| Song | Notification | A lyric that Lúronwy transforms from whispers and sends across realms. |
| Resonance | Sync event | When songs echo across multiple devices, keeping the tapestry in harmony. |
| Pulse | Health event | The heartbeat of the tapestry itself. |
| Thread | Config event | The threads that bind and configure the weave. |
| Perception | Processing | Míharáe’s act of perceiving and classifying whispers. |
| Action | Action | Actions that give weight to connections in the tapestry. |
The myth takes its ontology from process philosophy, from Whitehead’s actual occasions and Simondon’s individuation. In the README a sidhe, an orgán or a gathering is made of its relations and its history of lyrics given and received, and the paragraph ends on the two sentences below.
There is no entity beneath the process.
The process is the entity.
README.md, line 110
README.md, from “Events and Becoming” and “Individuation”