/**
 * Baseline-schema vertical metadata.
 *
 * `src/services/schema_definitions.ts` ships ~65 baseline entity schemas that
 * pre-date the `VerticalPack` system. Rather than rewriting each schema's
 * inline `metadata` block to declare `verticals` / `primary_vertical` /
 * `example_use_case` (a 65-touch refactor with high merge-conflict risk),
 * this module owns the mapping in one place. It is merged into the schema
 * registry's view of metadata at the boundary points that need it:
 *
 *   - the records index/guide pages (P2 frontend)
 *   - the `GET /api/registry/entity-types` payload (P2 API)
 *   - the `frontend/src/data/entity_types.generated.ts` generator (P2 generator)
 *
 * Vertical-specific schemas defined in `src/services/verticals/schemas/<slug>.json`
 * already declare `verticals` and `primary_vertical` inline; they take
 * precedence over this baseline table when both are present.
 *
 * Mapping rules:
 *   1. Use the same href base as `EntityTypeGuidePage.tsx`'s legacy
 *      `verticalHref` mapping for the seven types it covered (contacts,
 *      tasks, transactions, contracts, etc.).
 *   2. For everything else, pick the vertical where the type is "natural" —
 *      where an operator working in that vertical would expect to find it.
 *      Multi-vertical types list secondary verticals after the primary.
 *   3. Personal-life rolls up health/habit/goal types; personal-agent rolls
 *      up agent_* runtime types.
 */
export interface BaselineVerticalMetadata {
    verticals: string[];
    primary_vertical: string;
    example_use_case: string;
}
export declare const BASELINE_VERTICAL_METADATA: Record<string, BaselineVerticalMetadata>;
/** Snake-case entity types covered by the baseline vertical map. */
export declare function listBaselineEntityTypes(): string[];
/** Lookup with `null` fallback for types not yet mapped. */
export declare function getBaselineVerticalMetadata(entity_type: string): BaselineVerticalMetadata | null;
//# sourceMappingURL=baseline_metadata.d.ts.map