From e18ac45d702a7c39a79d4d2b273e4b4277e50ac2 Mon Sep 17 00:00:00 2001 From: Jeffrey Ward Date: Sat, 25 Jul 2026 09:59:04 -0400 Subject: [PATCH] Updated README --- README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 4f1b621..91a674b 100644 --- a/README.md +++ b/README.md @@ -320,9 +320,12 @@ tell you "PDF", just "this looks like something I was trained on, or not". - **Artifact:** trained weights live in `model/classifier.jld2` (committed), so the server just loads them at startup. Missing/unreadable ⇒ the server fails fast rather than run without classification. -- **Effect today:** *annotate-only*. The class is logged - (`classification=known|unknown`) but every file still moves to `done/`; the - classifier can't misroute real files while it's unproven. +- **Effect today:** *active routing*. The class is logged + (`classification=known|unknown`) and drives the pipeline split: `:known` files + go to `known/` for metadata enrichment (stage 2), `:unknown` files go to + `unknown/` for content triage (stage 3). The class chooses the downstream + stage; what's still unproven is the model's *accuracy*, not whether the routing + path runs. The architecture and byte→feature mapping are defined once in `src/model.jl` and shared by the trainer and the server, so they can't drift apart.