Split SynthID campaign docs by detector, classifiers, and removal

Keep Model 1 as a research AI-versus-camera result outside the library.
Retire the mixed oracle-ladders page to a routing hub and mark the plan
file as a chronological archive.
This commit is contained in:
Victor Kuznetsov
2026-08-22 21:04:06 -07:00
parent e74b06d1a0
commit 99146cf2de
13 changed files with 1567 additions and 26 deletions
+2 -1
View File
@@ -187,7 +187,8 @@ OpenAI's API documentation says not to use repeated queries to reverse-engineer,
or evade a watermark. Using it as an adaptive research oracle therefore requires explicit
authorization. Without that authorization it must not become a training loss, search loop,
or automated removal gate. The provider-specific detector and pixel-only removal research
protocol is in [`synthid-detector-removal-plan.md`](synthid-detector-removal-plan.md).
protocol is in [`synthid-detector-research.md`](synthid-detector-research.md);
the chronological archive is [`synthid-detector-removal-plan.md`](synthid-detector-removal-plan.md).
Scope honestly: this tier certifies strength floors on a handful of images per vendor, and
that is all it can do. See `docs/synthid.md`.