Reference only; verify against the target FastGPT release and deployment documentation.
What data this category includes
The data for this category mainly comes from the national government service platform’s "one thing" special zone, local integrated government service platforms, electronic certificate repositories, and approval systems of various departments. Daily documents include collaborative handling item lists, one-time notification sheets, collaborative handling application forms, material transfer sheets, parallel approval opinions, and completion receipts. The data update frequency is daily, and the field structures of different documents vary. For example, the collaborative handling item list includes fields such as item name and lead department, while the completion receipt includes fields such as handling result and transfer link.
Constraints on the citation sources and traceability link
Because data sources cover multiple departmental platforms, the traceability link must accurately label the original source platform and affiliated department for each cited item. This prevents confusion between cross-departmental collaborative handling policy bases. Data updates daily, so a regular synchronization mechanism must be configured to keep cited content up to date. Field structures vary widely across different documents, so original document metadata must be preserved to fully show the context of cited basis. The number of policy documents linked to collaborative handling items is relatively concentrated, so irrelevant non-collaborative policy content must be excluded to avoid disrupting responses.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 characters | Collaborative policy documents have moderate single-document length, preventing exceeding the model context window |
responseData | Enabled | Original cited document metadata must be returned for traceability display |
detail | Enabled | Complete fields of cited content must be displayed, such as lead department and handling link |
| Single recall limit | Top 5 items | The number of policy documents linked to collaborative handling items is limited; too many will dilute valid information |
| Synchronization cycle | Daily | Matches the daily data update frequency to ensure cited content is always the latest version |
| Temperature coefficient | 0.3–0.5 | Calibrated through actual testing, ensuring accurate policy citations without off-topic responses |
Three common configuration errors
- Phenomenon: The number of citations returned by semantic retrieval is far fewer or more than the actual number of associated collaborative handling policy documents. Cause: The single recall limit is not adjusted based on the actual number of policy documents associated with the collaborative handling item. A setting that is too small will miss valid policy basis, while a setting that is too large will introduce irrelevant content.
- Phenomenon: Some uploaded collaborative handling documents show training errors and cannot be retrieved. Cause: The document format does not meet the platform's supported standards, or a network interruption occurred during upload leading to failed chunked upload.
- Phenomenon: The response does not display traceability information such as the affiliated department and source platform of the cited content. Cause: The
detailorresponseDataconfiguration items are not enabled, so original document metadata is not returned.
How to verify correct configuration
- Upload a collaborative handling item list document, initiate a query that includes the item name, and check whether the response carries the corresponding citation source identifier and metadata.
- Adjust the value of
quoteMaxToken, and observe whether the total length of cited content in the response matches the set character range. - Upload multiple collaborative handling documents with duplicate policy statements, and verify that the knowledge base automatically deduplicates to avoid multiple citations of the same content.
- Trigger a query involving a cross-departmental collaborative handling item, and check whether the response labels the affiliated department and source platform for each cited item.
The values provided are common starting points and should be evaluated against local deployment samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.