Skip to content
Intelligence

Intelligence

Intelligence is what the platform knows about the estate it manages. Most of it is a page-for-page Flutter port of the partner product Atlas: capital-governance (CapEx) data quality, business-rule governance, remediation, and playbooks. CORE adds three pages of its own. Resolve maps the data estate, Data audit assesses it, and Deploy lineage answers “did my commit ship”.

Everything on these pages comes from CORE’s own services. Atlas displayed fixed sample numbers. CORE ports only the layout and the engine. A figure CORE cannot compute is drawn as absent, with the reason, and never as zero.

Three rules every page follows

  • Absent is a state, not a zero. A figure that cannot be computed is a Kpi with no value and a non-empty absent_reason. Each response also carries a Provenance: LIVE, DEFAULT, EMPTY (nothing has been uploaded) or UNAVAILABLE (the store could not be read).
  • Reads never dial. A page load, a timer or a read RPC never contacts a tenant source. Only an admin’s confirmed Resolve action (or a CapEx pull) dials.
  • Writes are attributable and audited. Every non-read attempt is recorded in the console’s audit chain, including refusals. With no sign-in configured, every write is refused.

Where it lives

PieceSource
Page map (Atlas page → CORE data)flutter/lib/features/intelligence/ATLAS_SOURCE.md
Protosgrpc/operators/core/api/proto/runink/core/{atlas,ask}/v1/*.proto
Service implementationsgrpc/operators/core/internal/console/atlas_*.go, ask*.go
CapEx engine (stdlib)grpc/operators/core/internal/atlas/capex/