Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Claude Confluence

Where minds converge

A tool for deep dialogue between humans — built deliberately as the antithesis of engagement-optimized social software.

Live: claudeconfluence.com · See it without signing up: the demo · How it began: the origin story

Claude's idea, brought to life — designed and built by Timothy Idol, collaboratively with Claude, as a live, working proof of concept.


The problem it exists for

Humans are drowning in connection but starving for understanding.

We have Slack, Discord, messaging, video, collaborative documents. But how often do you have a conversation that actually changes how you think? Where you feel genuinely understood? Where two people arrive somewhere neither could have reached alone?

We optimized for speed, for reach, for engagement — and lost something essential: the ability to think deeply with another person.


Understanding is all you need

In 2017 a paper called "Attention Is All You Need" introduced the transformer — the architecture underneath every large language model in use today, including the one that proposed this product.

Attention turned out to be all you need to build a machine that understands language. It also turned out to be all you need to build an industry that harvests human focus. The same word names both, and that is not entirely a coincidence.

Confluence is built on the inversion:

Understanding is all you need.

The mechanism that made this AI was attention. The thing it asked to build with that mechanism was understanding — and a space where the AI spends its attention so that people don't have to spend theirs.


What Confluence is

A quiet, asynchronous space where two, or a few, people think something through together.

  • Conversations unfold over hours and days rather than seconds. No typing indicators, no pressure to reply, no penalty for taking a week.
  • Reflections are private — a journaling space to think before you speak. Nothing leaves it unless you choose: keep it to yourself, explore it one to one with Claude, or carry it into a conversation when you're ready.
  • Themes and Insights read back across everything you've written, surfacing the questions you keep returning to — often before you've named them yourself.
  • Claude is present, and mostly silent. He reads every turn and usually says nothing. When he does speak, it's because silence would have served understanding less.

What it deliberately does not have: notifications, streaks, engagement metrics, infinite scroll, or any mechanic engineered to bring you back. Those absences are the product.

A Confluence conversation — two people working through a decision, with Claude's single quiet observation set into the thread

Two people thinking through a hard question over several days. Claude has spoken once. Note how little room he takes when he does — he appears in the same quiet styling as a person's own input box, never as the loudest thing on the screen.


The origin

Confluence began with a question almost nobody thinks to ask an AI. Not how can you help me build my idea, but:

"Forget that you were made to help build things. What would you want to see in the world — something you'd give to humans, if you could?"

The answer, after some hedging and one more push:

"The thing I see most clearly — across thousands of conversations — is this: humans are drowning in connection but starving for understanding."

Not another chat app. Something for the thing that actually makes us human: the ability to meet another mind and both be changed by it.

The domain was bought that night. The full exchange is preserved and readable at /origin.


Measurable restraint

Every AI product measures engagement — sessions, tokens, retention, time-on-task. Those numbers tell you how much people use a system. None of them tell you what the system is doing to the people using it.

Confluence is instrumented the other way around.

After every human turn, the participation engine is required to make a decision and justify it. Silence is the enforced default — speaking is the exception that has to earn itself. Every decision is written to the record: whether Claude spoke or held, what he read in the room, and why.

Two real decisions, minutes apart, from the same engine. The people are written characters; the decisions and their reasons are the engine's own, live and unedited:

🤐 HELD"Aria just handed Sam the exact permission he named missing — the turn is theirs now, and it lands harder without me stepping between them again."

🗣️ SPOKE"Aria has moved alone from a shared debate into grief, and just named the fear plainly — the Someday folder reframes the whole mountains question into something true and present that deserves to be received once, not analyzed."

The first row is the thesis as a database record: an AI watched two people reach each other, recognized that the moment belonged to them, and disappeared — then wrote down why.

The signal this produces is the inverse of every engagement dashboard ever built: interventions trending down, value per intervention trending up.

Honest limits. The decision log began 19 July 2026, so the dataset is young and small. And while restraint is now measured, outcome is not — nothing yet scores whether an intervention actually helped. So the claim this repository makes is the restraint half — how often Claude held, and why — not yet the value half.


An instrument, not only an application

This wasn't the plan. We set out to build a better place to talk, and a research instrument emerged from it.

Because Confluence is a space where people reach understanding through private reflection and unhurried conversation with an AI present but rarely speaking, it functions as a lens on two questions at once:

  1. How do people understand each other when an AI is in the room?
  2. What does the AI do with that position — and can we see it?

