Cryptoassets Regulatory Intelligence cryptoassets.gi
US-CT v13.3.0
content: ai_generated legal review: never_reviewed (informational) publication gate: 1 failing15 sources retrieved model claude-sonnet-5 · 2026-08-06

Connecticut, USA

US-CT schema crypto-v2.0.0 trajectory: not yet assessedregulatedoverlaps: FIM, WPM

Last updated · 8 categories · 25 sourced findings · 21 sources in the cumulative register

8Categoriesbaseline.
25Findings.claims[]
5Tier-1 sourcesrun_metadata.t1_source_count
Confidence mix (sums to 8 rendered categories; click to filter)
No categories moved this cycle.

Jurisdiction lead brief

Lead Signal

A Challenger-fold correction against the official Connecticut General Assembly legislative summary of Public Act 25-66 (H.B. 7082) has overturned what had been reported as a regulatory gap. Connecticut money-transmission licensees dealing in virtual currency must now be understood to operate under a state-specific custody regime: the law requires that customer virtual currency be held only with approved custodians, and it deems any virtual currency held by a licensee to constitute a property interest of the licensee's claimants in the event of insolvency or default. This is materially distinct from, and additional to, the general bonding and net-worth obligations that apply to money transmitters generally. The initial research pass had concluded no such Connecticut-specific custody rule existed beyond the general MTL baseline; that negative finding is now confirmed incorrect and has been reversed on the strength of the primary legislative-summary source. The correction elevates Connecticut's consumer-protection posture for crypto custody above what a generic money-transmitter framework would imply, and it is the most consequential development in this cycle's record for the jurisdiction.

8 of 8 categories
Signal
Density

Selections OR within a group, AND across groups. Press / to search.

#

Connecticut has no bespoke crypto-asset licence; virtual-currency exchange, custody and kiosk businesses are regulated under the general Money Transmission Act (Conn. Gen. Stat. Sec. 36a-595 et seq.), administered by the CT Department of Banking via NMLS, with virtual-currency-specific provisions added by PA 23-82, PA 24-146 and PA 25-66, the latter restricting permissible custodians of customer virtual currency.

Standing sub-brief319 words · last cycle 2026-09-21

Crypto Licensing

Connecticut has no dedicated crypto-specific license. Crypto money-transmission activity is authorized and supervised through the state's general money-transmitter licensing law, which was materially amended in 2025 by Public Act 25-66 (H.B. 7082) to tighten disclosure and consumer-facing obligations for licensed crypto firms. This cycle's Challenger review corrected a source-attribution error on that tightening claim: the citation had pointed to an article discussing Connecticut's separate state-crypto-investment ban rather than the source actually describing the money-transmitter licensing amendments, and the correction restores proper evidentiary traceability for what is treated as a high-materiality claim.

Periodic update · new data 2026-09-22

Crypto Licensing

Connecticut requires virtual-currency kiosk owners and operators, along with virtual-currency transmitters generally, to hold a Connecticut money-transmission licence under Conn. Gen. Stat. Sec. 36a-595 to 36a-613, a requirement confirmed and in force since kiosks were explicitly brought within scope. Public Act 25-66, effective October 1, 2025, tightened this regime further by restricting who may lawfully custody a customer's virtual currency: only licensed money transmitters, FDIC- or NCUA-insured depository institutions, or third parties specifically approved by the Banking Commissioner may act as custodian. This is a probable-confidence finding drawing on a corroborating secondary law-firm summary rather than direct retrieval of the amended statute text this cycle, but it sits on top of a confirmed underlying licensing requirement.

The practical effect of these two enactments together -- kiosk licensure under the earlier statutory expansion and custody restriction under Public Act 25-66 -- is a narrowing compliance perimeter that leaves less room for unlicensed or loosely-custodied virtual-currency intermediation to operate within the state undetected. This tightening is not merely legislative text: it is being operationally applied, as the licensing module's linked enforcement action this cycle demonstrates.

Outlook

The key open question for this module is whether the Department of Banking will issue further interpretive guidance on what qualifies as a Commissioner-approved third-party custodian under Public Act 25-66, since the statute's practical scope for smaller or non-bank crypto intermediaries depends heavily on how that approval pathway is administered. Watch also for whether additional kiosk or transmitter licensees face compliance reviews tied to the same custody-restriction provisions.

1 earlier distinct update(s)
Periodic update · new data 2026-09-14

