/**
 * @copyright Sister Software
 * @license AGPL-3.0
 * @author Teffen Ellis, et al.
 *
 *   `fcc-bdc`: FCC Broadband Data Collection (BDC) — Fabric-derived location consumer.
 *
 *   The first member of Phase 1.6's "adversarial sources" class. BDC ships the public-domain US
 *   broadband-serviceable-location (BSL) fabric: ~120M addresses keyed by stable `location_id`,
 *   carrying `address_primary` + `city` + `state` + `zip` + `zip_suffix`. Compared to the clean
 *   gazetteer rows from WOF / TIGER / BAN, BDC carries the chaos of address data that has passed
 *   through several layers of human entry + automated geocoding + revision: abbreviation drift,
 *   inconsistent unit designators, "RR" / "HC" / "PSC" rural-route shapes, embedded apartment /
 *   suite numbers that did not survive the address parser cleanly. This is the highest-signal,
 *   hardest-to-normalize address corpus in the federal public-domain catalog.
 *
 *   Following the `tiger` / `wof-admin` pattern, this adapter consumes a SQLite database the operator
 *   pre-builds via the isp-nexus BDC ETL (`/srv/isp-nexus/sync/fcc/bdc/`) or any equivalent
 *   host-side pipeline. The mailwoman side does not download or parse the raw CSV/ZIP distribution
 *   directly — that keeps the adapter narrow and the BDC ingest pluggable.
 *
 *   The SQLite schema is documented in README.md and modeled after `NTIARecord`
 *   (`isp-nexus/fcc/bdc/data-collection.ts`): one row per `location_id`. The adapter splits
 *   `address_primary` into `house_number` (leading numeric prefix, if any) + `street` (everything
 *   after), and combines `zip` + `zip_suffix` into the canonical USPS `postcode` slot.
 *
 *   One CanonicalRow per fabric record. Unlike `tiger` (multiple postcode variants per segment) or
 *   `wof-admin` (multiple hierarchy variants per place), BDC records already represent fully
 *   specified addresses; no fan-out is warranted. Adversarial composition (Phase 1.6 §2.1) is the
 *   mechanism for deriving multiple training rows per BDC record.
 *
 *   License: stamped `"Public Domain"` per the BDC fabric's US federal-government distribution terms.
 *   The CostQuest Fabric source data has its own license; consumers who substitute that path should
 *   re-stamp accordingly.
 */
import type { CorpusAdapter } from "@mailwoman/corpus/types";
/**
 * Registry id for this adapter. Stamped into every row it emits, so a corpus record can be traced back to the dataset
 * it came from.
 */
export declare const FCC_BDC_ADAPTER_ID = "fcc-bdc";
/**
 * License carried by this source (Public Domain), attached to each row so downstream consumers inherit the terms rather
 * than having to look them up.
 */
export declare const FCC_BDC_DEFAULT_LICENSE = "Public Domain";
/**
 * Combine `zip` + optional `zip_suffix` into the canonical USPS postcode surface form.
 *
 * NTIARecord doc is ambiguous about whether `zip_suffix` is the 4-digit extension alone or the full ZIP+4 string. This
 * handles both:
 *
 * - Bare 4-digit extension (`zip="94103"`, `zip_suffix="1234"`) → `"94103-1234"`
 * - Already-joined form (`zip_suffix="94103-1234"`) → returned as-is
 * - No suffix → bare `zip`
 *
 * Empty / whitespace-only suffix is treated as missing.
 */
export declare function buildPostcode(zip: string, suffix: string | null): string;
/**
 * Build a BDC adapter. Pure factory so multiple instances can be created in tests.
 */
export declare function createFccBdcAdapter(): CorpusAdapter;
/**
 * The configured adapter instance registered with the corpus builder.
 */
export declare const fccBdcAdapter: CorpusAdapter;
//# sourceMappingURL=adapter.d.ts.map