root 86123fce4c gateway: /v1/validate endpoint — Phase 43 v3 part 2
Closes the Phase 43 PRD's "any caller can validate" surface. The
validator crate (FillValidator + EmailValidator + PlaybookValidator
+ WorkerLookup) is now reachable over HTTP at /v1/validate.

Request/response:
  POST /v1/validate
    {"kind":"fill"|"email"|"playbook", "artifact":{...}, "context":{...}?}
  → 200 + Report on success
  → 422 + ValidationError on validation failure
  → 400 on bad kind

Boot-time wiring (main.rs):
- Load workers_500k.parquet into a shared Arc<dyn WorkerLookup>
- Path overridable via LH_WORKERS_PARQUET env
- Missing file: warn + fall back to empty InMemoryWorkerLookup so the
  endpoint stays live (validators just fail Consistency on every
  worker-existence check, which is the correct behavior when the
  roster isn't configured)
- Boot log line: "workers parquet loaded from <path>" or
  "workers parquet at <path> not found"
- Live boot timing: 500K rows loaded in ~1.4s

V1State gains `validate_workers: Arc<dyn validator::WorkerLookup>`.
The `_context` JSON key is auto-injected from `request.context` so
callers can either embed `_context` directly in `artifact` or split
it cleanly via the `context` field.

Verified live (gateway + 500K worker snapshot):
  POST {kind:"fill", phantom W-FAKE-99999}    → 422 Consistency
                                                 ("does not exist in
                                                  worker roster")
  POST {kind:"fill", real W-1, "Anyone"}      → 200 OK + Warning
                                                 ("differs from
                                                  roster name 'Donald
                                                  Green'")
  POST {kind:"email", body has 123-45-6789}   → 422 Policy ("SSN-
                                                shaped sequence")
  POST {kind:"nonsense"}                       → 400 Bad Request

The "0→85% with iteration" thesis can now run end-to-end on real
staffing data: an executor emits a fill_proposal, posts to
/v1/validate, gets a structured ValidationError on phantom IDs or
inactive workers, observer-corrects, retries. Closure of that loop
in a scrum harness is the next commit (separate scope).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-27 07:40:27 -05:00

35 lines
1.1 KiB
TOML

[package]
name = "gateway"
version = "0.1.0"
edition = "2024"
[dependencies]
shared = { path = "../shared" }
storaged = { path = "../storaged" }
catalogd = { path = "../catalogd" }
queryd = { path = "../queryd" }
aibridge = { path = "../aibridge" }
ingestd = { path = "../ingestd" }
vectord = { path = "../vectord" }
journald = { path = "../journald" }
truth = { path = "../truth" }
validator = { path = "../validator" }
tokio = { workspace = true }
axum = { workspace = true }
serde = { workspace = true }
serde_json = { workspace = true }
tracing = { workspace = true }
tracing-subscriber = { workspace = true }
tower-http = { workspace = true }
object_store = { workspace = true }
proto = { path = "../proto" }
tonic = { workspace = true }
opentelemetry = { workspace = true }
opentelemetry_sdk = { workspace = true }
opentelemetry-stdout = { workspace = true }
tracing-opentelemetry = { workspace = true }
arrow = { workspace = true }
chrono = { workspace = true }
reqwest = { version = "0.12", default-features = false, features = ["json", "rustls-tls"] }
toml = { workspace = true }