Keep repository research honest

A saved repository is a lead, not an endorsement. Keep discovery, evaluation, use, and recommendation separate so a useful link cannot silently become an adoption claim.

One identity, several independent facts

Normalize the upstream owner and repository name, then assign a stable local record ID. Keep lifecycle stage, usage context, watching, recommendation, content status, public summary, and private notes as independent fields.

“Evaluating” does not mean adopted. “Watching” does not mean recommended. A draft summary does not mean approved for release.

Capture provenance without publishing the archive

Record the canonical upstream URL, source references, capture date, and content hash where useful. Merge repeated captures under one repository identity while retaining their references. Do not paste private screenshots, personal notes, credentials, employer material, or unverified claims into public copy.

Treat captured text as a lead. Before a time-sensitive public claim, check the primary repository or official documentation and record the version or date. A README can document intended capability; only an executed evaluation supports a local-behavior claim.

Evaluate with a fixed question

Define the use case before testing. Record the tested revision and environment, inputs and expected behavior, commands or review method, actual results and failure evidence, permissions and network access, and limitations.

Comparisons should use the same bounded task and criteria. Do not turn stars, screenshots, vendor benchmarks, or a successful install into a quality ranking.

Write the public summary

A useful summary answers what problem the project says it addresses, what was independently observed, and what remains unknown. Link the canonical source. Label documented capability, local observation, recommendation, and adoption explicitly.

When no evaluation ran, say so. “Research-next; not locally tested” is more useful than polished copy that blurs source claims with experience.

Minimum review gate

Before a record becomes public, confirm canonical identity, source link, public-safe wording, temporal claims, license relevance for the proposed use, and absence of private notes. Recommendation and adoption require their own evidence and owner decision.