What is kept, and where
Every entry to share goes to .jadpo/suggest_pending with its kind:
found, accepted or ignored. The kind lets HQ tell a signal that was
right from one that fired wrongly. jadpo suggest share sends them
(Sharing with Jadpo HQ).
Everything in .jadpo/ is local, and the first command that writes there
adds .jadpo/ to .gitignore. .jadpo/suggest_last,
.jadpo/suggest_pending and .jadpo/suggest_signals hold one JSON object
per line, since they hold source text. Only the committed records are in
Jadpo's readable format. Those are written at format 2, with the shared
header (The record format),
as shown above. Files at format 1 are still read, and
jadpo records update rewrites them.
| File | Committed | Holds |
|---|---|---|
ignored_suggestions.jadpo_record |
yes | The team's ignores: hash, signal, suggestion, reason |
taught_suggestions.jadpo_record |
yes | The team's taught patterns: hash, suggestion, reason, canonical form |
.jadpo/suggest_last |
no | The last scan's findings, so a vanished one counts as accepted |
.jadpo/suggest_pending |
no | The entries waiting for share |
.jadpo/suggest_wanted |
no | The exact payload share --approve sends, until it is approved or declined |
.jadpo/suggest_shared |
no | That this checkout has shared once, so the first-share line shows once |
.jadpo/suggest_signals |
no | A cache of the taught record |
Markdown for agents: /docs/what-is-kept-and-where.md.Built from Jadpo main at a707efb.