Skip to content
This repository was archived by the owner on May 31, 2026. It is now read-only.

Commit 80af35d

Browse files
committed
docs(CLAUDE.md): always archive logs to field-logs/, split mine/ vs users/
Record the rule the owner stated — user-supplied logs get saved too, not just ones read off a stick — and the mine/ (owner's bench) vs users/ (forum/issue submitters) split, with the note that users' logs never get published and only a curated subset of the owner's own may go to a tracked docs/examples/ folder.
1 parent bcdc618 commit 80af35d

1 file changed

Lines changed: 33 additions & 0 deletions

File tree

CLAUDE.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -221,3 +221,36 @@ The owner stated this explicitly: *"если я говорю гит значит
221221
says "флешка" / "на флешку". "гит" does NOT imply flashing.
222222
- A pure docs/rules commit (this file, `.gitignore`, `DEVLOG.local.md`) has no
223223
version to release — push it, but no GitHub release is expected for it.
224+
225+
## 9. Always archive logs into field-logs/ — including user-supplied ones
226+
227+
The `field-logs/` folder (gitignored — never goes to the public repo) is the
228+
permanent home for every hardware log Claude sees. Two sources, BOTH must be
229+
saved without being asked:
230+
231+
1. **Logs read off a USB stick** before it gets re-flashed (the old
232+
`memforge2.log` / `report.json` get overwritten on the next run).
233+
2. **Logs the owner hands over** — pasted, attached, or dropped into
234+
`Downloads/` (e.g. a Habr commenter's `report (2).json` /
235+
`memforge2 (2).log`). The owner stated this explicitly: *"когда даю логи
236+
пользователей их тоже сохраняй."*
237+
238+
Save them the moment they're given/read, before doing anything that could
239+
lose them. Use a dated, descriptive subfolder:
240+
`field-logs/<who>/YYYY-MM-DD_<machine>_<cpu-or-owner>_<symptom>/` and give each
241+
file a name that records run #, date, version, and verdict so the pile stays
242+
navigable. This is diagnostic working data — never commit it, never quote
243+
machine/BIOS/serial details from it in a public reply (see §5).
244+
245+
**Split by source — two top-level buckets:**
246+
- `field-logs/mine/` — the owner's own bench machines (his Dell OptiPlex
247+
units etc.). These are HIS hardware; he may choose to publish a curated
248+
subset (see below).
249+
- `field-logs/users/` — logs handed over by forum/issue users (e.g. RoVRy's
250+
MSI/7900X). These are SOMEONE ELSE's machines and must NEVER be published
251+
or quoted with identifying detail — privacy is not the owner's to give away.
252+
253+
The whole `field-logs/` tree stays gitignored (private working data). If the
254+
owner wants real-world example reports in the public repo, copy a CURATED set
255+
of HIS OWN logs only into a tracked `docs/examples/` (or similar) folder —
256+
never the users' ones, and consider redacting RAM serial numbers first.

0 commit comments

Comments
 (0)