Assign source ownership
Create a source register with owner, authority level, freshness target, permission contact, and retirement rule.
Deliverables
- Source ownership register
- Freshness target map
- Retirement policy
Guias
An operating model for keeping retrieval systems accurate, permission-safe, fresh, and useful after launch.
Conditions that should be true before expanding this workflow in production.
Knowledge sources have named business and technical owners.
Retrieval drift is detected through probes, reviewer signals, and source health metrics.
Remediation work is routed to the correct layer instead of defaulting to prompt changes.
Each stage produces operational artifacts that client teams can review and run.
Create a source register with owner, authority level, freshness target, permission contact, and retirement rule.
Deliverables
Evaluate source authority, conflict risk, freshness, ingestion reliability, and production readiness.
Deliverables
Run probes and reviewer-signal analysis to detect degraded source support or permission behavior.
Deliverables
Classify drift by failing layer and assign remediation to source, ingestion, ranking, permission, prompt, or policy owners.
Deliverables
Learn references that support this playbook in delivery.
Snapshot view used to track progress and health for this playbook.
Operational view focused on support throughput, escalation pressure, and queue quality.
Related routes