Skip to main content

6 — Fase de Prova (EVIDENCE_PHASE)

Analisar a resposta do arguido, apreciar os elementos apresentados, decidir sobre diligências requeridas e consolidar a prova relevante para o desfecho do processo.

Source: src/components/workflow/FaseProvaPhaseView.tsx, FaseProvaFieldDrawer.tsx.

The widest phase view — five blocks, of which two carry inputs, one embeds the diligências engine and one is purely a read-back of Resposta do Arguido.

1. Elementos recebidos da resposta — no inputs​

Read-only summary of the previous phase: Texto da resposta (with a Recebida / Expirado / Pendente badge) · Anexos submetidos (file count) · Testemunhas indicadas · Diligências requeridas (count).

2. Decisão sobre diligências requeridas​

One row per requested diligência, each with two inputs:

InputControlOptions
DecisãoselectDeferida · Indeferida · Deferida parcialmente · Por decidir
Notastextarea

The rows are synthesised by splitting case_response_data.diligences_requested on newlines and trimming. Each ruling is then stored under the key diligence_<index> in case_phase_deliverables.metadata.diligence_decisions.

Nothing binds that index to the text it ruled on. Reorder the requests textarea in the previous phase, or delete a line, and every ruling silently re-attaches to a different request — an Indeferida can become an Indeferida of something else. For a phase whose output is the defensible record of which defence requests were refused and why, the identity of the thing being refused is a line number in a string. Compare string vocabulary contracts.

The header counts "n/total decididas", but nothing gates on it: the phase can complete with every request still Por decidir.

3. Diligências probatórias​

InquiryActionsList with phase="EVIDENCE_PHASE" and dismissalIntent passed through — the same eight action types as Inquérito Prévio, catalogued in diligências. This is where a WITNESS_HEARING for the arguido's named witnesses, or an ARGUIDO_HEARING, would actually be run.

4. Consolidação da prova — 5 steps​

All five are 12-row textareas in one drawer, stored in the deliverable's jsonb metadata.

StepWhat it asks for
Factos confirmadosFactos que ficaram provados após a instrução probatória
Factos controvertidosFactos que permanecem controvertidos ou cuja prova é insuficiente
Prova relevanteSíntese da prova relevante produzida nesta fase (documental, testemunhal…)
Observações internasNotas internas da equipa — não visíveis ao arguido
Timeline probatória consolidadaCronologia consolidada dos factos e atos probatórios

Four of these five are re-asked in Relatório Final, pre-filled from here.

5. Deliverable — Nota de Consolidação Probatória​

Creation mode (auto · company Word template · upload) → editable content → Validar. The auto template is generated from the consolidation fields, the diligence rulings, the requested diligências and the response text together.

Gate​

Allowed transitions: BODIES_OPINION or FINAL_REPORT. Which one is mandatory depends on dismissal_intent && employee_rep_or_union_related — see bodies opinion mandatory.

Leaving this phase stamps cases.last_evidence_act_at, the anchor for the next deadline.