Context and Token Budgets for Kindergarten Operations and Quality Self-Assessment: Compare Documents and Locate Differences

Kindergarten Quality: 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 includes three types of materials: self-assessment reports, issue lists, and rectification plans. Self-assessment reports are updated by semester and contain items such as operating conditions, safety and hygiene, and care and education, with fields including name, quantity, date, and signature. Issue lists are summarized monthly, recording issue descriptions, responsible persons, and rectification deadlines item by item. Rectification plans are adjusted in sync with the issue lists and include measures, completion dates, and receipts. When these three types of materials enter this feature, the self-assessment report serves as the primary reference source, while the issue list and rectification plan serve as comparison objects, each taking on the role of field verification and discrepancy localization. During material verification, the name, quantity, and date of the same record in two materials must be consistent, versions must be synchronized, and signatures or receipts must be complete. The discrepancy list is answered by the model based on this, and the entry point and authorization are handled by the publishing service and file permissions.

Configuration and implementation checks

This part is executed by application settings (response limit, etc.), which determine 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 uses a slider to control the length of a single answer. If set too low, the answer may be truncated early; if set higher, the model can generate more complete content, but it may also increase consumption.

ObjectCheckVerification action
Self-assessment reportCheck whether the name, quantity, and date are consistent with the issue listIn application settings, check the response limit switch and slider position, compare the same record fields in the two materials, and record discrepancies
Issue listCheck whether the date, signature, and receipt are complete against the rectification planUse maxResponse to limit the length of a single answer, ask a question that requires a long answer to see whether the ending is complete, then compare the fields
Rectification planCheck whether the version is synchronized and the quantity corresponds with the self-assessment reportCheck the maxContext and quoteMaxToken settings, and confirm that the tokens of the quoted text and the number of array items are recorded separately
Ledger recordUse one real record to find fields inconsistent with the ledgerCompare name, quantity, and date field by field, mark inconsistent items, and hand them to the reviewer for confirmation and write-back

Three common errors

  • Symptom: The name, quantity, and date of the same record do not match between the self-assessment report and the issue list. Cause: The two materials are updated at different rhythms, and no field-level comparison was performed.
  • Symptom: The rectification plan and the issue list are not synchronized in version, and the number of items is inconsistent. Cause: After modification, the ledger was not written back, and there was no version verification action.
  • Symptom: The issue list lacks a signature or receipt, and the discrepancy list cannot be confirmed. Cause: Signatures and receipts were not collected during the material circulation process, and the omission was only discovered during verification.

How to verify the setup

Feature acceptance: Ask a question that requires a long answer, check whether the ending is complete, confirm that the response limit setting matches the answer length required by the page, and check the actual behavior of maxResponse, maxContext, and quoteMaxToken.

Business test: Use one real record to find fields inconsistent with the ledger, record discrepancies in name, quantity, and date, and hand them to the reviewer for confirmation and write-back.

  • In application settings, check the response limit switch and slider position, and compare usage changes between two runs.
  • Compare the name, quantity, date, and signature of the self-assessment report, issue list, and rectification plan field by field, mark discrepancies, and write them back to the ledger.