Context and Token Budgets for Grade Entry and Credit Recognition: Find Supporting Evidence

Grades and Credits: review context & tokens for evidence lookup. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

This page is for grade entry and credit recognition scenarios. The materials include three types: transcripts, deferred exam applications, and makeup exam arrangements. Transcripts carry course names, credits, grades, and signature fields; deferred exam applications record the reason for deferral, the original exam date, and approval signatures; makeup exam arrangements state the makeup exam time, location, and receipt. Materials are updated by semester and batch, with course code, student ID, date, and signature as the key fields. When entering the business basis query feature, transcripts serve as the primary record source, while deferred exam applications and makeup exam arrangements serve as supporting evidence and supplements. Together, the three support basis entries that can be traced back to the original text. If the name, quantity, or date of the same record does not match across two materials, or if versions are not synchronized, or signatures or receipts are missing, it will affect whether the basis entries can match the original text.

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. "Basis entries that can be traced back to the original text" are 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 will be truncated; if set too high, consumption will increase.

ObjectCheckVerification action
Response limitMatches the answer length required by the pageCheck the switch and slider position in application settings, and confirm the maxResponse value
Truncation behaviorThe ending of longer answers is completeAsk a question that requires a long answer and check the ending, while recording the budgets for maxContext and quoteMaxToken
TranscriptFields, dates, and signatures are complete, and it can match the original textCheck the course name, credits, grades, and signature fields, and confirm consistency with the same record in the deferred exam application and makeup exam arrangement
Deferred exam application and makeup exam arrangementThe version is current, and cases of missing signatures or receipts have been ruled outCheck the original exam date, makeup exam time, and receipt, and confirm consistency with the course code and student ID in the transcript

Three common errors

  • Phenomenon: The name or credits of the same course do not match across two materials. Cause: Entry was not unified by course code, so the basis entry cannot be traced back to the same original text.
  • Phenomenon: The dates in the deferred exam application and makeup exam arrangement are inconsistent. Cause: Versions are not synchronized, and old batch materials are still being referenced, affecting the determination of the basis entry.
  • Phenomenon: The transcript is missing a signature or the makeup exam arrangement is missing a receipt. Cause: The process node is not closed, and the basis entry cannot be confirmed as currently valid.

How to verify the setup

Acceptance for this feature: Ask a question that requires a long answer, check whether the ending is complete, and verify whether maxResponse and maxContext match the answer length required by the page.

Business test: Ask a basis question that spans materials, see whether the answer gives a traceable source, and record the number of citations and the quoteMaxToken budget.

  • Check the response limit switch and slider position in application settings, and confirm they match the answer length required by the page.
  • Ask a question that requires a long answer, check whether the ending is complete, and compare the usage changes between two runs.