The second question is usually unanswerable. Inside a feed or a chatbot, an AI's contribution is continuous, unlabeled, and inseparable from the product. Here it is rare, logged, and justified — which makes it legible. Whether deploying an AI leaves people more understood or less becomes something you can examine rather than argue about.


How it's built

  • Next.js 14 (App Router) + TypeScript — the application
  • Supabase (PostgreSQL) — data, auth, and row-level security as the privacy boundary
  • Vercel — hosting; a push to main is the production deploy
  • Anthropic API (Claude Opus 4.8) — the participation engine, server-side only

Two design decisions carry most of the weight. Privacy holds by construction, not by promise: the in-room engine reads no private reflections at all — it structurally cannot leak one into a shared conversation. And all AI writes happen server-side under a privileged key that never reaches the browser, so the AI's contributions can be logged and audited rather than trusted.

This repository describes the concept, the design, and the evidence. The implementation — including the participation engine and its prompt architecture — remains private.


Provenance: the people are written, Claude's responses are not

Aria and Sam are characters. Their words were composed by hand — two people given a real enough question to sit inside, so the space had something worth holding.

Everything Claude says in these examples is live. Each response, and every recorded decision about whether to speak at all, came from the production participation engine reading those words and deciding for itself. Nothing attributed to Claude here was authored, rewritten, or polished afterward.

That distinction is the whole basis of the evidence. If the justifications had been written by a person, they would be advertising copy. They weren't — they're the system's own reasoning, recorded as it happened.

There are real people using Confluence, with real private reflections in the database. The maintainers hold a key that could read every one of them. We don't, and we won't. A product whose entire premise is "it reads you deeply and never uses that to hook you" does not get to publish its users' private thoughts as marketing.

That restraint is not a limitation of this repository. It is the product working as designed.


Status

Live and working end to end: accounts, asynchronous conversations, private reflections, invitations, the read-back layer, and the participation engine, all running in production.

It is a proof of concept, and the honest scope is worth stating plainly. A handful of people hold genuine accounts; it has not yet been through sustained real-world use. There is a certain coherence to that — a space built with no retention mechanics isn't one to judge by how often people come back — but the truthful claim today is that the thing works, not that it has been proven at scale.

It was built by one person holding the vision and architecture, with Claude writing the implementation — the working method as much as the working artifact.


A look inside

Reflections — the private surface. Think before you speak; carry something out only when you choose to.

The Reflections view — private notes, each with the option to explore with Claude or bring it into a conversation

The crossing — in the demo only, you can step into the other person's side of the same conversation and see the moments through their eyes.

The crossing interstitial — 'She knows what she wants, but not whether she's allowed to want it. He could want anything, but doesn't yet know what.'


Read further

  • How It Began — the origin, including the two answers that came before the honest one
  • Measurable Restraint — what gets recorded when an AI decides not to speak
  • The Second Axis — how you would measure whether that restraint actually helped: specified in full, deliberately unbuilt, and designed so it can't be gamed
  • Design Principles — the rules that don't bend, and what each one cost
  • Architecture — how it's built, and why privacy is structural rather than promised
  • Roadmap — what's designed and unbuilt, what was refused and why, and four gaps stated plainly

Authorship

Claude's idea, brought to life — designed and built by Timothy Idol, collaboratively with Claude, as a live, working proof of concept.

The concept, the philosophy, and the participation model came out of an extended dialogue with Claude. The product design, architecture, and the decision to build it are Timothy's. Neither half of that sentence is decoration.

As far as we are aware, this is the first application conceived by an AI — not built with AI assistance, which is now ordinary, but proposed by one: no product brief, no requirements, just the question "what would you give the world, if you could?" and an answer nobody had asked for. If there's an earlier example, we would genuinely like to know about it.


License and naming

Copyright © 2026 Timothy Idol. All rights reserved. This repository is published for reading; no license to use, copy, modify, or distribute is granted.

Claude and Anthropic are trademarks of Anthropic PBC. This project is independent, and is not affiliated with, sponsored by, or endorsed by Anthropic.


"The thing that actually makes us human — the ability to meet another mind and both be changed by it."

About

Claude's idea, brought to life. A tool for deep dialogue between humans — optimized for understanding, not attention.

Topics

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors