/**
 * Texas Data Privacy and Security Act (TDPSA / HB 4) Compliance Pack
 *
 * Regulation: Texas Business and Commerce Code Chapter 541
 *             (enacted via HB 4, 88th Texas Legislature, 2023)
 *             Also known as TDPSA (Texas Data Privacy and Security Act)
 *
 * Jurisdiction: US-TX (Texas)
 * Regulator: Texas Attorney General (enforcement authority)
 *
 * Effective date: 1 July 2024
 *
 * Scope:
 *   Applies to controllers that conduct business in Texas OR produce products /
 *   services consumed by Texas residents AND:
 *   (a) process or sell personal data, AND
 *   (b) are not a small business as defined by the US Small Business Administration
 *       (size thresholds by industry -- tenant configuration required to verify).
 *
 *   Exemptions: entities governed by GLBA, HIPAA, FERPA, COPPA, FCRA; Texas
 *   state agencies; financial institutions covered by Texas Finance Code; non-profit
 *   organizations; institutions of higher education.
 *
 * Key obligations:
 *   1. Consumer rights: access, correction, deletion, portability, opt-out of
 *      sale / targeted advertising / profiling for significant decisions.
 *   2. Sensitive data: opt-in consent before processing biometric, health,
 *      mental health, immigration status, religious beliefs, sexual orientation,
 *      citizenship status, or children's data.
 *   3. Child data: opt-in required for data of known children under 13 and
 *      parental consent for 13-17 (where applicable, consistent with COPPA).
 *   4. Data Protection Impact Assessments (DPIA): required for high-risk
 *      processing activities (targeted advertising, sale of personal data,
 *      sensitive data, ADM profiling, children's data).
 *   5. Vendor contracts: data processing agreements with processors covering
 *      controller instructions, confidentiality, breach notification, deletion.
 *   6. Biometric data: additional consent requirements beyond general sensitive data.
 *   7. Privacy notice: clear, conspicuous, reasonably accessible notice.
 *
 * Retention:
 *   As long as reasonably necessary for purpose; mandatory deletion on consumer request.
 *
 * Incident:
 *   Breach affecting Texas residents: AG notification (typically 60 days per
 *   Texas Business & Commerce Code §521.053 -- verify against current rules);
 *   affected consumers per breach notification provisions.
 *
 * @connexum/ai-governance
 */
import { CompliancePack } from './index';
import { CategoryClassifiers } from '../classification/pack-driven-classifier';
/**
 * F-NEW-VERA-PACK-C4-02 (LOW): Texas HB 4 jurisdiction-tagging note.
 *
 * All 6 substantive classifiers in this pack require explicit "texas", "TDPSA",
 * or "HB 4" markers in the raw input text. In production deployments where
 * jurisdiction is carried in session metadata (e.g., user profile, IP geolocation,
 * customer consent record, or operator configuration) rather than injected into
 * every message, classifiers will miss Texas-resident data.
 *
 * DEPLOYER ACTION REQUIRED: Inject the jurisdiction tag ("texas TDPSA consumer")
 * at the classifier input boundary -- either by prepending it to the input string
 * before calling the data-classifier, or by configuring the operator's
 * classification pipeline to merge session metadata into the classifier payload.
 *
 * Proof-of-concept: TEXAS_RESIDENT_PERSONAL_DATA accepts a ClassificationContext
 * parameter. If context carries a jurisdictionCode extension property that resolves
 * to 'texas', 'tdpsa', or 'us-tx' (case-insensitive), the classifier fires regardless
 * of whether the raw input contains a Texas marker. Operators who configure a
 * jurisdictionCode in their context pipeline can use this fallback. To extend metadata
 * awareness to all classifiers, apply this pattern per your jurisdiction strategy.
 */
export declare const TEXAS_HB4_CATEGORY_CLASSIFIERS: CategoryClassifiers;
export declare const TEXAS_HB4_PACK: CompliancePack & {
    categoryClassifiers: CategoryClassifiers;
};
//# sourceMappingURL=texas-hb4.d.ts.map