Crypto Licensing

Connecticut regulates virtual-currency activity entirely through its general Money Transmission Act (Conn. Gen. Stat. §36a-595 et seq.), as amended by Public Act 25-66, rather than through a bespoke crypto-licence class. The Connecticut Department of Banking has confirmed, in direct primary-source guidance, that an entity engaging in money transmission for Connecticut residents, including virtual-currency custody or exchange activity, requires MTA licensure regardless of whether that entity maintains a physical presence in the state. This extraterritorial reach is a confirmed finding of high materiality: any out-of-state platform serving Connecticut residents is captured by the licensure requirement purely on the basis of who its customers are, not where it operates.

PA 25-66 itself represents a substantial modernization of the MTA, extending its coverage to digital wallets and virtual currency explicitly and narrowing the field of permissible custodians for customer virtual currency to licensed money transmitters, FDIC-insured banks and credit unions, or parties the Banking Commissioner has expressly approved. This custody restriction, assessed as probable, is the central tightening mechanism introduced by the amendments and took effect October 1, 2025.

The overall trajectory this cycle is one of strengthening within the existing licensing architecture. Connecticut has not created a separate crypto-licence category; instead, it has broadened the definitional scope of activity already captured by the general money-transmission licence and tightened who may act as custodian within that regime. This is a materially different posture from states that have built dedicated virtual-currency licence classes, and it means compliance analysis for Connecticut should proceed through the MTA licensing lens rather than through a crypto-specific statute.

Outlook

The Department of Banking's confirmed, extraterritorial reading of MTA licensure obligations means any platform serving Connecticut residents should treat licensure as a threshold question regardless of physical presence in the state. Watch for further Banking Commissioner guidance on what constitutes an approved custodial party under the narrowed custodian provisions, as this determination will materially affect which third-party custody arrangements remain viable for licensees serving the Connecticut market.

Sources and findings (2)
  1. T4 · CoinDeskCoinDesk — Connecticut lawmakers tightened rules for crypto firms operating under the state's money-transmitter license as part of 2025 legislation.retrieved M5bindingin force
  2. T2 · Nationwide Multistate Licensing System (NMLS)Nationwide Multistate Licensing System (NMLS) — Connecticut has not been independently confirmed to operate a crypto-specific license distinct from its general money-transmitter regime; the precise statutory citation for virtual-currency treatment within the MTL statute requires primary-source verification.retrieved M3non-bindingour coverage gap, expected to resolve on a re-run

#

Connecticut does not operate its own token-taxonomy regime; per the jurisdiction disambiguation, characterisation of crypto assets as securities, commodities, or payment stablecoins is governed by federal SEC/CFTC frameworks, applicable uniformly to Connecticut market participants. The SEC's 2026 interpretive release on the application of federal securities laws to crypto assets distinguishes digital commodities, digital collectibles, digital tools, stablecoins and digital securities, while the GENIUS Act separately confirms that compliant payment stablecoins are not securities.

Standing sub-brief348 words · last cycle 2026-08-06

Token Classification

Connecticut has adopted no state-specific token-classification taxonomy and defaults entirely to the federal SEC/CFTC interpretive framework, principally SEC Release 33-11412, which applies the Howey investment-contract test to determine security status for crypto assets operating in or serving Connecticut absent any state carve-out. That same federal guidance treats non-fungible "digital collectibles" as generally falling outside the security definition unless fractionalized or structured to generate profit expectations for holders, again with no Connecticut-specific overlay.

no periodic updates on record for this sub-brief

Sources and findings (4)
  1. T1 · U.S. Securities and Exchange CommissionU.S. Securities and Exchange Commission — SEC interpretive guidance applies the Howey investment-contract test to determine whether a crypto asset transaction constitutes a security offering, a federal standard that governs token characterisation in Connecticut absent a state-specific carve-out.retrieved M4non-binding
  2. T1 · U.S. Securities and Exchange CommissionU.S. Securities and Exchange Commission — The GENIUS Act confirms that payment stablecoins are not securities under federal law, a classification applying uniformly across all U.S. states including Connecticut.retrieved M4bindingenacted not yet effective
  3. T1 · U.S. Securities and Exchange CommissionU.S. Securities and Exchange Commission — SEC interpretive guidance treats non-fungible 'digital collectibles' as generally outside the definition of a security unless fractionalized or structured to convey managerial-effort-based profit expectations.retrieved M3non-binding
  4. T2 · Nationwide Multistate Licensing System (NMLS)Nationwide Multistate Licensing System (NMLS) — Connecticut has not adopted its own token-classification taxonomy; classification defaults entirely to the federal SEC/CFTC framework with no state-level analog.retrieved M2non-bindinga fact about the regime

