Resource · FAIR catalog · evaluators

FAIR catalog for multi-horizon agent context

Findable, Accessible, Interoperable, and Reusable metadata for dept.* data products—so multi-horizon BI and Build · Steer · Compound loops stand on contracts, lineage, and provenance, not a company-wide vector dump.

Full organizational heartbeat: live operations, knowledge memory, and analytics patterns — department-scoped, policy-gated. FAIR catalog signals attach to those same mesh layers—operational heartbeats, knowledge products, and analytical live views—when evaluator features are enabled for your workspace.

Browse data product catalog for contracts, lineage, and freshness SLOs per product.

Why FAIR matters for agentic BI

Agents that invent numbers or cite stale docs fail evaluators. FAIR scores, DOI handles, and provenance alignment make products discoverable and citable under department tenancy—whether the product is an ops stream pulse, a knowledge doc event, or an analytical metric view.

Mesh layers in this dashboard

Operational mesh

Heartbeats from live SaaS connectors—incidents, tickets, deploys, CRM stages—as dept.* products with contracts and lineage agents can audit.

Knowledge mesh

Docs and runbooks as versioned products. FAIR metadata supports citation and reuse alongside live ops evidence—not disconnected RAG islands.

Analytical bridge

dbt metrics and warehouse CDC live views for longer-horizon BI. FAIR + freshness SLOs beat unconstrained warehouse SQL in prompts.

Multi-horizon context needs findable products

Real-time pulses, short-term stream history, and long-term analytical or institutional patterns only compound when products stay findable and interoperable under policy.

Real-time

Operational FAIR products back live heartbeats agents subscribe to under MCP policy.

Short-term

Catalog contracts and lineage keep recent history interpretable across systems—not first-class 1h/24h/7d window products.

Long-term

Analytical FAIR products and institutional recall need durable handles and provenance for Compound-loop narratives.

What this dashboard shows

  • FAIR-qualified products (metadata present or score ≥ 50) across mesh layers
  • DOI handles when minting is enabled for your control plane
  • Provenance alignment against the warehouse register (aligned / missing / pending)
  • Filter by operational · knowledge · analytical layers

Loading FAIR dashboard…

Evaluator honesty

FAIR dashboard, DOI, and provenance are optional control-plane features. Empty states mean those features are off.

Related I/O Mesh surfaces

Governed products agents can find and cite

Browse the catalog, map a multi-horizon use case, or Sign Up with Base Plan. FAIR features surface when enabled on your control plane.

Secure payment · Immediate full access · 15% off annual