GeniffyDocs
Changelog Log In Get a key

How the brain works

What you add becomes sources. Geniffy reads them into facts, and into what a person keeps about their work: where each project stands, what was promised, what happened and the lessons. What comes back reads only from those, and anything can be taken out again.

You add sources; Geniffy keeps facts

What you add is a source: a note, a web page, a file (PDF, Word, PowerPoint, Excel or text), or a conversation. Geniffy reads it and keeps each fact in it as its own memory, with the source it came from:

"Priya Nair signs the Lumen renewal, and it comes up in March. She prefers WhatsApp to email."

becomes three memories:

  • Priya Nair signs the Lumen renewal.
  • The Lumen renewal comes up in March 2027.
  • Priya Nair prefers WhatsApp to email.

Reading takes a few seconds. sources.wait(id) holds until it is done; until then the source says it is still reading.

What it does while reading

  • Dates mean what was meant. "Comes up in March", added in October, is kept as March 2027, and "tomorrow" is the next day where the person is. See How dates are read.
  • People stay people. In a conversation, what the user says becomes facts about the user, not about your assistant. System and developer messages are skipped.
  • Each memory has a kind: people, plans and dates, preferences, or details. You can filter by kind when you list, search or build context.
  • What changes is kept as history. When a later source changes something, the newer word serves and the older one is kept as its history, so you can see what changed and when. The one said later wins, whatever order the sources arrive in. When two sources disagree and neither says it changed the other (two people give two dates), both are kept and served as a clash, never chosen between silently. See When something changes or ends.
  • Secrets are not kept. Passwords, tokens, card numbers and Aadhaar numbers in what you add are redacted: a memory can say one was mentioned, never what it was. The same goes for a question.

How dates are read

Every date Geniffy keeps is worked out from the words that were said, by code, on the clock of the person who said them. The model that reads a source copies the words ("next month", "on Friday", "by the end of Q1"); it never works out a date itself.

Said When Kept as
"Our renewal is on 12 March" 1 October 2026 12 March 2027
"We first met on 12 March" 1 October 2026 12 March 2026
"The launch moved to next month" 31 January 2026 February 2026
"We signed last month" 31 October 2026 September 2026
"Let's do the demo next Friday" Wednesday 28 October 2026 Friday 6 November 2026
"I'll send the deck in two weeks" 29 October 2026 about 12 November 2026
"Payment by the end of the month" 20 October 2026 31 October 2026 at the latest
"The proposal by the end of Q1" 2 November 2026 31 March 2027 at the latest
"I'll send the quote tomorrow" 22:30 on 1 November in Los Angeles 2 November 2026
  • A day or a month with no year is the next one when it is still to come, and the last one when it happened. A birthday or an anniversary is kept as a day every year.
  • The words stay, and the date is added. "The launch moved to next month" is kept as "The launch moved to next month (November 2026)", so it still reads right a year later.
  • Dates are local to the person. Send timezone with a save (America/Los_Angeles, or an offset such as +05:30), or a said_at or message time with its offset. Set a user's zone once with PUT /v1/timezone and everything they say is read on it. With none of these, UTC.
  • A date written in numbers (11/12) is read the way the person's zone writes dates: month first in the US, day first elsewhere, or as date_order says. The memory says how it was read.
  • What comes back says which date is which. A memory's said_at is when it was said and date is the day it is about. A promise's at is its day (2026-10-31), or its time with its offset when one was said; due says it in words and overdue is true once the day has gone by where the person is.

Memories and promises saved before 3 November 2026 are dated again, once, the first time their memory is read.

When something changes or ends

A later word can change what Geniffy holds in three ways, and each applies to everything it holds, not only facts: the lessons and rules it learned, the promises still open, and where each project stands.

A later word says What happens Example
It has a new value The new one serves, the old one is kept as what it was before "The launch moved to 17 December"
It stopped It is no longer served, and is kept with when it ended and what said so "Priya's admin access was removed", "the formal English rule no longer applies"
It was done A promise or an open question is closed "Omar sent the signed contract"
  • The word said later decides, whatever order the sources arrive in. An old email saying access was removed, imported after access was given again, ends nothing.
  • A hedge or a rumour changes nothing. "I heard Priya might lose her access" leaves her access as it is. So does a word about another system, another account or another project.
  • An end still to come is kept as one. "Her access ends on 20 November" leaves the access current until then, and it is not served after it.
  • Nothing is deleted. What ended is kept with when it ended and what said so: an export lists it as ended, and one memory comes back with its history. Deleting the source that ended something, or marking that word wrong, brings it back.

An agent that holds a briefing through a long session can ask what changed since: GET /v1/changes with since set to the briefing's cursor lists each memory, rule, promise or line of where things stand that changed, with what it was, what it is now and the words that changed it.

The rest of the brain

Facts are one part. From the same sources, conversations and whole agent sessions above all, Geniffy keeps:

Part What it holds Read it with
Where things stand Each project's status, its next steps in the order they were said, what is still open, and what was decided and why now()
Promises What someone said they would do, and by when; each can be marked done intentions()
What happened Each stretch of work as a story: what was tried, what failed, what worked, tool steps included episodes()
Lessons What worked and what didn't, so it isn't repeated lessons()

Every night

While nobody is waiting, Geniffy goes over what it learned that day:

  • It settles what disagrees. Two things that can't both be true are read side by side. The newer and better sourced one serves, each change keeps its reason, and any of them can be put back. One it can't settle waits for the person.
  • It merges what it learned. Lessons that say the same thing become one.
  • It tests itself. A short self-check of what it holds gives the memory health shown in the app.

What comes back

The briefing reads where things stand and what comes next, what happened last time, what is due, the lessons that apply, what happened before and then the facts, in one call and without a model, so it comes back at once. A session opened in the minute after the last one stopped also gets the last words as they were said, before Geniffy has read them. context, ask and search read from the same parts, never from somewhere else. context and ask judge whether anything stored bears on the question, and say so in words when nothing does. See Recall.

Taking it out again

Everything is removable, at three sizes:

To remove Call What goes
One memory memories.delete(id) That fact
One source sources.delete(id) The source, and every memory only it taught
One user forget_space(space) Everything held for them

A memory that is wrong can also be corrected instead: memories.correct(id, text) says what is right, and the wrong version is kept as its history rather than used again. See Correct and forget.

Where it is kept

Geniffy stores memory in India. See Security and privacy. Your key reaches only your own memory and the spaces beneath it.

Last updated November 2, 2026