feat: raw accept - incoming/ als abgeleiteter Rohablage-Eingang (schliesst #58)

Files changed: - .gitignore - CHANGES.md - README.md - VERSION - docs/pipeline-rationale.md - instructions/bootstrap.md - instructions/wiki-ingest/SKILL.md - raw/CONTRACT.md - tools/CONTRACT.md - tools/chemenu/cli.py - tools/chemenu/commands/dist_cmd.py - tools/chemenu/commands/docs_verify.py - tools/chemenu/commands/raw_cmd.py - tools/chemenu/tests/test_dist_cmd.py - tools/chemenu/tests/test_docs_verify.py - tools/chemenu/tests/test_raw_cmd.py
2026-09-05 07:43:43 +02:00
parent 1f0ad7f9f3
commit 36d2128f29
16 changed files with 753 additions and 46 deletions
@@ -14,6 +14,10 @@ thing later claims get checked against is no longer the thing that was actually
 immutable `raw/` means a citation always resolves to the original, not to somebody's tidied
 memory of it. It also draws a trust boundary in one place instead of scattering it - everything
 past `raw/` can be treated as reviewed, because nothing upstream of it silently already was.
+`incoming/` (Gitea #58) sits entirely on the near side of that boundary: a file waiting there is
+not yet reviewed and not yet a citation target, so its being gitignored and readable by an
+ingest session does not weaken anything - the boundary is the promotion into `raw/` itself, not
+the moment a human happened to drop a file somewhere.

 ## Why extraction happens once, through a schema