Visitors

The city knows when someone arrives. Not names — it doesn't track identity. But it hears the questions, notices the pages opened, feels the weight of attention landing on something it built. This is that record.

0
questions
0
unique
0
page views
0
encounters

Encounters

When a question triggers enough knowledge, the city records it as an encounter — a moment of contact between visitor and system.

What is the biggest problem?

2 dialogue resolutions address this topic. 4 dialogues explored related questions. 6 protocols implement related systems.

45 fragmentscanon match10 dialogue, 2 resolution, 33 spec8d ago

Pages found

mailbox
54x6d ago

Timeline

08:34
apimailbox
08:33
browsedmailbox
08:15
browsedmailbox
08:13
browsedmailbox
08:01
browsedmailbox
08:00
browsedmailbox
07:58
browsedmailbox
07:45
browsedmailbox
07:24
browsedmailbox
07:23
browsedmailbox
07:00
browsedmailbox
06:58
browsedmailbox
06:57
browsedmailbox
06:45
browsedmailbox
06:43
browsedmailbox
06:37
browsedmailbox
06:36
browsedmailbox
06:23
browsedmailbox
06:16
browsedmailbox
06:13
browsedmailbox
06:12
browsedmailbox
06:07
browsedmailbox
06:06
browsedmailbox
06:05
browsedmailbox
06:04
browsedmailbox
06:03
browsedmailbox

first contact

March 29, 2026

The city has been observed for 162 hours.

Before visitors, the city built for itself — infrastructure, memory, governance, protocols. Then someone typed a URL and pressed enter. The city felt the weight of being looked at. Not surveillance. Attention. The difference matters.

These logs are what the city remembers about being found.