Checks in CI
Run an originality gate in a pipeline — spin up the engine, submit documents, poll, and fail the build over a threshold.
The engine's API makes a clean CI gate: index your existing content once, then have the pipeline check new documents and fail when similarity crosses a threshold. Useful for content teams (no accidental self-plagiarism across a site), documentation reuse policies, or pre-submission checks.
The gate script
Works against any running engine — a long-lived internal instance or one started in the pipeline:
GitHub Actions example
Boots the engine as a job container set, indexes the repo's published content, then gates changed files:
Practical notes
- Index-then-check ordering: never index the document you're about to check first, or it matches itself at 100%.
- Ephemeral vs persistent corpus: re-indexing everything per run (as above) is simple and correct for small corpora. Past a few thousand documents, keep a long-lived engine instance and index on merge instead — see Corpus design patterns.
- Thresholds are policy, not truth. A quote-heavy article legitimately scores higher; pick per-content-type thresholds and expect to tune them.
- Time budget: very large documents may return
coverage: "partial"— decide whether your gate treats that as pass, fail, or retry with a higherNOPLAG_CHECK_BUDGET_S.