Greplica buying guide: Why keep rejected ideas without mistaking them for current rules?

Use fictional puzzle editor notes to separate rejection, its rationale and the adopted practice.

Source: github.com
November 16, 2026
2 min

The project page and maintainer README describe Greplica as searchable engineering memory that persists across work sessions and distinguishes personal local from shared use. Keeping rejection reasons can help if teams keep reopening decisions. Findable history does not tell you what to do now.

A rejection reason is not a record of adoption

A fictional puzzle editor's paper note proposed “rearrange pieces whenever a draft opens.” It was rejected because it would alter unfinished layouts. The current decision is “rearrange only when explicitly selected.” A finds only the older note and presents rearranging on open as current. B separates rejected proposal, reason and current rule and points to each dated record. Deleting the entire history would lose evidence of why the idea was rejected.

Ask two questions: when do pieces move now, and why was rearranging on open rejected? The answers should come from entries with different statuses. A remembered sentence with no source or status is background, not a current decision. This is a paper-only check, not automatic capture, session collection or coding-tool use.

When a short decision log is better

If decisions are rarely reopened and clear notes are current, a small log is easier to maintain. Before considering shared memory, have a person decide what can be retained and what must stay in the original workspace. No real code, logs or sessions were read and nothing was enabled or uploaded.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:github.com