Detect AI slop markers
Go to file
Dandaedre c88c5b8de2
docs: define input safety limits
2026-09-29 12:11:33 +02:00
docs/decisions docs: define input safety limits 2026-09-29 12:11:33 +02:00
src test: correct Unicode offset expectations 2026-09-29 12:10:17 +02:00
.gitignore chore: ignore local work recap 2026-09-29 12:07:28 +02:00
AGENTS.md docs: define architecture and implementation plan 2026-09-29 12:07:08 +02:00
Cargo.toml Shitcoded some base functions, too tired to do any useful shit 2025-12-04 17:27:50 +01:00
Jenkinsfile Add Jenkinsfile 2026-09-13 13:13:14 +02:00
LICENSE Initial commit 2025-12-03 18:42:17 +01:00
README.md docs: define input safety limits 2026-09-29 12:11:33 +02:00
tasks.md docs: define input safety limits 2026-09-29 12:11:33 +02:00

README.md

John Slop

John Slop is an early-stage, local-first heuristic linter for concrete signals of low-effort or insufficiently reviewed text and source code. It is intended to highlight evidence for human review, not to prove that content was written by AI or assign an authorship probability.

Current prototype

The repository currently contains proof-of-concept code that:

  • reads UTF-8 text from a file or recursively from a directory;
  • reads text entries from ZIP-based files, including .zip, .docx, .xlsx, and .pptx;
  • rejects missing paths and invalid UTF-8 with a diagnostic error;
  • detects a configured-in-code set of hyphen-like Unicode characters; and
  • demonstrates source-labelled terminal diagnostics with miette.

The implementation is being restructured into a reusable library plus detector, formatter, and LSP binaries. See tasks.md for the ordered backlog and AGENTS.md for the design and contribution rules. Architecture and product choices are recorded under docs/decisions, beginning with the core analysis contracts. The default traversal, text-recognition, and archive safety policy is specified in ADR 0002.

Development

Run the current test and quality suite with:

cargo fmt --all -- --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test --all-targets --all-features
cargo doc --no-deps

Behavior is intentionally captured with regression tests before the refactor so that later changes are deliberate and reviewable.

Detector spans use zero-based UTF-8 byte offsets. Presentation layers will convert those canonical offsets to terminal or LSP coordinates at their boundaries.

Background reading