7826710051
User flagged that the bureau was emitting English-only output, violating
the project's bilingual rule. Every narrative field now ships in both
languages: stored in sibling DB columns + rendered as adjacent markdown
sections per CLAUDE.md §3.
Migration 0007 (apply as supabase_admin):
- public.hypotheses +question_pt_br, +position_pt_br,
+argument_for_pt_br, +argument_against_pt_br
- public.contradictions +topic_pt_br, +notes_pt_br
- public.witnesses +access_to_event_pt_br, +bias_notes_pt_br,
+verdict_pt_br
- public.gaps +description_pt_br, +suggested_next_move_pt_br
- public.evidence: unchanged (verbatim_excerpt stays source-language)
- JSONB siblings inside contradictions.chunks + gaps.scope handled at
runtime (statement_pt_br, title_pt_br, dominant_model_pt_br,
why_surprising_pt_br, what_it_implies_pt_br).
Detective prompts (all 7) rewritten with explicit bilingual JSON contract:
- Output protocol section names every EN field + its _pt_br sibling
- "Bilingual is mandatory" warning in the task instruction
- Sentinel skip-states unchanged (NO_HYPOTHESES, NO_CONTRADICTIONS,
INSUFFICIENT_TESTIMONY, INSUFFICIENT_HYPOTHESIS, NO_OUTLIERS,
NO_NEW_EVIDENCE, INSUFFICIENT_ARTEFACTS)
- Schneier: parallel arrays — hidden_assumptions[i] matches
hidden_assumptions_pt_br[i], lengths must match
- Case-Writer: interleaved §1 (EN) / §1 (PT-BR) per act in the body
Writer-side validation (all 7 tools):
- Reject INSERT if PT-BR sibling missing when EN field is set
- Persist both languages atomically in one INSERT (no half-updates)
- Markdown renderers write adjacent EN+PT-BR sections in case files
(## Argument for (EN) followed by ## Argumento a favor (PT-BR), etc.)
Detective parse layer (all 7 detectives):
- Coerce both keys from JSON output
- "incomplete_bilingual_*" skip reason when either side missing
- Defensive: PT-BR fields trimmed + length-capped same as EN
Orchestrator propagates question_pt_br + topic_pt_br through job payload
to runHolmes / runCaseWriter, mirroring the chat-tool entry point.
Web (UI):
- /api/jobs/[id] hydrates _pt_br siblings from pg
- job-status-poller HypothesisCard: PT-BR primary, EN in <details>
fallback when both exist
- ContradictionCard: PT-BR statement primary + secondary EN quote
- WitnessCard: PT-BR verdict primary + secondary EN quote, panels in PT
- GapCard: PT-BR title/why/implies primary
- /bureau hub: SELECTs both columns, renders PT-BR primary
- /h/[id]: ArgumentPanel renders PT-BR primary with collapsible EN
fallback when both exist
- BureauSnapshot homepage: position_pt_br / topic_pt_br / verdict_pt_br
primary
- DocBureauPanel /d/[doc]: same primary-PT-BR pattern
- New web/lib/i18n/pick.ts helper (unused yet by chat/agents — kept
for future locale-driven switching when both languages are equally
full; current rule is PT-BR-first since the user is brasileiro)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
44 lines
1.8 KiB
PL/PgSQL
44 lines
1.8 KiB
PL/PgSQL
-- 0007_bilingual_bureau.sql — bilingual EN+PT-BR sibling columns for the
|
|
-- Investigation Bureau (per CLAUDE.md §3: "Narrative descriptions ... Both
|
|
-- EN and PT-BR via sibling fields").
|
|
--
|
|
-- This migration adds nullable `*_pt_br` siblings for every narrative
|
|
-- column the bureau writes. Existing rows stay valid; new rows must
|
|
-- populate both. The detective prompts get re-flowed in W4 to emit both
|
|
-- languages in their JSON output.
|
|
--
|
|
-- Notes:
|
|
-- - public.evidence.verbatim_excerpt stays single-language. Per CLAUDE.md
|
|
-- §3, verbatim quotes "preserve source language only".
|
|
-- - public.contradictions.chunks JSONB carries `statement` per position;
|
|
-- the runtime adds a sibling `statement_pt_br` key per array item
|
|
-- (no schema change needed for JSONB shape).
|
|
-- - public.gaps.scope JSONB likewise carries `title`, `dominant_model`,
|
|
-- `why_surprising`, `what_it_implies` — the runtime adds `*_pt_br`
|
|
-- siblings inside the JSONB object.
|
|
--
|
|
-- Apply as supabase_admin (these tables are owned by supabase_admin
|
|
-- per migration 0004 / repo memory).
|
|
|
|
BEGIN;
|
|
|
|
ALTER TABLE public.hypotheses
|
|
ADD COLUMN IF NOT EXISTS question_pt_br TEXT,
|
|
ADD COLUMN IF NOT EXISTS position_pt_br TEXT,
|
|
ADD COLUMN IF NOT EXISTS argument_for_pt_br TEXT,
|
|
ADD COLUMN IF NOT EXISTS argument_against_pt_br TEXT;
|
|
|
|
ALTER TABLE public.contradictions
|
|
ADD COLUMN IF NOT EXISTS topic_pt_br TEXT,
|
|
ADD COLUMN IF NOT EXISTS notes_pt_br TEXT;
|
|
|
|
ALTER TABLE public.witnesses
|
|
ADD COLUMN IF NOT EXISTS access_to_event_pt_br TEXT,
|
|
ADD COLUMN IF NOT EXISTS bias_notes_pt_br TEXT,
|
|
ADD COLUMN IF NOT EXISTS verdict_pt_br TEXT;
|
|
|
|
ALTER TABLE public.gaps
|
|
ADD COLUMN IF NOT EXISTS description_pt_br TEXT,
|
|
ADD COLUMN IF NOT EXISTS suggested_next_move_pt_br TEXT;
|
|
|
|
COMMIT;
|