What this category’s data looks like
The data sources involved in this category include regulatory and rule repositories, higher-level law databases, departmental policy document repositories, and administrative normative document filing systems. Update frequency is irregular. Documents processed daily include normative document drafts, drafting explanatory notes, legality review opinions, solicited comment summaries, and filing reports. Document fields include issuing entity, effective date, full text of articles, audit process node records, and more. The length of individual documents varies widely. Core content consists of policy provisions and review basis.
What constraints do these characteristics impose on the "citation sources and traceability" link
Data sources are scattered and updates have no fixed cycle. Traceability links must match the latest official published document versions in real time. Daily processed documents include internal process records and policy provisions. It is necessary to accurately distinguish between review basis content and process documents to avoid traceability pointing to non-compliant files. The length of individual documents varies widely. It is necessary to ensure complete citation of original text to support legality judgments. Compliance scenarios have strict requirements for citation authority. Official data sources must be directly bound, and third-party compiled content cannot be relied upon.
Configuration Setup
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Adapts to the full citation length of normative document provisions, avoids truncating core policy basis |
responseData | Enable traceability data return | Ensures that file metadata of citation sources is returned, meets traceability requirements for compliance review |
detail | Enable detailed traceability mode | Displays specific paragraph positions of cited provisions and source file identifiers |
| Number of associated knowledge bases | Top 6 | Adapts to the mounting needs of multi-department policy repositories for public sector and state-owned enterprise entities, avoids excessive data sources causing retrieval delays |
| Total word count limit for associated knowledge bases | 1000–1500 MB, calibrated via actual testing | Balances retrieval efficiency and content coverage, avoids resource exhaustion |
| Citation matching threshold | 0.85–0.95, calibrated via actual testing | Filters irrelevant matching results, ensures authority and relevance of traceability content |
Three Common Configuration Mistakes
- Phenomenon: In non-tool call mode, the large model output does not include knowledge base citation entries. Cause: The
responseDataconfiguration item is not enabled. The system does not return traceability data fields, making it impossible to generate a citation list. - Phenomenon: After associating multiple policy-related knowledge bases, the number of retrieval results is abnormally reduced or no matching content is found. Cause: The number of associated knowledge bases or total word count limit is not set appropriately. Excessive data sources cause retrieval resources to be scattered or exhausted.
- Phenomenon: Citation traceability only displays the file name, and does not mark the specific paragraph position of the provision. Cause: The
detailconfiguration item is not enabled. Only file metadata is returned, and no detailed position of the cited provision is included.
How to Verify Successful Configuration
- Initiate a test query containing specific policy provisions, and check whether the output result includes the file name and provision position of the citation source.
- Adjust the configuration of associated knowledge bases, and verify that retrieval results change correspondingly as data sources increase or decrease.
- Check configuration logs in the system backend, and confirm that parameter values of configuration items such as
quoteMaxToken,responseData, anddetailmatch preset values. - Trigger a test process simulating legality review, and check whether traceability content points to official compliant data sources.
The values provided are common starting points and should be measured against the reader's own 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.