1.0
Review source quality
Operators see extraction warnings, hash, chunk count, tags, and trust state before a source becomes retrievable.
- Warnings
- Tags
- Chunk count
Home
Resource
Knowledge review
The workflow for approving, rejecting, renaming, and retiring project-scoped knowledge before it can shape support drafts.
State
Trusted
Only approved sources influence drafts.
Preview
Text
Extracted text can be inspected.
Coverage
Project
Sources stay scoped to the right product.
2.0
Keep retrieval accountable
Approved sources provide citations, while rejected or stale sources remain visible but out of the draft path.
- Approve
- Reject
- Retire
Operations
What this means in production.
These pages describe the product contract behind the UI, not a decorative brochure. Each surface should connect back to the same governed support loop.
Control boundary
No dashboard editing of uploaded source text.
Operator workflow
Support moves through secure ingest, AI preparation, human approval, outbound execution, and audit evidence.
Configuration impact
Provider setup, project policies, knowledge trust, retention, and billing limits decide how this behaves for a real workspace.
Proof points
Designed for governed support, not hidden autonomy.
No dashboard editing of uploaded source text.
Rejected sources stay excluded.
Citations can be shown with drafts.
References
Official stack and legal references.
These external links point to provider documentation, privacy notices, data-processing terms, or platform terms that shape production operation.