What this type of data looks like
Reference only; verify against the target FastGPT release and deployment documentation.
What constraints do these characteristics impose on citation sources and traceability
The non-public nature of internal systems and data of state-owned enterprises requires traceability information to be bound to internal permission checks to prevent sensitive content disclosure. Documents with different update rhythms need to have their effective times marked in traceability to avoid referencing expired system clauses. Structured metadata provides precise identifiers for traceability, allowing the system number to be directly extracted as the core traceability field without relying solely on main text fragment matching. The multi-field structure requires traceability configuration to cover both metadata and main text content, ensuring citation integrity and verifiability.
How to Configure
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Matches the average main text length of internal system documents, avoids truncating key traceability clauses |
responseData | Enable associated field display | Ensures structured traceability metadata such as system number and effective date is included when generating reports |
detail | Full citation snippet | Retains context information from the original document to facilitate subsequent compliance checks |
| Number of citation sources displayed | Top 3 | Adapts to reading habits in internal scenarios, avoids excessive citations distracting from core responses |
| Permission check switch | Bind internal RBAC rules | Only displays traceability information to users with access permissions to the corresponding system, aligns with data security requirements of state-owned enterprises |
Three Common Misconfigurations
- Phenomenon: When setting
quoteMaxToken, only fixed options outside 100 or 900 are available, and custom values around 300 cannot be set. Reason: The preset options for this configuration item in FastGPT v4.17.0 do not include the middle range, and the target value must be adjusted manually via code parameters. - Phenomenon: Source traceability information is not displayed for referenced external HTTP return content. Reason: The
responseDataconfiguration is not enabled, and the metadata fields of the external interface return content are not bound, resulting in missing traceability information. - Phenomenon: Even after setting the minimum relevance to 1, the response outputs a large amount of non-core citation content. Reason: The length of the citation snippet in the
detailconfiguration is not limited, or the result deduplication logic is not enabled, causing redundant citations to be displayed.
How to Verify Successful Configuration
- Initiate an internal system query, check whether structured traceability fields such as associated system number and issuing unit are displayed at the bottom of the response result
- Check the actual effective value of the
quoteMaxTokenconfiguration, confirm whether it matches the preset token range - Copy a single citation snippet, verify that it completely matches the corresponding content in the original knowledge base document, with no truncation or tampering
- Adjust the relevance threshold, verify that the number of citations changes as expected with the threshold, with no abnormal redundant content
The values provided are common starting points and should be evaluated 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.