Skip to main content

AI learning user guide

AI learning user is an internal governance role. It should not be visible to normal accounting, archive, or customer viewer users. This role works with samples, golden datasets, provider benchmarks, release gates, and local OCR learning.

AI Learning Engine

What this role can do

AreaActions
Learning samplesReview, approve, exclude, and export samples captured from verification corrections.
Golden datasetsPromote trusted samples into controlled benchmark sets.
Provider benchmarkCompare Azure, Mistral, OpenAI-style extraction, Tesseract, RapidOCR, PaddleOCR, Ollama Qwen3 JSON routes, rules, and hybrid routes.
Release gatesCreate, compare, publish, and rollback model/prompt/rule/provider versions.
Local OCR learningUse teacher/student experiments to improve local OCR and rule extraction.
Quality analysisInspect field-level accuracy, line accuracy, confidence calibration, and correction SLA.

Workflow

  1. Refresh dashboard and verify the sample count.
  2. Select pending samples.
  3. Exclude noisy or invalid samples.
  4. Approve reliable samples.
  5. Promote a subset to mini-golden dataset.
  6. Run mini-golden accuracy.
  7. Create a release candidate.
  8. Publish only if critical fields and line metrics do not regress.
  9. Roll back if a provider or prompt performs worse.

Quality Engine

IDP quality guarantee

Quality Engine should turn technical OCR metrics into an operational guarantee:

  • critical field target;
  • line item target;
  • correction SLA;
  • QA sampling;
  • provider regression;
  • customer-specific accuracy state.

What this role must not do

  • It must not edit customer billing.
  • It must not manage unrelated tenant users.
  • It must not expose raw customer data outside approved training policy.
  • It must not publish a model or prompt without release gate comparison.

Demo test path

  1. Enter the IDP demo as AI Learning specialist.
  2. Confirm only AI Learning is visible in the menu.
  3. Refresh dashboard.
  4. Run mini-golden accuracy.
  5. Create a release candidate and verify publish/rollback controls are visible.