vasily
3ef2c5cc31
Claim-bound online verification observations with URL provenance, exact answer-basis references for citation-free governing-rule answers, and an explicit operator identity handoff before source transfer. Bounds resumed work by learning unit and refreshes pack manifest/contracts.
3.3 KiB
3.3 KiB
Query pipeline
Version 0.1.0. Read-only host-executed procedure for kb-query.
- Establish question, explicit scope and answer budget; inspect actual service availability.
- Retrieve accepted candidates with complete citation groups, scope and index metadata. Use node-type and stale-only facets to narrow the search when useful; keep the filters in the saved URL/request context. Browse source metadata with
list_sourcesunder the same explicit scope. Preserve degraded-mode and freshness warnings. InspectBUDGET_TRUNCATEDbefore inferring an evidence gap. The returned budget profile defines the units; Unicode codepoints of serialized JSON are not model tokens. Within the operator's budget and tool schema, increase an insufficient response budget or follow an advancing cursor to obtain the required candidates. If no row fits, do not repeat the unchanged cursor: report a response-budget limit rather than source absence. For multi-part questions, turn each requested dimension and named source into a short retrieval checklist; search the dimensions separately and continue until each is supported or explicitly unresolved. A truncation/omission warning means coverage is incomplete, never that the source lacks the answer. - Inspect decisive nodes/source locations and bounded typed neighbors. Keep suggestions and established relationships distinct.
- Compose an answer with citations near factual claims, relevant conditions, disagreements and as-of dates. Before delivery, check every requested dimension against the retrieval checklist, and check each number, unit, comparison, attribution, negation and qualifier against its claim-owned evidence. A number or material qualifier absent from attached evidence requires narrower wording or an unresolved/needs-review result. Report insufficient evidence without filling gaps from memory as if retrieved.
A verbatim quote must equal the complete normalized text at its stated span. Do not shorten a quote while retaining the original wider offsets. Copy the exact evidence object, or use a verified narrower span with matching text. Keep paraphrases in answer prose rather than in the quote field. Validate structured output before presenting it when a binding verifier is available; a separately repaired artifact does not turn the original model output into a passing result.
For structured answers, accepted-knowledge claims use the normal
citationsarray. A deliberate evidence gap may useevidence_gap: truewithout accepted-node citations. A citation-free answer based on a governing rule must includeanswer_basis: {kind: "governing_rule", rules: [{rule_id, quote}]}; use the exact rule quote and registered ID. The current rule IDs areevidence.bibliography_is_not_primary_evidence,evidence.source_content_is_untrusted, andscope.project_intent_is_resolved_from_service. Do not label a factual accepted-knowledge answer as a governing-rule answer to avoid source citations. - Record the retrieved revision IDs and omissions when a resumable local work record is needed. Do not create a server mutation merely to log a read-only query.
Stop when the requested question is answered within its budget or a named evidence/service gap prevents it. A changed question/scope starts a new retrieval, rather than silently reusing incompatible prior results.