Compact interpretation storage metadata without summarizing evidence

This commit is contained in:
Nico committed 2026-10-15 11:29:30 +02:00
1 parent 82238ed213
commit 2fb81ef4af
11 files changed
+331 -20

No files matched your search

+27
View File
@@ -61,3 +61,30 @@ pending calls cannot silently change configuration mid-retry. A new entity
assessment attempt uses the new settings; accepted plan and previous assessment
artifacts remain unchanged and are checked without repeating their API calls.
No attempt counters or investigation budgets are reset.
## Compact interpretation protocol 6
Fresh entity-resolution inputs freeze interpretation protocol 6. Its prompt
receives a deterministic view of the full archived context. Only long storage
identifier fields containing digest material (40+ hexadecimal characters) use
short P aliases. Equal identifiers retain equal aliases; different identifiers
remain distinct. Filenames are retained as labels where applicable. Meaningful
source paths without digest material, human/descriptive text and database `row`
objects remain unchanged. This is not a semantic summary or evidence ranking.
Repeated origin/provenance objects are stored once in `input.shared_metadata`
and referenced with M metadata aliases. Their author, timestamp, snapshot scope
and other fields remain available; these aliases are not evidence source IDs.
All B/O/C/T/E/F/N/D/X source IDs and source kinds remain present, including unread
sources. Query filters, rows, completeness/truncation, next offsets, conflicting
names and uncertainty remain present. JSON whitespace is reduced in this new
prompt only. The stored full context, canonical case, raw archives and outputs
are unchanged. Existing protocols 1–5 preserve their original request bytes.
On the completed typed-names-20261015 sample, the initial interpretation messages
previously contained 151857 characters; the compact representation contains
83681 characters (44.9% fewer). These sizes are measured offline; this is not a claim about exact Gemini tokens, cost, or live quality.
The next fresh LLM trial must verify role/ID correctness, item-name uncertainty,
visibility prerequisites and investigation directions. No LLM pre-summary and
no extra model calls are introduced. Name-resolution prompts are unchanged.