@instruments/materialgraph 0.28.0 → 0.30.0

package/codes-types.d.ts

@@ -1,325 +0,0 @@
-/**
- * Hand-mirrored wire types for the advisory building-code surface
- * (`GET /api/v1/codes/context`, `GET /api/v1/codes/requirements`,
- * `POST /api/v1/codes/advisory` — MG-433, MG-674).
- *
- * Like the rest of the SDK these interfaces have NO runtime dependency on any
- * `@materialgraph/*` package — they mirror the `codeAdvisoryInputSchema` /
- * `codeAdvisoryResultSchema` Zod contracts the route is built from. Response
- * enums follow the SDK's TOLERANT-PARSING contract (widened with `OpenEnum` so a
- * new server value still type-checks); `requirement.scale` is an open IBC-scale
- * id and `caveat` is the AHJ advisory sentence, both read as plain strings.
- *
- * ADVISORY ONLY: every verdict and the envelope carry the AHJ caveat — this is
- * model code as adopted, never a legal determination.
- */
-import type { VariantId } from "./identifiers.js";
-import type { FilterGroups } from "./list-variants-types.js";
-import type { OpenEnum } from "./types.js";
-/**
- * A code context: the space the registry is queried for.
- *
- * CONDITIONAL REQUIREMENT — two axes must END UP resolved, and each may be
- * stated OR correlated. Every field below is optional in the type because the
- * validator resolves them per axis independently; the rule it enforces at
- * runtime is:
- *
- * > occupancyGroup, resolved = `input.occupancyGroup` ?? correlate(roomType)
- * > spaceType,      resolved = `input.spaceType`      ?? correlate(roomType)
- *
- * and either resolving to nothing is a 400, verbatim:
- *
- * - `"An occupancy group is required — state occupancyGroup, or a roomType that
- *   correlates to one."`
- * - `"A space type is required — state spaceType, or a roomType that correlates
- *   to one."`
- * - `"Room type \"{roomType}\" does not correlate to an IBC occupancy group —
- *   state occupancyGroup explicitly."`
- * - `"Room type \"{roomType}\" does not correlate to a Table 803.13 finish
- *   location — state spaceType explicitly."`
- *
- * So: give `occupancyGroup` + `spaceType`, or give `roomType` and let both
- * correlate, or mix them — an explicit axis always wins over a correlated one,
- * and a room is only consulted for an axis you did not state. Correlation never
- * guesses: a room that maps to neither is an error naming the axis, and the
- * response's `resolvedContext` is where you audit what was inferred for you.
- *
- * Discover every accepted value — jurisdictions, occupancy groups, finish
- * locations, and the room correlations themselves — from
- * {@link CodesClient.context}. Nothing here should be hardcoded.
- */
-export type CodeContextRequest = {
-    /** A seeded jurisdiction id (e.g. `"us-tx"`); an unknown id is a 400 listing the seeded set. */
-    jurisdictionId: string;
-    /**
-     * The IBC occupancy group for the space (e.g. `"I-2"` hospital, `"A-2"`
-     * restaurant). Required unless `roomType` correlates to one. An uncovered
-     * group is a 400 listing the covered ones.
-     */
-    occupancyGroup?: string;
-    /**
-     * The finish location: `"corridors"`, `"exit_stairs_passageways"`, or
-     * `"rooms_enclosed_spaces"`. Required unless `roomType` correlates to one.
-     */
-    spaceType?: string;
-    /**
-     * A `room` term id (e.g. `"hotel_room"`) to correlate the regulatory axes
-     * from. Explicit `occupancyGroup` / `spaceType` always win. A room that
-     * correlates to neither axis is a 400 naming the axis — never a guess.
-     */
-    roomType?: string;
-    /** Whether the space is sprinklered — relaxes several fire-finish floors. No default. */
-    sprinklered: boolean;
-};
-export type CodeAdvisoryInput = {
-    /**
-     * 1–100 opaque variant ids to badge, echoed back in `results` in this exact
-     * order and cardinality (duplicates are echoed, never collapsed). Preserve
-     * them verbatim — never parse or construct one.
-     */
-    variantIds: VariantId[];
-} & CodeContextRequest;
-/** The resolved jurisdiction the verdicts were evaluated against. */
-export type CodeAdvisoryJurisdiction = {
-    id: string;
-    name: string;
-    codeFamily: string;
-    edition: string;
-    adoptionNote: string;
-};
-/** The echoed evaluation context (the space the badges apply to). */
-export type CodeAdvisoryContext = {
-    occupancyGroup: string;
-    spaceType: string;
-    sprinklered: boolean;
-};
-/**
- * What one material is, and therefore what it was held to. `dimensions` are the
- * regulatory dimensions the material can be scored on; `basis` names which
- * source(s) produced them: a mapped `productTypeId`, `applicationIds`, both, or
- * `unresolved` when neither yielded anything. `unresolved` does NOT mean the
- * material is answerable for nothing — it means we could not tell what the
- * material is, so every requirement the space imposes was scored against it and
- * `notApplicable` on the result is empty. That is a coverage gap in the
- * product-type/application map, not a narrow material. A short `requirements`
- * list under `product_type` / `application` / `both` is a genuine intersection;
- * a full list under `unresolved` is the map falling short.
- */
-export type MaterialCodeProfile = {
-    /** The variant's accepted primary product type, or null if it has none. */
-    productTypeId: string | null;
-    /** The variant's accepted `applications` terms, as stored. */
-    applicationIds: string[];
-    /** Regulatory dimensions this material can be held to. Empty ONLY when `basis` is `unresolved`. */
-    dimensions: OpenEnum<"fire" | "floor" | "slip" | "decorative">[];
-    basis: OpenEnum<"product_type" | "application" | "both" | "unresolved">;
-};
-/** Why one requirement the space imposes was excluded from this material's `requirements`. */
-export type CodeRequirementExclusion = {
-    requirementId: string;
-    dimension: OpenEnum<"fire" | "floor" | "slip" | "decorative">;
-    reason: OpenEnum<"not_a_material_dimension">;
-    /** One readable line, e.g. `"Slip resistance is not a dimension wallcovering answers for."`. */
-    detail: string;
-};
-/** The threshold one requirement imposes: a class floor and/or a numeric floor. */
-export type CodeRequirementThreshold = {
-    /** The IBC classification scale this requirement is measured on (open id). */
-    scale: string;
-    /** The minimum acceptable class on `scale`, or null when only a numeric floor applies. */
-    minClass: string | null;
-    /** A numeric floor (e.g. a DCOF minimum), or null when only a class floor applies. */
-    numericFloor: {
-        metric: string;
-        value: number;
-        unit: string;
-    } | null;
-};
-/**
- * The accepted fact a verdict was decided from — null when the material carried
- * none, which is exactly the case that produces `verdict: "unknown"`.
- *
- * `confidence` and `sourceBasis` are the strength of the fact, not of the code
- * reading. Quote them whenever you quote the badge: a `meets` resting on a
- * `derived` value at low confidence is a materially different statement from one
- * resting on a `tested` figure.
- */
-export type CodeRequirementEvidence = {
-    attributeId: OpenEnum<"fire_classifications" | "slip_resistance_dcof">;
-    value: string;
-    confidence: number | null;
-    sourceBasis: string | null;
-};
-/** One requirement badged against one material. */
-export type CodeRequirementVerdict = {
-    requirementId: string;
-    dimension: OpenEnum<"fire" | "floor" | "slip" | "decorative">;
-    section: string;
-    requirement: CodeRequirementThreshold;
-    /**
-     * What may be said about this material against this requirement:
-     *  - `meets` — a defensible fact clears the threshold. Advisory, still not a
-     *    determination.
-     *  - `shortfall` — a defensible fact FAILS to clear it. A real negative.
-     *  - `unknown` — no defensible fact maps onto `scale`. NOT a failure and NOT a
-     *    pass: "no comparable rating on file". Never present it as either.
-     */
-    verdict: OpenEnum<"meets" | "shortfall" | "unknown">;
-    evidence: CodeRequirementEvidence | null;
-    /** The AHJ advisory caveat — model code as adopted, never a legal determination. */
-    caveat: string;
-};
-/**
- * One candidate's requirement verdicts folded into a single status and sentence.
- * A shortfall outranks an unknown, and an unknown NEVER rolls up to a pass:
- * `not_applicable` (nothing applied) is deliberately distinct from `meets`.
- */
-export type CodeAdvisorySummary = {
-    /**
-     * The rolled-up card, and what each token licenses:
-     *  - `meets` — every applicable requirement was `meets`. Advisory pass.
-     *  - `shortfall` — at least one requirement failed on real evidence. Blocking.
-     *  - `unverified` — nothing failed, but something is `unknown`. COMMON, and
-     *    never a pass: it means "no comparable rating is on file". Show it as an
-     *    open question, not a green tick.
-     *  - `not_applicable` — the space imposes nothing this material answers for.
-     *    Deliberately distinct from `meets`: it is silence, not approval.
-     */
-    status: OpenEnum<"meets" | "shortfall" | "unverified" | "not_applicable">;
-    /** One deterministic sentence naming what failed, e.g. `"Falls short on fire for A-2 corridors."`. */
-    headline: string;
-    shortfallDimensions: OpenEnum<"fire" | "floor" | "slip" | "decorative">[];
-    unverifiedDimensions: OpenEnum<"fire" | "floor" | "slip" | "decorative">[];
-};
-/** Per-variant advisory outcome, in input order. */
-export type CodeAdvisoryVariantResult = {
-    /** Opaque — echoed verbatim from `variantIds`, in that position. */
-    variantId: VariantId;
-    /** `evaluated` when the id resolved; `unknown_variant` (with `requirements: []`) when it did not. */
-    state: OpenEnum<"evaluated" | "unknown_variant">;
-    /** What this material is and what it was scored against. Null only for `state: "unknown_variant"`. */
-    material: MaterialCodeProfile | null;
-    /** Verdicts for the requirements this material is answerable for — the answerable subset only. */
-    requirements: CodeRequirementVerdict[];
-    /** Requirements the space imposes that this material cannot answer. Empty when nothing was excluded. */
-    notApplicable: CodeRequirementExclusion[];
-    /** The rolled-up card, or null for an id that resolved to nothing. */
-    summary: CodeAdvisorySummary | null;
-};
-/** The `POST /api/v1/codes/advisory` envelope — per-variant, per-requirement verdicts. */
-export type CodeAdvisoryResponse = {
-    jurisdiction: CodeAdvisoryJurisdiction;
-    /** The context AS SUPPLIED, echoed verbatim. */
-    context: CodeAdvisoryContext;
-    /** The canonical axes the registry was queried with, and where they came from. */
-    resolvedContext: ResolvedCodeContext;
-    /** The AHJ advisory caveat, at the envelope level too. */
-    caveat: string;
-    results: CodeAdvisoryVariantResult[];
-};
-/** Where a resolved axis came from: stated outright, or correlated from a room type. */
-export type ResolvedCodeContext = {
-    jurisdictionId: string;
-    occupancyGroup: string;
-    /** The canonical finish-location term id the registry was queried with. */
-    spaceType: string;
-    sprinklered: boolean;
-    basis: OpenEnum<"explicit" | "derived_from_room">;
-    /** The `room` term the axes were correlated from, or null. */
-    roomType: string | null;
-};
-/**
- * How far a jurisdiction's rows have been reviewed against that AHJ's own tables.
- *
- *  - `thorough` — reviewed against this jurisdiction's own adopted tables.
- *  - `model_baseline` — UNAMENDED model IBC stood in, because that AHJ's own
- *    amendments have not been reviewed. Local amendments may be stricter, so
- *    say "per model IBC" rather than naming the jurisdiction as the authority.
- */
-export type CodeCoverageTier = OpenEnum<"thorough" | "model_baseline">;
-export type CodeJurisdictionSummary = {
-    id: string;
-    name: string;
-    codeFamily: string;
-    edition: string;
-    coverage: CodeCoverageTier;
-    /** One honest line on how the model code actually applies in this jurisdiction. */
-    adoptionNote: string;
-};
-/** The `GET /api/v1/codes/context` envelope — the vocabulary for stating a context. */
-export type CodeContextResponse = {
-    jurisdictions: CodeJurisdictionSummary[];
-    occupancyGroups: {
-        id: string;
-        label: string;
-    }[];
-    finishLocations: {
-        id: string;
-        label: string;
-        shortLabel: string;
-    }[];
-    dimensions: {
-        id: OpenEnum<"fire" | "floor" | "slip" | "decorative">;
-        label: string;
-        description: string;
-        /** The MaterialGraph attribute this dimension is scored against. */
-        attributeId: string;
-    }[];
-    scales: {
-        id: string;
-        label: string;
-        detail: string;
-        /** Ordered BEST FIRST: index 0 outranks index 1. */
-        classes: string[];
-    }[];
-    /** `room` → regulatory axes. `null` where the registry refuses to correlate. */
-    roomCorrelations: {
-        roomType: string;
-        label: string;
-        occupancyGroup: string | null;
-        finishLocation: string | null;
-    }[];
-    /** The AHJ advisory caveat. */
-    caveat: string;
-};
-/** One requirement a context imposes, independent of any candidate material. */
-export type CodeRequirementListing = {
-    requirementId: string;
-    dimension: OpenEnum<"fire" | "floor" | "slip" | "decorative">;
-    /** The code section this demand is cited from. */
-    section: string;
-    attributeId: string;
-    requirement: CodeRequirementThreshold;
-    /** One readable line, e.g. `"Class A or better · ASTM E84 / UL 723"`. */
-    label: string;
-};
-/** Why one requirement the context imposes could not become a `list_variants` filter predicate. */
-export type CodeSpecFilterUnexpressible = {
-    requirementId: string;
-    dimension: OpenEnum<"fire" | "floor" | "slip" | "decorative">;
-    reason: OpenEnum<"no_matchable_tokens" | "unsupported_scale" | "no_floor">;
-    /** One readable line naming why, e.g. `"Scale ... has no ordinal definition..."`. */
-    detail: string;
-};
-/**
- * The `GET /api/v1/codes/requirements` envelope. An empty `requirements` array
- * means the registry holds nothing for this context — it is not a pass.
- */
-export type CodeRequirementsResponse = {
-    jurisdiction: CodeJurisdictionSummary;
-    context: ResolvedCodeContext;
-    requirements: CodeRequirementListing[];
-    /**
-     * The same requirements as a ready-to-use `list_variants` `filters` group
-     * (MG-2222, `{terms, numbers, presence}`) — pass it straight through as
-     * `listVariants({ filters })`.
-     * `null` when nothing here is filterable; read `specFilterUnexpressible`
-     * for why, not an empty `requirements` list.
-     */
-    specFilter: FilterGroups | null;
-    /** The dimensions `specFilter` actually narrows on — a subset of `requirements`' dimensions. */
-    specFilterApplied: OpenEnum<"fire" | "floor" | "slip" | "decorative">[];
-    /** Requirements that could not be turned into a filter predicate, and why. */
-    specFilterUnexpressible: CodeSpecFilterUnexpressible[];
-    caveat: string;
-};

