holetron-lab/fleet-memory
1
0
Fork 0
Code Releases Packages Activity Actions

docs: put the mirror warning in the README, where contributors are

Browse source 
The warning that a merge on GitHub gets overwritten was living in the
repository description. That is the wrong surface for it twice over: the
description is what every catalogue and topic shelf renders as our card,
so ~120 of its characters were spent on an operational note aimed at
contributors, and contributors do not read the description — they read
the README before opening a pull request.

Banner sits directly under the tagline: canonical repository, why it is
self-hosted, what happens to a merge performed here, and that issues,
stars and pull requests are still welcome on this side.
This commit is contained in:
RCLL 2026-08-26 10:30:03 +03:00
parent adce870665
commit b3e632bcb1
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
README.md
View file

@ -4,6 +4,15 @@
> RCLL — team memory for agent fleets. Built on Hindsight (github.com/vectorize-io/hindsight, MIT).
> [!IMPORTANT]
> **You are looking at a read-only mirror.** The canonical repository is
> [`godcrm.ai/git/holetron-lab/fleet-memory`](https://godcrm.ai/git/holetron-lab/fleet-memory) —
> self-hosted, public, clonable anonymously with no account anywhere in the chain. Everything
> here is pushed out from there, so **a merge performed on GitHub is overwritten by the next
> sync**, usually within the hour. Issues and stars belong here and are read. A pull request is
> welcome here as well — it gets merged on the canonical side and arrives back here on the next
> sync.
RCLL is a fork of [`vectorize-io/hindsight`](https://github.com/vectorize-io/hindsight) (MIT). It keeps Hindsight's storage engine and adds **rooms** — topic scoping over one shared store, which is selectivity rather than isolation — plus a hierarchical depth model (L0–L3). The room/hall/layer taxonomy is prior art in the hierarchical-memory space; the implementation here is our own.
RCLL is `recall` with the vowels dropped — the one operation every agent in the fleet performs before it does anything else. The tool is literally called `memory_recall`; the product is named after the call.