Evernote cull tooling on evernote.gf.cx — batch-LLM Layer-2 value_signal pipeline (parked sketch 2026-05-29)
DARE.CO.UK · PARKED SKETCH · 2026-05-31
Mirrored from ~/.claude/.../memory/parked_sketch_evernote_cull_tooling_on_surface_2026-05-29.md. This is a design sketch parked for future build — read for context, not as a current deliverable.
Build plan for the 24K → ~2.5K diamond+gold cull pipeline that lives on evernote.gf.cx once the corpus is ingested. Per-note Haiku call → value_signal scoring → Diamond/Gold/Reference/Archive/Noise tier assignment → /diamonds/ + /timeline/ + curation UI surfaces. Architecture already designed in the 2026-05-22 parked sketch; this entry is the trigger conditions + build order specific to the evernote.gf.cx locus.
Sketch: A batch-LLM cull pipeline that processes the ingested 24K-note corpus and surfaces the ~10% signal tier (Diamond + Gold ≈ 2.5K notes) as the default view on evernote.gf.cx. Nothing deleted — every note remains searchable; the default view just shows signal. Per-note value_signal score drives tier classification; manual Dan-validated overrides win over the LLM.
Why parked: Blocked on (a) full-corpus ingest landing in ~/Code/evernote.gf.cx/_substrate/ (estimated 6–12 hours wallclock for the 24K with heavy video) and (b) a Dan-validated check on the dry-run substrate output shape before betting $25-35 of Haiku spend on the full pass. Build the cull tooling AFTER the substrate is locked, not in parallel.
Resume conditions:
- ENEX exports complete from Evernote desktop (~30 manual clicks)
pa-evernote-substrateR2 bucket created + 1Password creds wired- Full 24K ingest run completed;
_index.jsonshows expected note count - Dan eyeballs ~20 sample notes in the substrate and confirms ENML→markdown fidelity is acceptable
- Then unblock this sketch
Architecture (lifted verbatim from 2026-05-22 parked sketch):
Per-note Haiku call returns standard schema PLUS a value_signal block: