KERNIT Documentation
Hyperlinker Limits
KERNIT is built for real manuscripts, but unusually complex DOCX or resolver jobs can sometimes run into KERNIT-side processing availability. That is a service-side condition, not a client app requirement.
Practical Limits#
| Limit area | What to expect | Mitigation |
|---|---|---|
| DOCX validity | Only valid .docx packages are accepted. | Re-save the file in Word if the package is damaged. |
| Large files | Image-heavy files take longer to parse. | Compress images or test with scan first. |
| Server-side processing | Some resolver-heavy files may return a temporary service availability error. | This is handled as KERNIT service availability. Contact KERNIT support if it repeats. |
| Apply safety | Apply checks file/settings/graph consistency. | Use the same file, settings, scan token, and decisions. |
| Ambiguous citations | Same-year/same-author citations may be held. | Retarget manually in review. |
Availability Notes#
5xx responses indicate KERNIT-side availability or processing failures. They should not be framed as client integration mistakes. If the issue repeats, include the original scan token, settings, fingerprint, and decisions when contacting KERNIT support so the run can be traced.
Was this page useful?Send a lightweight docs feedback event.