Repair search result routing and advisory query ranking
This commit is contained in:
@@ -145,6 +145,7 @@ Implemented in `src/AdvisoryAI/StellaOps.AdvisoryAI/KnowledgeSearch/KnowledgeSea
|
||||
- Ranking determinism:
|
||||
- Freshness boost is disabled by default and only applies when `UnifiedFreshnessBoostEnabled` is explicitly enabled.
|
||||
- Ranking no longer depends on ambient wall-clock time unless that option is enabled.
|
||||
- Generic advisory/security-id intent (`cve`, `ghsa`, vulnerability/advisory wording) boosts findings and VEX evidence ahead of API-operation knowledge cards unless the query explicitly asks for API/endpoint material.
|
||||
- Query telemetry:
|
||||
- Unified search emits hashed query telemetry (`SHA-256` query hash, intent, domain weights, latency, top domains) via `IUnifiedSearchTelemetrySink`.
|
||||
- Search analytics persistence stores hashed query keys (`SHA-256`, normalized) and pseudonymous user keys (tenant+user hash) in analytics/feedback artifacts.
|
||||
@@ -180,7 +181,7 @@ Global search now consumes AKS and supports:
|
||||
- Type filter chips.
|
||||
- Result actions:
|
||||
- Docs: `Open`.
|
||||
- API: `Curl` (copy command).
|
||||
- API: `Copy Curl` plus `Copy Operation ID`; API cards must not navigate to dead-end placeholder routes.
|
||||
- Doctor: `Run` (navigate to doctor and copy run command).
|
||||
- `More` action for "show more like this" local query expansion.
|
||||
- A shared mode switch (`Find`, `Explain`, `Act`) across search and AdvisoryAI with mode-aware chip ranking and handoff prompts.
|
||||
|
||||
@@ -41,6 +41,8 @@
|
||||
10. Search should summarize close evidence automatically. AdvisoryAI expands detail; it should not be required to make the primary result understandable.
|
||||
11. Search suggestions are only valid when end-to-end execution against the active ingested corpus returns a grounded or materially useful answer.
|
||||
12. Search verification is incomplete until live ingestion-backed route coverage proves the surfaced suggestions on every supported page family.
|
||||
13. Generic advisory queries such as `cve` or `ghsa` must rank operator-facing findings/VEX evidence before raw API operation cards unless the query explicitly asks for API/endpoint details.
|
||||
14. Search actions must land on canonical Stella routes. Recovery-only URLs such as double-encoded docs paths are not release-ready behavior.
|
||||
|
||||
## Target interaction model
|
||||
### Entry
|
||||
|
||||
Reference in New Issue
Block a user