What your team works out should stay with your team.

One person's win becomes everyone's head start. Rema is evidence-grounded memory for engineering teams. It reads the tools your team already writes in, answers with the exact passage, and keeps what someone corrects so nobody solves the same problem twice.

Five reasons

  1. 1

    Your knowledge compounds, whichever model you use.

    Use whichever model you like, and switch when a better one ships. What Rema keeps about your work, what your team decided and why, stays with you and grows with every session. After a while, no model on its own knows your corner of the world the way yours does with it.

  2. 2

    Every answer shows where it came from.

    An answer is the exact passage with the file and the lines it came from, so anyone can open the source and check it. When a newer thread overrides an older answer, the newer one comes back with it.

  3. 3

    A correction is kept, not thrown away.

    When someone fixes an answer, the fix is stored with the evidence it came from, so the next person starts from it.

  4. 4

    It says what it did not read.

    A system that reads part of a file and reports on all of it is wrong in a way that looks careful, and reviewers rarely catch it. In Rema, a claim about every item has to rest on complete coverage, name its sample, or say how much it actually saw.

    The bug that taught this
  5. 5

    It stays yours.

    Rema runs on your machine with no API key, and its store stays there: Rema itself sends nothing anywhere. What it builds up about your work is yours, whichever model you point it at.

    What the install does

Two fair questions

Is this not just retrieval over our documents?
Retrieval is the easy half. The part that compounds is the record of what a person decided when the evidence was ambiguous, kept next to the evidence, which no index gives you on its own.
What if our documentation is bad?
It usually is. The decisions are rarely in the documentation; they are in pull requests, threads and tickets. Those are the sources.

Where it is today

The install is one command. The hosted console is in a closed pilot with a few early teams. It reads from Slack, GitHub, Jira, Confluence, Notion, Figma.