diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-12 14:58:13 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-12 14:58:13 +0000 |
| commit | 7a78dce4bf6db058f1ac12a4176c2702debff798 (patch) | |
| tree | e54924b1881fd0850ea51a4b43f75cdc6eaeb07c /test/python/test_openapi.py | |
| parent | d507d3220910f528d95932f7772f80a902ec6fe9 (diff) | |
| download | genenetwork4-7a78dce4bf6db058f1ac12a4176c2702debff798.tar.gz | |
docs: say that project memory is how a session recovers, and where it lives
The ai-memory store already existed; what was missing was any mention that a reader should use it before starting work, and what they would find. Two concrete things a cold reader needs and cannot reconstruct from a diff: an operational RUNBOOK entry (the Slurm container from gn-machines, its fixed JWT, the environment /compute/gemma/ravanan needs, the four prerequisites that bit the first time, and the fastest test: one chromosome, 14 s), and the "why is this like this" entries behind endpoints that exist because something else was wrong (-pve reporting, the next-link graph, the reference-genome linkage). docs/www/SKILL.md gains section 7a with the three query forms, the topic names that exist (ravanan-slurm, reference-genomes, gemma-pve) and both measured costs; README gains the same note under Development, since that is where a maintainer looks first. States the limit honestly: the store is local, gitignored and per repository -- it survives a cleared session, not a lost machine, which is why every conclusion is also in a commit message and in these docs.
Diffstat (limited to 'test/python/test_openapi.py')
0 files changed, 0 insertions, 0 deletions
