About Nosce

Understanding someone means leaving room for them to say: that isn't me.

Nosce began with one unusually useful AI conversation. It is now an attempt to make that kind of self-understanding longitudinal, source-grounded, and correctable by design.

01

Why it began

One conversation connected experiences I had treated as separate problems.

For years I described myself as a low-energy person. Sleep, work, relationships, pressure, and choice all seemed to affect me, but I treated them as unrelated issues.

Then one long AI conversation placed those experiences beside one another. The answer was not perfect, and some claims were too confident. What mattered was that it organized something I had been living inside but had never seen as a whole.

02

What Nosce is building

The product is organized around an epistemic contract, not a persona.

Nosce connects experiences across time, forms a working understanding with visible sources, and lets the user correct what does not fit. New evidence can strengthen, limit, or overturn an earlier view.

The aim is not to simulate a person who always knows what to say. It is to build a system that can offer a meaningful connection without turning that connection into authority.

  • Direct when the evidence supports a connection.
  • Explicit about uncertainty and missing context.
  • Correctable at the level of the understanding itself.
  • Designed without streaks, guilt, or dependency-driven engagement.
03

Current stage

A real product, still under a strict seed validation gate.

The web product includes guided conversation, longitudinal memory, correctable understandings, an evolving portrait, Dreams, export, and deletion controls. Access remains invitation-only.

The central question is still being tested: after listening across time, can Nosce return one evidence-linked understanding that helps a user reframe something, survives correction, and becomes more useful rather than more confident?

04

Who is building it

Nosce is independently built by Rui.

I currently lead the product, engineering, AI behavior, and seed validation. I publish the reasoning behind important product boundaries because a tool for private expression should make its assumptions easier to examine.

I am also open to focused commercialization partnerships that can help Nosce test positioning, pricing, distribution, and willingness to pay without compromising its trust boundaries.

Want to understand Nosce a little better?

See how the product is being designed, or talk with Rui about how to take it to market.