From 73d219c34f752863fed00f981cc940d502a14db7 Mon Sep 17 00:00:00 2001 From: Jarvis Jr Hermes Date: Fri, 4 Sep 2026 10:08:35 +0000 Subject: [PATCH] docs: keep scheduled reports concise --- SKILL.md | 1 + 1 file changed, 1 insertion(+) diff --git a/SKILL.md b/SKILL.md index d057ca1..724ff41 100644 --- a/SKILL.md +++ b/SKILL.md @@ -255,6 +255,7 @@ For recurring registry batches, protect delivery from unbounded research: Legacy tables sometimes encode one vendor-backed service as two rows: one row for the service and another whose “system” label is only the supplier or e-solution credit. In the canonical six-column table, merge these into one service observation and place the supplier plus bounded role in `Contractor / company`; do not preserve a company name as a separate system merely to keep counts stable. This legitimate normalization changes the canonical identity set. Before bootstrapping, inspect the stale `SYS-*` analysis entry: delete it only if all lifecycle/hosting fields are still unknown; if it contains researched evidence, manually migrate that evidence to the correct surviving/new system identity when semantically applicable. Then bootstrap missing analysis entries, regenerate, and verify the expected observation/system delta and contractor extraction. Never make a bootstrap helper silently delete stale analysis IDs. 10. On `*.lrv.lt` procurement pages, inspect the raw attachment links as well as visible HTML. Plans and reports are often exposed only as generically named `/media/`, `/public/canonical/`, PDF, DOC, or XLS/XLSX links, so an HTML keyword scan can miss the actual procurement contents. Open and classify relevant attachment bodies before using them; a plan still proves intent only, not award or delivery. 11. Treat a completed no-new-claim rotation as a valid conservative research outcome. If the assigned source classes were genuinely reopened, identity and contractor/system query ladders were rerun, and existing claims remain supported, advance each dossier's `Last checked` date and the matching index date while preserving statuses, rows, confidence, and unresolved gaps. Do not advance dates after only a superficial availability check, and do not promote a status merely because the existing rows were reconfirmed. In the delivery report, state which source classes were checked and explicitly distinguish “no defensible new claim” from “no search performed.” +12. Keep scheduled-rotation delivery reports short and decision-oriented. Prefer five compact bullets: reviewed range and outcome; material evidence changes or conservative no-new-claim result; registry counts; validation, commit and exact-head publication/readback; and next range. Mention detailed query, document and route counts only when they explain a new claim, an exception or a blocker; keep exhaustive mechanics in the durable channel record instead of repeating them in the delivered report. ## Iterative Skill Improvement