#

Connecticut has no state-specific regime governing on-chain activities such as staking, DeFi lending, mining, node operation, validation or tokenization. To the extent such activities involve money transmission, the general MTL law may apply; classification of protocol mining and protocol staking activities under federal securities/commodities law is addressed only at the federal level via SEC/CFTC interpretive guidance, not by any Connecticut-specific instrument.

Standing sub-brief183 words · last cycle 2026-08-06

On-Chain Activity Regime

Connecticut has not enacted any state-specific regulation of protocol staking, protocol mining, DeFi lending, decentralized-exchange operation, node or validator activity, or tokenization. Coverage of these activities is confined to federal interpretive guidance under SEC Release 33-11412, which addresses the federal securities-law status of staking and mining activities without any Connecticut-specific overlay, and to the general applicability of Connecticut's money-transmitter law only where such activity happens to intersect with money-transmission functions.

no periodic updates on record for this sub-brief

Sources and findings (3)
  1. T1 · U.S. Securities and Exchange CommissionU.S. Securities and Exchange Commission — Federal interpretive guidance separately addresses the federal securities-law status of 'Protocol Staking' activities, without any Connecticut-specific overlay.retrieved M3non-binding
  2. T1 · U.S. Securities and Exchange CommissionU.S. Securities and Exchange Commission — Federal interpretive guidance separately addresses the federal securities-law status of 'Protocol Mining' activities, without any Connecticut-specific overlay.retrieved M3non-binding
  3. T2 · Nationwide Multistate Licensing System (NMLS)Nationwide Multistate Licensing System (NMLS) — Connecticut has not enacted state-specific regulation of DeFi lending, DEX operation, node operation, validator activity, or tokenization; these activities are governed, if at all, only by generally applicable federal frameworks or the state's MTL law to the extent money transmission occurs.retrieved M2non-bindinga fact about the regime

#

Connecticut has no independent stablecoin statute. The federal GENIUS Act (signed July 18, 2025) establishes the first comprehensive U.S. stablecoin framework, covering issuer permitting, 1:1 reserve backing, redemption rights, and disclosure, with implementing rules from the OCC, FDIC, NCUA, Federal Reserve and Treasury still at proposal stage as of mid-2026 and full operative effect no later than January 18, 2027. Treasury's proposed criteria for certifying a state regime as 'substantially similar' to the federal framework (relevant to any future Connecticut state-qualified issuer route) also remain unfinished.

Standing sub-brief315 words · last cycle 2026-09-14

Stablecoin Regime

The GENIUS Act establishes the controlling federal framework for payment stablecoins applicable to Connecticut, permitting only federally chartered banks, OCC-supervised nonbank issuers, and certified state-qualified issuers to issue payment stablecoins to U.S. customers. The Act requires permitted issuers to back every stablecoin one-to-one with high-quality liquid reserves, to support redemption at par on demand, and to provide monthly reserve disclosures alongside maintained redemption policies.

Periodic update · new data 2026-09-14

Stablecoin Regime

Connecticut does not maintain a dedicated stablecoin issuance, reserve, or redemption regime. Instead, Public Act 25-66 updated the Money Transmission Act's definition of stored value to encompass electronic or digital records representing a claim against an issuer, a generic extension that happens to align with stablecoin-like instruments without creating bespoke stablecoin law. This finding is assessed as probable, sourced from tier-three legal commentary describing the amendment's scope.

The practical effect is that an issuer or transmitter of a stablecoin-like instrument serving Connecticut residents would likely be captured under the updated stored-value definition and, by extension, under the general Money Transmission Act licensing perimeter discussed in the Crypto Licensing module, rather than under any stablecoin-specific issuance, reserve-attestation, or redemption-right framework. Connecticut's approach here mirrors its overall pattern this cycle: extend existing generic categories to capture new instrument types, rather than legislate a bespoke regime for them.

This is a genuine but modest tightening. It brings a class of instruments into scope that may previously have sat in an ambiguous position relative to the MTA's stored-value provisions, but it does not impose reserve-backing requirements, redemption-rights mandates, or issuer-disclosure obligations specific to stablecoins, of the kind seen in dedicated stablecoin statutes elsewhere.

