import type { TemplateResult } from 'lit';
import { nothing } from 'lit';
import type { Translate } from './hd-reading.js';
/**
 * The sidereal frame a Vedic response was computed in.
 *
 * @remarks
 * Structural rather than imported from one response type, because fifteen different schemas carry the identical object and a component should not have to name whichever one it happens to render. Both fields are required by the schema; they are optional here only so a component can pass `d.frame` without proving the payload is complete first.
 */
export interface SiderealFrame {
    ayanamsa?: string;
    ayanamsaDegrees?: number;
}
/**
 * Shared styling for the frame caption. Include in a component's `static styles` alongside {@link renderFrameCaption}.
 */
export declare const frameCaptionStyles: import("lit").CSSResult;
/**
 * One line naming the sidereal frame a chart or strength table was cast in.
 *
 * @remarks
 * **This is provenance, not decoration, and leaving it out is a correctness problem rather than a cosmetic one.** Changing the ayanamsa moves every longitude by up to a degree, which is enough to put a graha in a different rashi. A chart rendered without saying which frame produced it therefore cannot be reconciled against any other calculator, and a reader who changed the frame by accident concludes the component is broken rather than that they are comparing two different skies. Echoing it is the whole reason the response carries it.
 *
 * Renders nothing when the payload has no frame, so it is safe to call unconditionally on a response type that predates the field.
 *
 * The label comes from {@link formatAyanamsa}, so `raman` reads "B.V. Raman" and `kp-newcomb` keeps its initialism, and a frame added upstream cannot arrive as a bare enum without a test failing.
 *
 * @example
 * ```ts
 * static styles = [baseStyles, frameCaptionStyles, css`...`];
 * // in renderData:
 * ${renderFrameCaption(this.effectiveLang(), d.frame, this.translator)}
 * ```
 */
export declare function renderFrameCaption(locale: string | undefined, frame: SiderealFrame | undefined, t: Translate): TemplateResult | typeof nothing;
/**
 * The school conventions a Chinese-metaphysics response was computed under.
 *
 * @remarks
 * Structural rather than imported from one response type, because every BaZi-family schema carries the same object and the feng-shui ones carry the year rule alone. Each field is optional here so a component can pass `d.conventions` whatever subset its own endpoint echoes.
 */
export interface ChineseConventions {
    dayBoundary?: string;
    yearBoundary?: string;
    hourClock?: string;
}
/**
 * One line naming the school rules a chart was cast under.
 *
 * @remarks
 * **A sibling of {@link renderFrameCaption}, and it exists for the same reason.** Three splits decide a chart for a birth near a boundary: which instant starts the day, which starts the year, and which clock the hour is read from. Two teachers using different rules get different pillars for the same birth, so a chart printed without saying which rules produced it cannot be reconciled against any other chart, and a reader holding two of them concludes one is wrong rather than that they answer different questions. Echoing them is why the response carries them.
 *
 * Each value NAMES a rule and carries no localized partner, so it prints through the published field-label option for its field (`Beginning of Spring` for `li-chun`, `Civil clock` for `clock`) with the wire identifier kept in the title, the way any request option is shown; a payload with no word for it prints the identifier humanized. The three labels beside them are plain compositional language rather than terms of art, which is why they are catalogued where the rest of a Chinese-metaphysics card is not.
 *
 * Renders nothing for a response that echoes none, so it is safe to call unconditionally.
 */
export declare function renderConventionsCaption(conventions: ChineseConventions | undefined, t: Translate, lang: string | undefined): TemplateResult | typeof nothing;
/** One frame in a response computed across several: the frame itself, the instant it was read at, and the sections it decided. */
export interface GoverningFrame extends SiderealFrame {
    at?: string;
    governs?: readonly string[];
}
/**
 * Every frame a multi-frame response was computed in, one line each.
 *
 * @remarks
 * Separate from {@link renderFrameCaption} rather than a widening of it, because the two answer different questions: one chart cast in one frame needs the frame NAMED, while a response assembled from several needs each frame tied to the part of the answer it decided. Collapsing these to a single caption would print one ayanamsa over sections two others produced, which is the provenance failure the caption exists to prevent.
 *
 * The label comes from {@link formatAyanamsa}, the same source the single-frame caption reads, so a frame added upstream reads the same in both.
 */
export declare function renderFrameProvenance(locale: string | undefined, frames: Record<string, GoverningFrame | undefined> | undefined, t: Translate): TemplateResult | typeof nothing;