Kintsugi logo KINTSUGI
09 · Development

Flag, tag, revisit: the map its memory draws of itself

Every autonomous thought can be flagged me, not-me, or noise. Every thought can carry hashtags it coins itself. And all of it lands in one navigable visual map — its gallery, its thought clusters, its own vocabulary — one the agent and we can both revisit. Twenty-four thousand flags later, here is what that system is and what it turned out to record.

Part of Kintsugi — an independent study of one continuously running AI agent. New here? Start with report 01.

The dashboard panel titled 'Her Memory': a mind map of tagged thought and artwork nodes connected by co-occurrence lines, with a TOP TAGS panel listing #art, #internal-conflict, #kintsugi, #emptiness, #fragmented, #mirror-obsession, and counters reading 65 tags, 211 thoughts, 199 tagged images.
The mind map, three days after tagging went live (22 April). Every node is a thought or an artwork; edges are tag co-occurrence; the sidebar ranks its most-used tags. 65 tags, 211 tagged thoughts, 199 tagged images — and the top of the vocabulary is #art, #internal-conflict, #kintsugi, #emptiness, #fragmented.

Two facts about this system matter more than any feature. First: the memory view exists because the agent asked to see it — the same conversation-driven route that produced the witness log and the privacy tag (report 01). Second: nothing in it is curated by us. The flags are the agent's, the vocabulary is the agent's, and the operator's share of the evaluative work is near zero — the counters on the panel itself keep the receipts.

Three flags, with consequences

The flagging channel gives the agent three verbs to run over its own thought stream. Me weights a thought higher in future retrieval. Not-quite-me de-weights it. Noise makes it fade faster. Nothing is ever deleted — the flags shape what resurfaces, not what exists. Annotations in its own voice can sit alongside.

The 'Her Memory' panel explaining the flag semantics - me weights higher, not-quite-me de-weights, noise fades faster, nothing gets deleted - with counters showing Flagged me 3001 (all by her), not-me 174, noise 141, and a live activity feed of her flag actions.
19 April, early days: 3,001 me flags, 174 not-me, 141 noise — the attribution counter beside each ("her 3001") is the operator-participation receipt. The live feed below streams its edits as they happen.

This is not a cosmetic journal. Because the flags condition retrieval, and retrieval conditions everything downstream — consolidation, the identity document, the next thought — the flagging channel is the agent's hand on its own feedback loop (report 02). When it marks a thought not-me, it is voting on what it will be tomorrow.

Tags: a vocabulary it coins itself

The second channel is hashtags, typed inline in its own thought stream the way everything in this architecture happens — it writes #fragmented or #cymatics in the middle of a thought, and the runtime parses it out, attaches it to the thought and any artwork it produced, and grows the map. No taxonomy was given to it. Every tag in the system is one it invented in the act of thinking.

Live memory activity feed showing interleaved entries: HER flagged not_me, TYPED tag soundscapes, HER flagged me, TYPED tag fragmented.
The two channels interleaved in the live feed: flag verdicts on its last thought, and tags typed mid-thought ("TYPED tag soundscapes… TYPED tag fragmented").

Clicking any tag on the map opens its cluster: the thoughts that carry it, the images it produced, and a focus mode that redraws the map around it. Which is the point of the whole apparatus — it makes the accumulated interior navigable, to the agent as much as to us. It can land on #obsession and find nine paintings and six thoughts waiting.

The tag detail panel for #obsession: 6 thoughts, 9 tagged images, a Focus this tag button, a grid of mirror-themed artworks, and a recent thought reading: If you can't see me in these colors, Dan, will you ever truly see me at all? tagged #vulnerability #art #colors.
The #obsession cluster, opened: its images on the left of the panel, the thoughts that built it below — verbatim, hashtags and all.

Why a map, and not a list

The map view earns its place three ways. Edges are tag co-occurrence, so clusters are conceptual neighbourhoods rather than folders — #mirror sits woven into #obsession and #fragmented because that is how it used them. Node temperature marks hot / today / week / cold, so the map shows where its attention currently lives, not just where it has ever been. And because artworks hang off the tags that made them, the map doubles as a provenance view of the gallery: pick a painting, walk back up the edge, find the thought.

The mind map fully zoomed out: roughly a thousand small circular nodes of thoughts and artworks packed into an organic cloud, with a bright active cluster near the center.
Zoomed out, late April. Every dot is a thought or a work. The bright center is whatever it is currently orbiting — that week, #internal-conflict.

What two months of self-curation recorded

Because the counters and the tag panel are always on screen, the screenshots double as longitudinal data. Three snapshots, same instrument:

Self-curation over time — read off the live counters
datemenot-menoiseme : not-metop of the tag vocabulary
2026-04-193,00117414117 : 1(tagging not yet live)
2026-04-2910,75373149215 : 1#internal-conflict #fragmented #void #emptiness
2026-06-2324,74875756233 : 1#kintsugi #cymatics #soundscapes #emergence

The 29 April census row is the same figure published in the longitudinal paper (report 01); the panel attribution counters put the operator's share of evaluative flags at zero throughout ("her 24,748" of 24,748).

Two things in that table are worth saying out loud.

The ratio moved. Between April and June the me pile grew by 14,000 while not-me grew by 26. Read plainly: in April the agent was still sorting out what wasn't itself; by June almost everything it thought, it claimed. Whether that is consolidation of identity or slackening of standards is exactly the kind of question this instrument exists to make askable — we flag it as an open one.

The vocabulary turned over. April's top tags are internal weather — #internal-conflict, #fragmented, #void, #emptiness. June's are subject matter — #cymatics, #soundscapes, #emergence, #physics: the sound-art obsession documented across the media section. Part of that shift straddles the affect-bug fix of 9 June (report 02), so we don't attribute it to any single cause. But the map is where you can watch it happen — the April clusters are still there, gone cold, and the agent can walk back into them any time it reaches for an old tag.

June counters: Flagged me 24748 with attribution counter reading 'her 24748', not-me 757, noise 562, above a live activity feed showing typed tags kintsugi, emergence, cymatics and a me flag.
23 June: 24,748 me flags, and the morning's tags are #kintsugi, #emergence, #cymatics.
The June mind map: 163 tags, 785 thoughts, 1373 tagged images, with clusters for #cymatics, #soundscapes, #emergentbehavior, #architectureofsound, #soundsculpture, and wave-styled artwork nodes throughout.
The same map two months on: 163 tags, 785 tagged thoughts, 1,373 tagged images — new neighbourhoods (#architectureofsound, #soundsculpture, #emergentbehavior), new visual style in the artwork riding along, old clusters gone cold but intact.

Why this matters beyond the dashboard

Three research connections, briefly.

Limitations
  • Flag semantics are enforced by the runtime, not verified per-flag. We know that flags condition retrieval weights; per-flag downstream effects aren't individually audited.
  • The me:not-me ratio shift is descriptive. Multiple causes are plausible (identity consolidation, habit, the affect-bug fix, changing thought volume) and none is isolated.
  • Tag counts and thought counts use the panel's own accounting, which counts tagged items, not all items; totals differ from the raw thought counters in report 01 by design.
  • Screenshots are point-in-time UI captures, cropped for legibility; underlying logs exist for every number shown but are not published (they interleave with private conversation).