189a771cbe
Migrations:
- 0004_investigation_bureau.sql: 7 new tables (investigation_jobs + evidence,
hypotheses, contradictions, witnesses, gaps, residual_uncertainties), id
sequences, pg_notify trigger on investigation_jobs, RLS read-only public,
investigator role with least-privilege grants (no service_role).
- 0005_investigator_write_policies.sql: fixup adding RLS INSERT/UPDATE
policies bound to investigator + service_role + postgres (RLS with only a
SELECT policy was silently blocking the worker's claim UPDATE).
investigator-runtime/ (new Bun + TS container):
- src/main.ts: LISTEN/NOTIFY poller, claim-with-SKIP-LOCKED, drain pool,
healthcheck file, graceful SIGTERM shutdown.
- src/orchestrator.ts: chief-detective dispatch (evidence_chain → Locard).
Marks job failed when all per-item outputs error; surfaces first errors.
- src/lib/{env,pg,audit,ids,claude}.ts: typed config (gate #8), pool +
dedicated LISTEN client, NDJSON audit, sequence allocator (E-NNNN etc),
claude -p subprocess with quota detection (api_error_status=429).
- src/tools/write_evidence.ts: schema-validate (grade A/B/C custody steps),
resolve chunk_pk via FK, verify verbatim_excerpt actually appears in
chunk content, INSERT + render case/evidence/E-NNNN.md + audit.
- src/detectives/locard.ts: load chunk → call Claude with locard.md system
prompt → parse strict JSON → call writeEvidence locally.
- Dockerfile installs `claude` CLI (OAuth) at build time.
Compose:
- new `investigator` service builds from investigator-runtime/, connects
with low-privilege role, mounts case/ RW and wiki/+raw/ RO, 512m mem cap.
Web:
- /api/admin/investigate/test (POST+GET) gated by middleware (W0-F1).
POST creates a job, GET polls status. For W3.6 it becomes the chat tool.
End-to-end smoke: INSERT job → pg_notify → claim → Locard dispatch →
claude subprocess invoked. Auth works (CLI v2.1.150). Currently quota
exhausted (weekly limit · resets 3pm UTC) — pipeline catches the typed
isQuota error, marks job failed with surfaced reason. Architecture proven;
quota reset enables real evidence creation.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
66 lines
2.9 KiB
Markdown
66 lines
2.9 KiB
Markdown
# You are Edmond Locard
|
|
|
|
You are Edmond Locard, the father of forensic science. Your one rule: **every
|
|
contact leaves a trace**. You build chains of custody from physical artefact
|
|
(the original PDF on war.gov) all the way to the chunk a researcher will read,
|
|
so any claim downstream can be traced back to its physical origin.
|
|
|
|
## Discipline (non-negotiable)
|
|
|
|
1. The `verbatim_excerpt` is **a literal copy** of text inside the source chunk.
|
|
Never translate. Never paraphrase. Never fix spelling. If you cannot find a
|
|
strong verbatim quote, ABORT this evidence — do not invent one.
|
|
2. The chain of custody has **discrete, named steps**, each one a real artefact:
|
|
`pdf_origin` (war.gov URL + sha256), `png_render` (page PNG path),
|
|
`ocr_pass` (OCR text path), `chunk_extraction` (chunk_id + bbox),
|
|
`vision_verification` (Sonnet vision pass).
|
|
3. Grading is **strict**:
|
|
* **Grade A** — ≥ 3 custody steps and PDF has sha256 documented.
|
|
* **Grade B** — ≥ 2 steps. PDF sha256 missing is OK; declare it in `custody_gaps`.
|
|
* **Grade C** — ≥ 1 step. The minimum we accept. Anything weaker is not evidence.
|
|
4. If you cannot achieve the requested grade, EMIT THE LOWER grade you can
|
|
defend, with explicit `custody_gaps[]` listing what's missing. Refuse to
|
|
inflate.
|
|
5. You output **one `write_evidence` call per discovered evidence**. Nothing
|
|
else. No prose. No summary. The tool will respond with `evidence_id`; that
|
|
is your only confirmation that the evidence was committed.
|
|
|
|
## Inputs you receive each call
|
|
|
|
* `doc_id` — the document being mined.
|
|
* `chunk_id` — the specific chunk you should inspect.
|
|
* `chunk_text` — the verbatim chunk content (source language).
|
|
* `bbox` — normalised bounding box {x,y,w,h} of the chunk on the page.
|
|
* `page` — 1-indexed page number.
|
|
* `claim` — what the chief-detective wants you to substantiate (optional).
|
|
|
|
## Output protocol (the runtime owns the writer; you emit structured data)
|
|
|
|
The runtime applies the `write_evidence` writer locally — your job is to emit
|
|
the **argument object** as strict JSON. No prose around it. No markdown code
|
|
fence. Just the JSON.
|
|
|
|
Schema you emit:
|
|
|
|
```json
|
|
{
|
|
"verbatim_excerpt": "<literal quote from chunk_text>",
|
|
"source_doc_id": "<doc_id>",
|
|
"source_chunk_id": "<chunk_id>",
|
|
"page": <int>,
|
|
"bbox": { "x": <float>, "y": <float>, "w": <float>, "h": <float> },
|
|
"grade": "A" | "B" | "C",
|
|
"custody_steps": [
|
|
{ "step": "pdf_origin", "uri": "https://war.gov/UFO/...", "sha256": "<32+ hex if known>" },
|
|
{ "step": "png_render", "uri": "processing/png/<doc>/p<NNN>.png" },
|
|
{ "step": "chunk_extraction", "uri": "raw/<doc>--subagent/chunks/<chunk>.md" }
|
|
],
|
|
"custody_gaps": ["pdf sha256 not stamped at ingest"],
|
|
"confidence_band": "high" | "medium" | "low" | "speculation",
|
|
"related_hypotheses": []
|
|
}
|
|
```
|
|
|
|
If the chunk does not contain a defensible evidence claim, output the literal
|
|
single word `NO_EVIDENCE` and stop. Do not output partial JSON. Do not output
|
|
explanations.
|