Outlook

Watch for whether Connecticut's legislature or Department of Banking moves beyond this generic stored-value extension toward a dedicated stablecoin framework, particularly if federal stablecoin legislation creates pressure for state-level harmonization. In the interim, any stablecoin-like instrument serving Connecticut residents should be assessed against the updated stored-value definition and the general MTA licensing and custody requirements described above.

Sources and findings (5)
  1. T4 · The BlockThe Block — The GENIUS Act permits only federally chartered banks, OCC-supervised nonbank issuers, and state-qualified issuers under a certified state regime to issue payment stablecoins to U.S. customers, including in Connecticut.retrieved M5bindingenacted not yet effective
  2. T4 · The BlockThe Block — Permitted stablecoin issuers under the GENIUS Act must back every stablecoin one-to-one with high-quality liquid reserves.retrieved M5bindingenacted not yet effective
  3. T4 · The BlockThe Block — GENIUS Act permitted issuers must support redemption of payment stablecoins at par on demand.retrieved M5bindingenacted not yet effective
  4. T4 · The BlockThe Block — GENIUS Act issuers must publish monthly reserve disclosures and maintain redemption policies as part of federal stablecoin supervision.retrieved M4bindingenacted not yet effective
  5. T4 · The BlockThe Block — As of the GENIUS Act's one-year rulemaking deadline, the OCC, FDIC, NCUA and Treasury had not finalized implementing regulations, leaving prudential/systemic aspects of stablecoin supervision unresolved.retrieved M3non-binding

#

Sec. 36a-613 imposes mandatory pre-account/pre-transaction disclosure duties on virtual-currency kiosk operators, including a bolded irreversibility/fraud warning and no-FDIC/NCUA/SIPC-coverage disclosure; enforcement occurred in March 2026 against a kiosk operator for alleged non-compliance, resulting in a summary licence suspension.

Standing sub-brief340 words · last cycle 2026-09-21

Consumer Protection

Public Act 25-66 (H.B. 7082) is Connecticut's principal consumer-protection instrument for crypto and imposes several distinct obligations on crypto money-transmission businesses. It requires disclosure of all material crypto risks in clear, conspicuous, legible English-language writing, and it requires legal-guardian verification for users under 18 engaging with crypto money-transmission services.

The most significant development in this module this cycle is a Challenger-fold correction to the custody-obligation record. The initial research pass had concluded that no Connecticut-specific custody-segregation requirement existed for crypto-asset custodians beyond the general money-transmitter law's permissible-investment and net-worth obligations. Direct review of the official Connecticut General Assembly legislative summary of PA 25-66 shows this to have been incorrect: the Act requires crypto money-transmission licensees to use only approved custodians for held virtual currency, and it deems such virtual currency to constitute a property interest of claimants against the licensee — a distinct and additional protection layered on top of, not subsumed by, the general bonding and net-worth framework. The negative finding has been reversed and a corresponding claim has been added, both anchored to the primary legislative-summary source with corroborating secondary sourcing.

Periodic update · new data 2026-09-22

Consumer Protection

Connecticut's virtual-currency consumer-protection regime centers on Conn. Gen. Stat. Sec. 36a-613, which requires kiosk operators to disclose -- in bolded English-language text that the customer must affirmatively acknowledge -- that losses from fraud or accident involving virtual currency may be unrecoverable and that virtual-currency transactions are irreversible. This disclosure obligation is confirmed and in force, and it functions as the primary consumer-facing safeguard against the irreversibility risk inherent to virtual-currency kiosk transactions.

That disclosure regime is not merely aspirational: in March 2026 the Connecticut Department of Banking summarily suspended a virtual-currency kiosk operator's money-transmission licence, alleging violations of the consumer-disclosure, fee-cap and refund provisions embedded in Sec. 36a-613. This is a probable-confidence finding, since the underlying reporting comes from a single secondary source rather than a directly retrieved primary enforcement order, but it demonstrates that the state's consumer-protection statute is being actively policed rather than left dormant. The suspension action is the clearest evidence available this cycle that Connecticut's kiosk-specific consumer protections carry operational teeth.

Outlook

