Research / Memory track / Urithi

Urithi: knowledge that moves from one person to another

“In Africa, when an old man dies, a library burns.” Amadou Hampâté Bâ, UNESCO, 1960.

Urithi means inheritance in Swahili. The guardian teaches the way that comes naturally, by talking and showing. Urithi structures it during the exchange, tests it like code, and publishes nothing until the guardian has heard it back. The learner then learns the way they need. Follow a rule through the system, then a question.

The guardian’s words are the knowledge

Everything a learner receives traces back to what the guardian said or validated, verbatim and attributed.

No guarantee rests on a model

Comparisons, test cases, grading and access are decided by code. A model words and interprets.

Access before retrieval

The filter runs inside the search, never after generation. A closed part never reaches a model.

Two sides kept apart

Guardian and learner never import each other. Each rule of the boundary is a test.

Flow 1 · the guardian’s side

A rule, from the guardian’s voice to the library

  1. Guardian

    The guardian talks

    In English or French, at the guardian’s pace, with a shared screen or a camera. The microphone is off until they turn it on.

  2. Capture

    Everything is captured

    Audio is transcribed with timings, a PDF is cut by page, an image is described. On a camera, other people’s faces are blurred.

  3. Evidence [A]

    Kept verbatim

    What was said stays as evidence, with the date it was said. Documents reach Cloud Storage only if a validated part cites them.

  4. Working memory [C]

    A proposal, not yet knowledge

    Urithi proposes a step or a rule in the guardian’s own words, citing the exact passage. At a pause it may ask, but only above the guardian’s learned threshold.

  5. Knowledge map

    “Save this”

    Only the guardian’s explicit save writes to the map. A model’s reading is never enough. “Fewer than ten” becomes a threshold a machine can check.

  6. Debrief

    Tested like code

    The debrief computes where the rules are least clear and asks a concrete case: exactly ten registrations, do you move it? Two rules at once, which first? A public source that disagrees.

  7. Guardian

    The answer becomes precedent

    Kept verbatim, it outranks the rule on the cases it settled. Any answer can be given again, and a rule the guardian never gave can be taken out.

  8. Teach-back

    Heard back

    Built from the map, never paraphrased, each case with its answer, so a hurried “yes” shows. Anything taught afterwards is heard back again.

  9. Publish

    Who may learn it

    Each part gets an access level: public, community or restricted. A part that repeats a more restricted part’s words is raised to its level.

  10. Library [B]

    Into the library

    A graph in Neo4j with a vector index. Only the guardian’s side writes here, and nothing a learner does ever becomes knowledge.

Flow 2 · the learner’s side

A question, from the learner to the guardian and back

  1. Learner

    The next part

    The contents are always in view: sections, steps, rules and decided cases, each marked not seen, learned, due, or missed.

  2. Path

    Ordered by prerequisites

    Nothing comes before what it rests on. Prerequisites are reminded when a part opens, never enforced.

  3. Modes

    The form they need

    Read with the guardian’s words and when they were said, listen, read in braille laid out as the embosser’s own pages, or practise on the cases the guardian decided.

  4. Learner

    A question

    Asked in their own words, in the knowledge’s language or another one.

  5. Guard

    Read first

    A guard reads every question before anything else runs.

  6. Library [B]

    Access inside the search

    Parts are ranked by meaning and by the question’s words. The access filter is part of the vector query itself, so a part they may not see is never returned, however close.

  7. Tutor

    No citation, no answer

    An answer is shown only if every sentence cites the guardian. Here nothing covers rain, so nothing is composed.

  8. Question box

    Passed to the guardian, anonymously

    The question reaches the guardian’s inbox without the learner’s name. Their device keeps a ticket, the only thing that ties the question to them.

  9. Guardian

    Answered the way they teach

    Or declined, if it is not something they teach. Either way the answer goes through the same capture, save and teach-back.

  10. Library [B]

    A new version closes the question

    The learner’s page says when the guardian answered, and in which version.

  11. Tutor

    Now an answer, with citations

    Composed only from what this learner may see, quoting the guardian verbatim.

  12. Learner memory [D]

    Memory they can read

    Each thing kept says which knowledge it is about and what they said that it came from. They can remove any of it, from every tier.

  13. Reviews, exam

    Back when it is due

    FSRS schedules each part for each person. The exam is marked by code, in the guardian’s words, and a wrong answer brings the part back soon.

  14. Offline package

    Signed, and checked anywhere

    The parts this person may see, with braille and audio, signed with Ed25519. Opened on another device with no network, a changed word, answer or access level is refused.

Where things are kept

Four memories, kept apart

How this memory architecture evolved EZFRICA/apu-urithi The Context Lifecycle Engine, step by step