SYSE.43:4.2 - Construct writing and retrieval together

Choose granularity from the query and action. A single measurement may need an exact record; a recurring recovery may need a short episode linked to its trace. Summarize only after checking that the summary preserves the receiving-use conditions, and keep a return to the source when compression could be consequential.

Build the retrieval request from the unresolved premise: target, needed contribution, applicable edition or interval, and the kind of evidence required. Use exact identifiers or filters when those conditions are known; use semantic retrieval where wording varies. Rank by applicability as well as similarity. Bound what the receiver must inspect and retain enough provenance to qualify use. A person’s page/tab organization and a software index implement different access paths. For a model request, fit the retrieved material to its input budget through SYSE.52.

Keep read/write scope aligned with the permitted user or task. Prevent a record from another subject or access scope from becoming evidence merely because its wording is similar. Preserve the known origin when presenting an external record to its receiver.