package/colour-aggregate-types.d.ts

@@ -1,163 +0,0 @@
-/**
- * Wire types for the colour AGGREGATE surface — `GET /api/v1/colours/profiles`
- * and `GET /api/v1/colours/stats`.
- *
- * Kept out of `types.ts` for the same reason `material-types.ts` and
- * `codes-types.ts` are: the shared mirror is at its source-size budget. Same
- * tolerant-parsing contract as the rest of the mirror — response enums are
- * widened so a new server value still type-checks.
- */
-import type { OpenEnum } from "./types.js";
-/**
- * Which taxonomy tier a colour profile's `categoryKey` names — or `"merged"`,
- * where the key is a composite over a caller-defined key set rather than a
- * taxonomy node.
- */
-export type CategoryTier = OpenEnum<"group" | "type" | "merged">;
-/** How the endpoint picks which colours to keep. */
-export type ColourProfileSelect = OpenEnum<"frequency" | "diverse">;
-/** One representative colour bucket of a category. */
-export type CategoryColour = {
-    hex: string;
-    oklab: {
-        l: number;
-        a: number;
-        b: number;
-    };
-    variantCount: number;
-    /** This bucket's share of the category's coloured variants, 0–1. */
-    proportion: number;
-};
-export type CategoryColourProfile = {
-    categoryKey: string;
-    level: CategoryTier;
-    name: string;
-    path: string;
-    /**
-     * Under `groupBy: "merged"`, the requested keys in composite-key order, so
-     * `categoryKey` never has to be split. Absent on a single-category profile.
-     */
-    members?: string[];
-    variantCount: number;
-    avgLightness: number;
-    avgChroma: number;
-    colours: CategoryColour[];
-};
-/**
- * The snapshot a profile response was computed from. Compare `variantCount`
- * against `colours/stats`' `corpus.withColour` to see how complete the
- * underlying materialized view currently is, and `refreshedAt` for its age.
- */
-export type CategoryColourProfilesBasis = {
-    variantCount: number;
-    refreshedAt: string | null;
-};
-export type CategoryColourProfilesResponse = {
-    profiles: CategoryColourProfile[];
-    basis: CategoryColourProfilesBasis;
-};
-/** Request parameters for `colours.profiles()`. */
-export type ColourProfilesParams = {
-    /** 1–8 category keys, at the tier named by `groupBy`. */
-    productTypeIds: readonly string[];
-    /**
-     * `"group"` merges each group's leaf product types into one palette;
-     * `"merged"` merges EVERY key's leaves into a single combined palette.
-     */
-    groupBy?: "group" | "type" | "merged";
-    /** Representative colours per category, 1–64. */
-    topN?: number;
-    /** `"diverse"` maximises visual distinctness instead of frequency. */
-    select?: "frequency" | "diverse";
-};
-export type ColourStatsCorpus = {
-    variants: number;
-    withColour: number;
-    /** `withColour / variants`, 0–1. */
-    coverage: number;
-};
-export type ColourStatsFamily = {
-    id: string;
-    label: string;
-    variants: number;
-    brands: number;
-};
-export type ColourStatsGroup = {
-    key: string;
-    name: string;
-    productTypes: number;
-    variants: number;
-};
-/**
- * One cell of the brand x category x colour-family matrix — the shape that
- * answers questions no single dimension can, such as "how many whites does
- * Benjamin Moore offer in paint".
- */
-export type ColourStatsRow = {
-    /** Opaque brand id — the join key for brand reads. Never parse it. */
-    brandId: string;
-    brandSlug: string;
-    brandName: string;
-    /**
-     * Product-type key. NULL means these variants carry NO accepted primary
-     * product type — a real population, kept so the matrix sums to the corpus,
-     * not an error and not a residual bucket.
-     */
-    categoryKey: string | null;
-    family: string;
-    /**
-     * Distinct variants at this (brand, category, family) carrying an ACCEPTED
-     * `colour_family`. Not every variant of the brand.
-     */
-    variants: number;
-};
-/** How to narrow the matrix. Passing ANY of these asks for `rows`. */
-export type ColourStatsParams = {
-    /** `"brand,category"` — ask for the whole matrix, unscoped. */
-    groupBy?: string;
-    brandId?: string;
-    brandSlug?: string;
-    /**
-     * A product-type key, or the literal `"null"` for the unclassified
-     * population. Omitting it means every category — a different question.
-     */
-    categoryKey?: string;
-    family?: string;
-    limit?: number;
-};
-/** Where each section came from, how fresh it is, and what it does NOT answer. */
-export type ColourStatsBasis = {
-    corpus: string;
-    families: string;
-    groups: string;
-    groupsRefreshedAt: string | null;
-    groupsVariantCount: number;
-    /**
-     * Where `rows` came from, its freshness, and what it EXCLUDES — present only
-     * when `rows` is. Read it: the matrix deliberately omits Samplize, which is a
-     * sampling channel printing other manufacturers' colours rather than a maker.
-     */
-    rows?: string;
-    omissions: string[];
-};
-export type ColourStatsResponse = {
-    corpus: ColourStatsCorpus;
-    families: ColourStatsFamily[];
-    groups: ColourStatsGroup[];
-    /**
-     * The brand x category x colour-family matrix. Present ONLY when you asked
-     * for it; ABSENT means nobody asked, never that the matrix is empty.
-     *
-     * `families` above is NOT scoped by the same parameters and stays
-     * platform-wide under all of them. Scoped counts live here.
-     */
-    rows?: ColourStatsRow[];
-    /**
-     * Rows matching your query BEFORE the response cap — the honest total.
-     * A shortfall against `rows.length` means `rows` is a prefix.
-     */
-    rowsMatched?: number;
-    /** TRUE when the matrix exceeded the cap and `rows` is a prefix. */
-    rowsTruncated?: boolean;
-    basis: ColourStatsBasis;
-};

