Context and Token Budgets for Research Outcome Registration and Intellectual Property: Compare Documents and Locate Differences

Research IP: review context & tokens for document checks. Check source versions, input mappings and the values received by downstream nodes.

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 are submitted by the completers, updated by batch, and contain fields such as achievement name, completers, date, and signature; patent disclosure documents are written by the inventors, updated as the application progresses, and contain fields such as invention name, technical solution, drawings, and receipt; software copyright materials are organized by the copyright holder, updated by registration milestone, and contain fields such as software name, version number, development completion date, and seal. When the three types of materials enter the material verification and discrepancy localization function, the achievement registration form serves as the baseline ledger, while the patent disclosure document and software copyright materials serve as the objects to be verified. The function compares field by field the name, quantity, and date of the same record in two materials, locates inconsistent fields, and generates a discrepancy list, which is handed to the reviewer for confirmation and then written back to the ledger.

Configuration and implementation checks

This part is executed by application settings (response limit, etc.), which output the length of a single answer and the range of context that can be accommodated. The "discrepancy list" is then completed by the model. The response limit is controlled by a slider for the length of a single answer; if set too low, the answer will be truncated, and if set too high, consumption will increase.

ObjectCheckVerification action
Achievement registration formFields, date, and signature are complete, serving as the baseline ledgerCheck the achievement name, completers, date, and signature column, record the ledger version number, and confirm the correspondence with the patent disclosure document and software copyright materials
Patent disclosure documentInvention name, technical solution, drawings, and receipt are consistent with the achievement registration formCompare field by field the invention name, quantity, and date, check whether the receipt is complete, and mark fields inconsistent with the ledger
Software copyright materialsSoftware name, version number, development completion date, and seal are consistent with the ledgerCompare the software name, version number, and development completion date, check the seal and receipt, and locate fields whose version has not been synchronized
Context rangeThe length of a single answer and the range of context that can be accommodated match the volume of materialsIn application settings, check the position of the response limit slider and confirm that the values of maxResponse, maxContext, and quoteMaxToken match the number of material fields

Three common errors

  • Symptom: The name, quantity, and date of the same record do not match in two materials. Cause: The achievement registration form and the patent disclosure document are maintained separately, fields are not compared item by item, and discrepancies are not written back to the ledger.
  • Symptom: The version is not synchronized, and the software copyright materials still show an old version number. Cause: After the materials are updated, re-verification is not triggered, and the ledger and the object to be verified are out of sync in version.
  • Symptom: A signature or receipt is missing, and the discrepancy list cannot be handed to the reviewer for confirmation. Cause: The signature column and receipt are not checked during material collection, and missing fields are only discovered during verification.

How to verify the setup

This function's acceptance: ask a question that requires a long answer, see whether the ending is complete, and confirm that the position of the response limit slider matches the answer length required by the page.

Business test: use a real record to find fields inconsistent with the ledger, record the name, quantity, and date fields in the discrepancy list, hand it to the reviewer for confirmation, and write it back.

  • In application settings, check the response limit switch and slider position, compare the usage of two runs, and confirm that the length of a single answer matches the context range.
  • Compare field by field the name, quantity, date, and signature in the achievement registration form, patent disclosure document, and software copyright materials, mark inconsistent fields, and write them back to the ledger.