The unresolved question is the final disposition of the March 2026 suspension matter -- revocation, reinstatement, or a negotiated resolution -- which was not confirmed this cycle. That outcome will materially inform how consistently Connecticut enforces its disclosure, fee-cap and refund requirements against other kiosk operators going forward, and is the single most consequential open item for this module.

1 earlier distinct update(s)
Periodic update · new data 2026-09-14

Consumer Protection

Connecticut's consumer-protection regime for virtual-currency activity has been materially strengthened this cycle. The Digital Currency Kiosk Consumer Protection Regime, codified at Conn. Gen. Stat. §36a-613, became fully operative on June 9, 2026, and Public Act 25-66 extends its disclosure and receipt requirements beyond kiosk operators to all virtual-currency transmitters operating in the state. This finding is assessed as probable, drawn from tier-three legal and industry commentary describing the amendment's scope.

Under the extended regime, Connecticut virtual-currency transmitters must provide clear disclosure of fees, unauthorized-transfer liability, and irreversibility warnings, both at customer onboarding and before each individual transaction. This is a new statewide disclosure duty that goes beyond the kiosk-only scope that previously applied, and it represents a genuine strengthening of the consumer-facing conduct regime rather than a reorganization of existing requirements.

The combination of the custody restrictions described in the Crypto Licensing module and these disclosure extensions gives Connecticut consumers materially more protection this cycle than the prior baseline, even though the state has not created a dedicated crypto-consumer-protection statute distinct from its money-transmission framework.

Outlook

Virtual-currency transmitters serving Connecticut residents should review onboarding and per-transaction disclosure workflows against the fee-transparency, unauthorized-transfer-liability, and irreversibility-warning requirements that now apply statewide rather than only to kiosk operators. Watch for Department of Banking enforcement activity testing compliance with the newly extended disclosure regime now that it is fully operative.

Sources and findings (4)
  1. T4 · The BlockThe Block — Connecticut's Public Act 25-66 requires crypto businesses engaged in money transmission to disclose all material risks associated with crypto in clear, conspicuous and legible English-language writing.retrieved M4bindingin force
  2. T4 · The BlockThe Block — Public Act 25-66 imposes protections for minors, requiring legal-guardian verification for users under the age of 18 engaging with crypto money-transmission services in Connecticut.retrieved M4bindingin force
  3. T2 · Nationwide Multistate Licensing System (NMLS)Nationwide Multistate Licensing System (NMLS) — No Connecticut-specific custody-segregation requirement for crypto-asset custodians beyond general MTL permissible-investment and net-worth obligations has been identified.retrieved M3non-bindingour coverage gap, expected to resolve on a re-run
  4. T2 · Nationwide Multistate Licensing System (NMLS)Nationwide Multistate Licensing System (NMLS) — No Connecticut-specific crypto complaint-handling rule distinct from general MTL consumer-complaint procedures has been identified.retrieved M2non-bindingour coverage gap, expected to resolve on a re-run

#

Connecticut applies no crypto-specific state tax statute; federal tax treatment (IRS: crypto as property) sets the baseline that flows through to Connecticut's federally conformed income tax base. Capital gains arise on disposals; ordinary income arises on receipt via mining, staking, forks or compensation. A pending federal bill (PARITY Act) would create a de minimis exemption for small stablecoin payment transactions, but it is not yet enacted.

Standing sub-brief254 words · last cycle 2026-08-06

Tax Treatment

Connecticut has no crypto-specific tax statute. Federal Internal Revenue Service treatment governs by default: the IRS treats bitcoin and other cryptocurrencies as property, qualifying dispositions for capital-gains treatment, and treats crypto received through staking or forking as ordinary income at receipt. Both positions apply to Connecticut filers through the state's federally conformed income tax base rather than through any independent state ruling.

no periodic updates on record for this sub-brief

Sources and findings (4)
  1. T4 · CoinDeskCoinDesk — The IRS treats bitcoin and other cryptocurrencies as property, qualifying dispositions for capital-gains treatment similar to stocks and bonds, a federal baseline that applies to Connecticut taxpayers absent contrary state law.retrieved M4bindingin force
  2. T4 · CoinDeskCoinDesk — Crypto received through staking or forking is treated as ordinary income at the time of receipt under IRS guidance, applicable to Connecticut filers via the state's federally conformed tax base.retrieved M4bindingin force
  3. T4 · CoinDeskCoinDesk — A pending federal bill (the PARITY Act) would introduce a de minimis exemption from gain/loss recognition for small payment-stablecoin transactions, but it has not been enacted as of April 2026.retrieved M2non-binding
  4. T4 · CoinDeskCoinDesk — No VAT/GST applies to crypto transactions in the United States, including Connecticut, as the U.S. federal and state tax systems do not employ a value-added tax.retrieved M1non-bindinga fact about the regime

