What this category's data looks like
This category covers three types of materials: achievement registration forms, patent disclosure documents, and software copyright materials. Achievement registration forms record the name, contributors, date, and signature; patent disclosure documents carry the technical solution, inventors, application milestones, and receipts; software copyright materials correspond to the version number, copyright holder, completion date, and seal page. The sources of materials are the research group, the research management department, and the intellectual property role, and the update cadence changes with application milestones, version iterations, and approval circulation. When entering multi-turn dialogue and prompt features, achievement registration forms provide the achievement name and completion date fields, patent disclosure documents provide the technical name and inventor fields, and software copyright materials provide the version number and copyright holder fields. The three types of materials jointly serve signable material drafts and handover records; once the fields are complete, the responsible persons are clear, and the version and date are consistent, they are handed to the next stage for sign-off.
Configuration and implementation checks
This step is executed by the memory turns and prompt configuration in the app settings, and outputs the referenced historical message range and answer constraints. The signable material drafts and handover records are then completed by the model, while the external entry point and authorization are handled by the publishing service and file permissions.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | The name, contributors, date, and signature fields are complete, and the name, quantity, and date match the same record in the patent disclosure document | Check the memory turns value in the app settings, run a trial with two consecutive questions, and check whether the second question carries over the reference from the first question |
| Patent disclosure document | The technical name, inventors, application milestones, and receipt fields are complete, and the version and date are synchronized | Check whether the historical message range in messages covers follow-up questions on the disclosure document fields, and compare the usage records of two runs |
| Software copyright materials | The version number, copyright holder, completion date, and seal page fields are complete, and the name and date match the achievement registration form | Check whether the version and date passed in variables are consistent, and confirm whether missing signatures or receipts are blocked |
| Handover record | The responsible person is clear, the version and date are consistent, and the sign-off receipt for the next stage is complete | Use chatId to locate one handover session, and check whether the answer constraints for that turn cover the sign-off fields |
Three common errors
- Symptom: the same achievement name is written differently in the registration form and the disclosure document. Cause: the multi-turn dialogue did not lock the earlier name, and the prompt did not constrain field consistency.
- Symptom: the version number of the software copyright materials does not match the date on the registration form. Cause: the version was not synchronized, and historical messages brought in content from old turns that interfered with the current judgment.
- Symptom: a handover record missing a signature or receipt is still allowed through. Cause: the answer constraints did not enforce validation of the sign-off fields, and missing items were not blocked.
How to verify the setup
Acceptance for this feature: run two consecutive follow-up questions, see whether the second question carries over the reference from the first question, and check the referenced historical message range and answer constraints.
Business test: draft one document according to the template and complete one handover, and see whether missing items are blocked.
- Check the current value of memory turns in the app settings, and match it with the range of prior context the question requires.
- Run a trial with two consecutive questions, and compare the usage records before and after adjusting the number of turns.