Context
Two repos under the "VeriSimDB" brand describe different products:
hyperpolymath/verisimiser — Rust CLI that augments any database with octad capabilities (drift, provenance, temporal, …)
hyperpolymath/verisimdb-data — git-backed flat-file storage for "panic-attack scan results and drift detection data"
A reader landing on either repo from a search result has no way to know:
- Whether the other repo is the same product or a different one
- Whether they need both
- Which is canonical
What to do
Add a short "Related repos" section to each README (after the title, before "What is this?"):
If the actual relationship is different from what's sketched above (which it may well be — see V-L1-J1), adjust accordingly. The goal is: a reader can answer "do these two repos belong together?" from the first paragraph of either README.
Acceptance
Context
Two repos under the "VeriSimDB" brand describe different products:
hyperpolymath/verisimiser— Rust CLI that augments any database with octad capabilities (drift, provenance, temporal, …)hyperpolymath/verisimdb-data— git-backed flat-file storage for "panic-attack scan results and drift detection data"A reader landing on either repo from a search result has no way to know:
What to do
Add a short "Related repos" section to each README (after the title, before "What is this?"):
In
verisimiser/README.adoc:In
verisimdb-data/README.adoc:If the actual relationship is different from what's sketched above (which it may well be — see V-L1-J1), adjust accordingly. The goal is: a reader can answer "do these two repos belong together?" from the first paragraph of either README.
Acceptance