package/coordinate-client.d.ts

@@ -1,23 +0,0 @@
-/**
- * The COORDINATION lens: given several materials already chosen, what completes
- * them. A thin wrapper over the shared {@link HttpTransport};
- * `MaterialGraphClient.coordinate` delegates here.
- *
- * Extracted from `client.ts`, which sits above the repository's source-size
- * limit, in the same per-lens shape as `brands-client` / `codes-client` /
- * `colours-client`. Behaviour is unchanged.
- */
-import type { HttpTransport } from "./http-transport.js";
-import type { CoordinateInput, CoordinateResponse } from "./types.js";
-/**
- * THE QUESTION: "here is my whole scheme so far — what completes it?" The
- * multi-seed form of `pairings`: lift is SUMMED across seeds, so a companion
- * suiting one pick ranks below one suiting several. Returns demand-lift-ranked
- * companions with colour swatches and an annotate-only `colourFit` that never
- * reorders in v1.
- *
- * Instead use `pairings` for a single material, and `colours.palette()` when the
- * scheme is COLOURS rather than materials. Check `unresolved` before presenting:
- * a reference that resolved to nothing is named there, not dropped.
- */
-export declare const coordinate: (transport: HttpTransport, input: CoordinateInput, signal?: AbortSignal) => Promise<CoordinateResponse>;

