Declaration Materials and File Review for Investment Project Approval and Post-Evaluation: Source Citation and Traceability

Declaration Materials and File Review for Investment Project Approval and Post-Evaluation: Source Citation and Traceability

What this category of data includes

Service entities for this category include central enterprise strategic investment departments, project companies, state-owned asset supervision departments, and external consulting and evaluation institutions. Daily generated documents cover annual investment plans, project proposals, feasibility study reports, due diligence reports, asset evaluation reports, and post-investment evaluation reports. Data sources include state-owned asset supervision authority investment supervision systems, enterprise ERP and project management systems, industry market data, audit and financial statements. The update frequency is quarterly. Document structures and fields vary across different sources. Core fields include project number, investment amount, approval nodes, and post-evaluation indicators.

Data sources are scattered across multiple internal and external systems. The traceability link must support cross-system source identifier binding to ensure cited content can be traced back to the original generating system. The quarterly update frequency requires the index update cycle to match the data synchronization rhythm, to avoid citing outdated project information. Complex document structures and inconsistent fields require adaptation to long text chunking and multi-field extraction, to ensure the integrity of cited content. Compliance requirements for file review mean traceability information must include the original document’s generation time, source system, and approval node. Relying solely on general document titles is insufficient. Consequences of errors include state-owned asset losses and liability investigations. The traceability link must accurately associate each cited item with its original basis, to avoid mismatches between citations and content.

How to configure the settings

Configuration ItemRecommended ValueRationale
Maximum Context8000–12000 tokenAdapt to the average length of a single feasibility study report, match the total scale of quarterly updated documents
quoteMaxToken1500–2000 tokenEnsure a single cited item fully covers core project parameters, avoid truncating key investment amount or approval node information
Maximum Number of CitationsTop 6Match the standard number of citations in investment decision-making meeting materials, avoid excessive redundant content interfering with large model generation
detailEnabledDisplay the original document source field for each citation, meet the compliance traceability requirements of file review
responseDataEnable traceability fieldsRetain association identifiers for original data, facilitate subsequent audits and liability tracing
Cross-source Binding SwitchEnabledAdapt to data sources scattered across different systems, ensure traceability information is accurately linked to the original system

Three Common Configuration Mistakes

  • Phenomenon: After adjusting quoteMaxToken to above 2000, the large model response does not cite any retrieved content, and retrieved records can only be viewed in the background. Reason: The total context length exceeds the system threshold, causing cited fragments to be filtered out and not included in the generation context.
  • Phenomenon: The response shows eligible citation counts, but the corresponding cited content does not appear in the main text. Reason: The detail parameter was not enabled correctly, so cited fragments were not embedded into the large model’s generation context.
  • Phenomenon: Calling the API to reference a private knowledge base returns empty traceability fields. Reason: The responseData parameter was not enabled, and external call traceability permissions were not opened.

How to Confirm the Configuration is Successful

  • Upload a single annual investment plan document, trigger a question that includes the project number, check if the response contains this field.
  • View the question and answer details page, confirm that the original document’s source path and update time are displayed below each cited item.
  • Call the API interface, check if the returned detail field contains complete traceability information.
  • Adjust quoteMaxToken to 1800 token, verify that the response can still correctly cite fragments of eligible length.
  • Adapt to the configuration logic of FastGPT v4.17.0, ensure all parameters take effect.

The values provided are common starting points and should be evaluated against the user’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.