john-slop/docs
Dandaedre 033be96d79
Rust CI JohnSlop passed all CI checks.
Gitea/john_slop/pipeline/head This commit looks good Details
test: complete formatter milestone
2026-09-29 16:51:44 +02:00
..
decisions docs: define input safety limits 2026-09-29 12:11:33 +02:00
README.md docs: publish formatter contract 2026-09-29 16:49:38 +02:00
architecture.md docs: publish formatter contract 2026-09-29 16:49:38 +02:00
background.md docs: split detailed guides from readme 2026-09-29 12:55:53 +02:00
configuration.md docs: publish formatter contract 2026-09-29 16:49:38 +02:00
development.md test: complete formatter milestone 2026-09-29 16:51:44 +02:00
editors.md docs: publish formatter contract 2026-09-29 16:49:38 +02:00
evaluation.md test: add reviewed heuristic corpus 2026-09-29 15:31:46 +02:00
heuristics.md feat: summarize confidence and severities 2026-09-29 15:49:54 +02:00
limitations.md docs: publish formatter contract 2026-09-29 16:49:38 +02:00
output.md docs: publish detector output contracts 2026-09-29 16:05:21 +02:00
usage.md docs: publish formatter contract 2026-09-29 16:49:38 +02:00

README.md

John Slop documentation

The root README is the short project overview. These guides hold the details needed to use, embed, and develop John Slop:

  • Runnable Rust examples demonstrate in-memory analysis, streaming path input, and shared replacement planning.
  • Usage documents accepted inputs, detector output, exit statuses, and the current formatter/LSP status.
  • Editor setup provides Helix (hx) and Vim configuration for the formatter and future LSP adapter, with current status caveats.
  • Output contracts specifies human and concise presentation plus the versioned JSON Lines schema and partial-error records.
  • Architecture describes module boundaries, shared domain values, input safety, and the reusable library facade.
  • Configuration documents schema version 1, source precedence, stable-ID merges, validation, and inspection commands.
  • Heuristics and confidence documents rule execution, applicability, evidence damping, normalization, and score interpretation.
  • Evaluation corpus records fixture provenance, per-rule precision/recall, aggregate false positives, and benchmark caveats.
  • Limitations covers false positives, evasion, domain shift, score semantics, evaluation limits, and operational boundaries.
  • Development covers the supported Rust version, feature matrix, snapshots, coverage, badges, and CI quality gates.
  • Background collects external context on observable signs of low-care AI-assisted writing.
  • Decision records preserve durable product and engineering choices, including confidence semantics and input limits.

Future LSP and release-hardening contracts remain specified in tasks.md and AGENTS.md until their implementation milestones land.