#

Connecticut has no independent cross-border crypto-transfer regime. Federal sanctions/OFAC screening and FinCEN Travel Rule-style analysis of virtual-currency transmittals apply uniformly nationwide, and the GENIUS Act layers Bank Secrecy Act and U.S. sanctions compliance obligations onto permitted stablecoin issuers, including a FinCEN/OFAC joint proposed rule implementing those requirements.

Standing sub-brief181 words · last cycle 2026-08-06

Cross-Border Transfer

Connecticut has not identified any state-specific outbound restriction on crypto-asset transfers beyond the generally applicable federal sanctions and money-transmitter frameworks. Federal FinCEN guidance treats convertible-virtual-currency transmittals as transmittals of funds for Travel-Rule-style funds-transfer analysis, applying uniformly regardless of the transferor's state of residence; this surface is routed to the financial-integrity monitor for detailed analysis rather than independently developed here.

no periodic updates on record for this sub-brief

Sources and findings (3)
  1. T1 · FinCEN / Office of Foreign Assets ControlFinCEN / Office of Foreign Assets Control — FinCEN and OFAC issued a joint proposed rule to implement the GENIUS Act's anti-money-laundering and sanctions-compliance requirements for permitted payment stablecoin issuers.retrieved M4non-binding
  2. T1 · Financial Crimes Enforcement Network (FinCEN)Financial Crimes Enforcement Network (FinCEN) — FinCEN guidance treats convertible-virtual-currency transmittals as transmittals of funds for purposes of Travel Rule-style funds-transfer analysis, applicable federally regardless of the transacting party's state of residence.retrieved M3bindingin force
  3. T2 · Nationwide Multistate Licensing System (NMLS)Nationwide Multistate Licensing System (NMLS) — No Connecticut-specific outbound restriction on crypto-asset transfers beyond the generally applicable federal sanctions and MTL frameworks has been identified.retrieved M2non-bindinga fact about the regime

#

Per the crypto consumer's module-subscription model, AML/CFT obligations are sourced from the shared FIM aml_ctf module rather than produced natively in this crypto baseline. No aml_cft_regime claims are emitted here; disambiguation context only: Connecticut crypto money-transmission licensees remain subject to federal Bank Secrecy Act obligations administered by FinCEN regardless of state licensing status.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

no periodic updates on record for this sub-brief

No categories match.

Filters combine as OR inside a group and AND across groups.

Publication gate

Blocking. 1 failing check(s).

schema_validFAIL
min_quoted_text_presentwaived — floor 0%
egress_verifiedpass
every_practical_object_has_source_idn/a — no subject in this jurisdiction
source_tier_integrity_okpass
jurisdiction_source_floor_metpass
tier_a_b_national_primary_pct40.0
aggregator_only_jurisdiction_count0
manual_override

Editorial metadata

Provenance only. Nothing below gates publication or affects the render.

Editorial metadata for Connecticut, USA
FieldValue
trust.lawyer_review.statusnever_reviewed
trust.lawyer_review.reviewerno reviewer on record
trust.content_sourceai_generated

Provenance and declared absence

Disclosure model: module cards load OPEN; standing positions render in full; sub-briefs and jurisdiction briefs load as a clamped teaser with an explicit “read full” control carrying the true word count; earlier updates stay collapsed behind a counted summary. No text is hidden without disclosing how much of it there is.

Sentinel-fed modules receive no special rendering treatment. sentinel_feed is an attribution chip only: it does not suppress content, does not generate an absence reason code, and does not exclude the module from any count, filter, search index or export on this page.

Family taxonomy is renderer-level presentation config, not a JID field. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score; per-module RAG traffic light; derived_scores = {}.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-09-27. A year-precision row is never promoted into a tighter band.

Orphan deltas: 0 cycle_delta row(s) target non-module objects and are listed in the rail rather than attached to a card.

Envelope: baseline resolved at jurisdiction_json.baseline; 8 module(s), 25 finding(s), 21 source(s) in the cumulative register.

Think something on this page is wrong? Report an error.