disclosure-bureau/web
Luiz Gustavo 7826710051
Some checks failed
CI / Web — typecheck + lint + build (push) Failing after 41s
CI / Scripts — Python smoke (push) Failing after 4s
CI / Web — npm audit (push) Failing after 26s
CI / Retrieval — golden set (Recall@5 + MRR) (push) Failing after 4s
W4: bilingual EN + PT-BR Investigation Bureau (CLAUDE.md §3 contract)
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>
2026-05-24 12:02:59 -03:00
..
app W4: bilingual EN + PT-BR Investigation Bureau (CLAUDE.md §3 contract) 2026-05-24 12:02:59 -03:00
components W4: bilingual EN + PT-BR Investigation Bureau (CLAUDE.md §3 contract) 2026-05-24 12:02:59 -03:00
lib W4: bilingual EN + PT-BR Investigation Bureau (CLAUDE.md §3 contract) 2026-05-24 12:02:59 -03:00
.dockerignore baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
.env.local.example baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
Dockerfile baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
instrumentation.ts W0+W1+W1.2: security hardening, observability, autocomplete, glitchtip, forgejo CI 2026-05-23 18:18:42 -03:00
middleware.ts W0+W1+W1.2: security hardening, observability, autocomplete, glitchtip, forgejo CI 2026-05-23 18:18:42 -03:00
next-env.d.ts baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
next.config.ts baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
package-lock.json W2: rerank opt-in, analyze_image_region tool, RAG eval, graph cleanup, ADRs 2026-05-23 19:20:09 -03:00
package.json W2: rerank opt-in, analyze_image_region tool, RAG eval, graph cleanup, ADRs 2026-05-23 19:20:09 -03:00
postcss.config.mjs baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
README.md baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
sentry.client.config.ts W0+W1+W1.2: security hardening, observability, autocomplete, glitchtip, forgejo CI 2026-05-23 18:18:42 -03:00
sentry.server.config.ts W0+W1+W1.2: security hardening, observability, autocomplete, glitchtip, forgejo CI 2026-05-23 18:18:42 -03:00
tailwind.config.ts baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
tsconfig.json baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00

web — Disclosure Bureau Next.js app

Next.js 15 + React 19 + Tailwind + Supabase + assistant-ui.

Quick start (local dev)

# 1. Install deps
npm install

# 2. (Optional) Start local Supabase
#    Requires Docker. Skip if pointing at remote Supabase.
npx supabase init        # first time only — creates supabase/ folder
npx supabase start       # spins up Postgres/GoTrue/Storage on :54321

# 3. Configure env
cp .env.local.example .env.local
# Edit .env.local — paste local Supabase keys (printed by `supabase start`)

# 4. Apply migrations
psql postgresql://postgres:postgres@localhost:54322/postgres \
  -f ../infra/supabase/migrations/0001_chat_schema.sql

# 5. Start dev
npm run dev
# http://localhost:3030

Without Supabase

The app degrades gracefully if Supabase env vars are unset:

  • Wiki browsing works (read-only from filesystem)
  • Auth bar shows "auth: disabled (dev)"
  • Chat bubble shows "Auth not configured"

Useful for quick UI work without spinning up Docker.

Production (Coolify on VPS)

See ../infra/coolify/. Stack:

  • Coolify orchestrates everything
  • Supabase self-hosted: db.disclosure.top, studio.disclosure.top
  • Next.js: disclosure.top
  • Meilisearch (shared): search.disclosure.top
  • Imgproxy (shared): img.disclosure.top
  • Caddy: TLS + reverse proxy (built into Coolify)

Architecture

app/
├── page.tsx                          # home — 116 docs grouped by collection
├── auth/
│   ├── signin/page.tsx               # magic-link form
│   ├── callback/route.ts             # exchanges code for session
│   └── signout/route.ts
├── d/[docId]/
│   ├── page.tsx                      # doc detail
│   └── [page]/page.tsx               # page reader (OCR + entity highlights + crops + sidebar PNG)
├── api/
│   ├── me/route.ts                   # GET current profile
│   ├── sessions/route.ts             # GET list, POST new
│   ├── sessions/[id]/route.ts        # GET detail, PATCH, DELETE
│   ├── sessions/[id]/messages/route.ts  # POST send → assistant reply
│   ├── documents/, pages/, entities/, tables/  # read-only data
│   └── static/[...path]/route.ts     # sandboxed file serve
components/
├── chat-bubble.tsx                   # floating Sherlock — auth-aware, session list
├── entity-modal.tsx                  # opens on entity click
├── reader-content.tsx                # OCR + highlights + crops
└── auth-bar.tsx                      # sign in / out + budget tracker
lib/
├── wiki.ts                           # markdown reader (gray-matter)
├── entity-index.ts                   # match loader + text segmentation
└── supabase/{server,client}.ts       # SSR helpers
middleware.ts                         # session refresh on every request

Tech notes

  • No RAG: chat agent reads markdown directly. Wiki-link traversal substitutes for vector search.
  • RLS-first: Supabase Row Level Security enforces "user sees only own sessions" at the DB layer.
  • Magic-link auth: no passwords. GoTrue handles email delivery.
  • Anti-abuse: per-user budget cap (default $5) + daily message quota (default 100) enforced via check_budget RPC before each Claude call.

Cost

Each chat turn costs ~$0.005-0.05 depending on context size (mostly Haiku $1/M input, $5/M output).