Hafiza OS
The integration narrows model judgment to candidate selection over source-checked records, with privacy checks, input and question budgets, caching, deadlines, and a local fallback around the call.
The integration narrows model judgment to candidate selection over source-checked records, with privacy checks, input and question budgets, caching, deadlines, and a local fallback around the call.
Hafiza uses Jev as an optional advisor over verified knowledge cards and memory-catalog candidates. Given a query, facets, and eligible candidate records, it asks typed questions about candidate relevance and returns scores, distributions, or choices. Local retrieval and source checks remain in code; Jev scores can gate or rank candidate IDs, and records still require local validity checks. Jev does not write canonical memory or grant user approval.
Does candidate 0 directly support facet 0 of the current request, within its scope, domain, conditions, and exceptions?
Source-defined request state contains query, facets, candidate cards (id, title, statement, scope, domains), and optional string-valued previous_user/cwd/project fields. This illustrative request has one facet and one candidate, therefore one question key f0_c0.
Local retrieval builds candidate cards from records that pass existing scope, source, and validity rules.
The client places the query, facets, candidates, and permitted optional state fields in one shared state, then creates one typed question per facet and candidate.
The caller consumes candidate scores or distributions only in configured modes; it rechecks records and falls back to local retrieval when Jev is off, degraded, or results are unusable.
The integration narrows model judgment to candidate selection over source-checked records, with privacy checks, input and question budgets, caching, deadlines, and a local fallback around the call. It separates retrieval advice from ownership of stored facts.