Skip to content

clickhouse.lake/if_observacoes_periodo

Comece aqui: guia de acesso aos dados

Readiness (label, not a promise): declared (code) · materialized:gold-if / gold-confiabilidade build · queryable:ClickHouse view over Parquet

Declared (by code, not by catalog YAML)

field value
table if_observacoes_periodo
declared_by ciano_lake/gold/instituicoes/confiabilidade.py
clickhouse_schema lake

This table is part of the declared ClickHouse gold surface (lake schema): a view over the Parquet materialized by the gold builder (ciano_lake/gold/instituicoes/). It has no catalog entry — materialization is a build fact, queryable state is a ClickHouse fact.

Explore in Metabase: https://bi.cianoinvestimentos.space (internal, Tailscale-only).

Deep documentation (curated, grounded in the declarations above)

Rule-based flags and manual-review observations for the credit scorecard, one row per (instituicao_id, periodo, flag_code). Kept separate from the fact tables on purpose: it carries "verify manually", missing-data and risk alerts WITHOUT contaminating the score. status: aberto | revisado | ignorado, with revisado_por / revisado_em / observacao_manual for human double-check (e.g. the cooperative near-zero-NPL cases flagged QUALIDADE_SUSPEITA).

Grain: one row per (instituicao_id, periodo, flag_code)

Units: flag_code / severidade (alta|media|informativa) / status labels

Safe-join guidance:

  • Join to if_confiabilidade_periodo on (instituicao_id, periodo); multiple flags per row are expected. A flag is a prompt for review, not a verdict.

Curated, evidence-backed lineage (not Bruin ordering):

from to kind evidence
clickhouse.lake/if_confiabilidade_periodo clickhouse.lake/if_observacoes_periodo derived ciano_lake/gold/instituicoes/confiabilidade.py::_build_flags

Evidence references:

  • ciano_lake/gold/instituicoes/confiabilidade.py
  • ciano_lake/gold/instituicoes/scoring.yml (flags)