What this category's data looks like
This category's data involves three types of materials: achievement registration forms, patent disclosure documents, and software copyright materials. Achievement registration forms record the achievement name, contributors, date, and signature; patent disclosure documents focus on the technical solution, inventors, filing date, and receipt; software copyright materials include the software name, version number, development completion date, and seal. The three types of materials come from different sources: registration forms are filled in by the research group, disclosure documents are written by the inventors, and copyright materials are compiled by the development team. In terms of update cadence, registration forms are submitted at any time as achievements are produced, disclosure documents are finalized before filing, and copyright materials are consolidated before registration. Field characteristics are manifested in the need for consistency among elements such as names, quantities, dates, signatures, and receipts. When entering the authorized access and external services function, achievement registration forms provide the externally visible achievement list and contributor information, patent disclosure documents provide the externally disclosable technical abstract and filing status, and software copyright materials provide the externally displayable copyright ownership and version information. Together, the three types of materials support the setting of the visible scope of the external entry point, and unauthorized content is not visible.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in the application settings, outputting the referenced historical message range and answer constraints. The externally available entry point and authorization scope are determined by the publishing service and file permissions; the model only processes filtered materials, while the publishing service and file permissions are responsible for actual authentication.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | The name, quantity, date, and signature must correspond consistently with the patent disclosure document and software copyright materials | Check the memory turns value in the application settings, run a trial with two consecutive follow-up questions, check whether the second round inherits the references from the first round, and record messages and chatId |
| Patent disclosure document | The inventor, filing date, and receipt must not have mismatched names or dates with the same record in the achievement registration form | Check whether the versions are synchronized, check whether the signature and receipt are complete, and confirm that the external fields declared in variables match the visible scope |
| Software copyright materials | The software name, version number, and development completion date must be consistent with the same record in the registration form | Access once with a restricted identity, see whether the visible scope matches the setting, ensure unauthorized content is not visible, and check whether the number of historical turns in messages is appropriate |
| Consecutive follow-up questions | The second round can correctly inherit the references from the first round | Run a trial with two consecutive question rounds, compare the usage records of the two runs, and confirm that consumption changes accordingly after adjusting the memory turns |
Three common errors
- Phenomenon: The name, quantity, and date of the same achievement do not match between the registration form and the disclosure document. Cause: The two materials are filled in separately without cross-checking.
- Phenomenon: The version of the software copyright materials is not synchronized, and the externally displayed version number is inconsistent with the registration form. Cause: The update cadences differ, and there is no unified version record.
- Phenomenon: The disclosure document lacks a signature or receipt, and the authorization scope cannot be proven during external services. Cause: Material archiving is incomplete, and the signature process is not closed-loop.
How to verify the setup
Acceptance of this function: with two consecutive follow-up questions, see whether the second question inherits the references from the first question; at the same time, check the actual values of the three identifiers messages, chatId, and variables in the configuration.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and ensure unauthorized content is not visible.
- Check the current value of memory turns in the application settings and match it with the preceding context range required by the question.
- Run a trial with two consecutive question rounds, compare the usage records of the two runs, and confirm that consumption changes accordingly after adjusting the turns.