Sources and catalog

Sources hold connection settings and operational health. Catalog holds the discovered objects and meaning used during planning.

Source lifecycle

A source moves from connected to indexed, curated, enabled, monitored, and eventually disabled or removed. Connection health and catalog readiness are separate states.

Catalog controls

For each object and field, data teams can review names, types, descriptions, availability, sensitivity, relationships, and organization-scoping metadata. Enabled objects become candidates for governed plans.

Descriptive business fields should be understandable to users. Technical identifiers may be needed for joins but do not need to dominate answer output.

Freshness and drift

Re-index after schema changes or on the organization's operating schedule. Investigate removed columns, changed types, new sensitive fields, and broken relationships before accepting drift.

Ownership

Assign an owner for every production source. The owner approves access, verifies representative questions, and responds to freshness or credential failures.