cyberneticlibrary

QA rendered content for extraction errors

content-rendering-qaworkflowsetup L30
bradyluce/theosis
What it does

Audit rendered content for source extraction artifacts

Best for

QA text content when you need to detect HTML/entities, page numbers, OCR gibberish, dropped words, truncation in rendered fields.

Inputs
  • · corpus domain (Bible verses, commentary, library chapters)
Outputs
  • · verified real issues + false-positive categorization + semantic findings (mis-mapping) + executive fix plan
Requires
  • · Deterministic scanner (counts mechanical hits)
  • · Grep (sampling)
  • · reader agents (judgment)
Preconditions

Corpus must be rendered via React Native (no HTML/markdown interpretation); rendered fields must be identified.

Failure modes

Scanner over-counts false positives (years, alt numbering); reader misses semantic issues; files too large to sample effectively.