package/coordinate-client.js

@@ -1,13 +0,0 @@
-import { resolveOperation } from "./operations.js";
-/**
- * THE QUESTION: "here is my whole scheme so far — what completes it?" The
- * multi-seed form of `pairings`: lift is SUMMED across seeds, so a companion
- * suiting one pick ranks below one suiting several. Returns demand-lift-ranked
- * companions with colour swatches and an annotate-only `colourFit` that never
- * reorders in v1.
- *
- * Instead use `pairings` for a single material, and `colours.palette()` when the
- * scheme is COLOURS rather than materials. Check `unresolved` before presenting:
- * a reference that resolved to nothing is named there, not dropped.
- */
-export const coordinate = async (transport, input, signal) => await transport.requestJson(resolveOperation("coordinate_materials"), { body: input, signal });

package/demand-batch-types.d.ts

@@ -1,118 +0,0 @@
-/**
- * Wire types for BATCH candidate demand enrichment — `POST /api/v1/demand/batch`.
- *
- * Split out of `types.ts` for the repository's source-file size budget, the same
- * reason `material-types.ts` and `catalog-discovery-types.ts` sit beside it;
- * re-exported from `types.ts`, so importers see no difference.
- *
- * THE LENS: this answers "how much is each of these already-chosen materials
- * actually specified?" — enrichment over a bounded id list you already hold. It
- * never resolves, ranks, reorders or discovers. Use
- * {@link MaterialGraphClient.demand} for one material named in free text,
- * {@link MaterialGraphClient.pairings} for what goes WITH a material, and
- * {@link MaterialGraphClient.search} to find candidates in the first place.
- */
-import type { VariantId } from "./identifiers.js";
-import type { DemandMomentum, DemandQuarter, DemandSignal, OpenEnum } from "./types.js";
-/**
- * Body for `POST /api/v1/demand/batch` — enrich 1–48 already-selected candidate
- * ids with their real specification demand, in input order and cardinality.
- */
-export type DemandBatchInput = {
-    /** 1–48 canonical variant ids. Order AND cardinality are preserved — duplicates are echoed, never collapsed. */
-    variantIds: VariantId[];
-    /** The behavioural signal to read demand from. Defaults to `sampled` (order co-occurrence) server-side. */
-    signal?: DemandSignal;
-    /** Optional declared context (e.g. `{ projectType: "hospitality" }`) — echoed for provenance, never used to rank or filter. */
-    context?: Record<string, string>;
-};
-/** Headline population behind the metric — this variant's own counts. */
-export type DemandBatchPopulation = {
-    specCount: number;
-    projectCount: number;
-    customerCount: number;
-};
-/** The consideration→specification funnel (project-grain; `exclusionRate` is annotate-only). */
-export type DemandBatchFunnel = {
-    consideredProjects: number;
-    specifiedProjects: number;
-    excludedCount: number;
-    exclusionRate: number;
-};
-/** Per-result guardrail status — present on `internal` (`mg:admin`) results only. */
-export type DemandBatchEvidence = {
-    belowPrivacyFloor: boolean;
-    belowQualityFloor: boolean;
-    suppressedForPublic: boolean;
-};
-/** A variant that carries a usable demand signal. */
-export type DemandBatchAvailableResult = {
-    variantId: VariantId;
-    state: "available";
-    population: DemandBatchPopulation;
-    /** Exact per-quarter counts (sparse — zero-spec quarters are absent). */
-    intervals: DemandQuarter[];
-    momentum: DemandMomentum;
-    /** The funnel; null when the signal is not `sampled` or no `considered` row/session exists. */
-    funnel: DemandBatchFunnel | null;
-    /** Exact guardrail evidence for `internal` callers; null for public. */
-    evidence: DemandBatchEvidence | null;
-};
-/**
- * A variant with a stats row that is below the public quality floor. We HAVE a
- * reading and are declining to publish it — not a claim that nobody specifies it.
- */
-export type DemandBatchInsufficientResult = {
-    variantId: VariantId;
-    state: "insufficient_data";
-};
-/**
- * A variant with no stats — indistinguishable from a privacy-suppressed one for
- * public callers, and therefore never reportable as "nobody specifies this".
- */
-export type DemandBatchNoSignalResult = {
-    variantId: VariantId;
-    state: "no_signal";
-};
-/** A requested id that resolves to no real variant. */
-export type DemandBatchUnknownResult = {
-    variantId: VariantId;
-    state: "unknown_variant";
-};
-/**
- * One discriminated result per input id, in input order and cardinality.
- *
- * ABSENT IS NOT ZERO: only `available` carries numbers. The other three states
- * each mean "no number to report", for three different reasons, and none of them
- * licenses "this material is not specified" — see each member.
- */
-export type DemandBatchResult = DemandBatchAvailableResult | DemandBatchInsufficientResult | DemandBatchNoSignalResult | DemandBatchUnknownResult;
-/** The `POST /api/v1/demand/batch` envelope. */
-export type DemandBatchResponse = {
-    /** The completed ingestion-session id these counts were mined in (the dataset generation). */
-    generationId: string;
-    metric: "specification_demand";
-    /** The metric universe — the window and signal the counts are scoped to. */
-    universe: {
-        window: "trailing_36mo";
-        signal: DemandSignal;
-        description: string;
-    };
-    /** The guardrail status under which `results` were projected. */
-    guardrail: {
-        audience: OpenEnum<"public" | "internal">;
-        minProjectCount: number;
-        minCustomerCount: number;
-    };
-    /** Outcome tallies over `results` — never a denominator for the metric. */
-    coverage: {
-        requested: number;
-        available: number;
-        insufficientData: number;
-        noSignal: number;
-        unknownVariant: number;
-    };
-    /** The echoed declared context, or null when none was supplied. */
-    context: Record<string, string> | null;
-    results: DemandBatchResult[];
-};