JurisdictionResolverGKR

What it is

JurisdictionResolverGKR resolves the state law a claim runs under and serves the sections a downstream tool reads: limitation periods, subrogation gates, defeat conditions and the fault system. It reads jurisdiction records and anchor records only. It computes nothing from the wall clock, defaults nothing, and stops the run when a section it needs is missing .

Sections it resolves

Section	Content	State of the registry
statute_of_limitations	Limitation periods per cause; feeds resolver deadlines	Team-curated (PL-F-2), 204 rows, all 51 states; 30 rows verified against two sources, 174 single-source
anti_subrogation	General P&C Sutton and own-insured rules; WC lien rules	96 records in reference_data; WC complete, 6 states outstanding on general P&C
AUTO subrogation (JUR-AUTO-{ST}-subrogation-v1)	no_fault_state, threshold_type, pd_subrogation_permitted, bi_subrogation_regime, pd_recovery_regime, loss_transfer_rule	Drafted by Claude Code, not the team; 5 promoted (TX, CA, NY, VA, FL), 46 draft; 12 no-fault states expert-verified Tier A, 39 Tier B
statute_of_repose	Construction and product, bar_type absolute or rebuttable presumption	Drafted and reviewed; absent from the team catalog
governmental_notice	Deadline type, entity class, claim class	Withdrawn pending re-draft from statute text; blocks AUTO-005 and the municipal theories
fault_system	State tort law: comparative and contributory rules	Shared by AUTO and PROPERTY; the Property comparative gate routes to the AUTO records

Drafts stay out of bundles until curated in the same discipline as the team's own sections. Tier A and Tier B records load as draft through the recorded path and move to approved, never active, until tester verification . Mandatory loss-transfer arbitration is modelled in the state section; carrier arbitration membership is a tenant fact, seeded at install, and never a state fact. The jurisdiction key convention is plain state codes.

How the harness reaches the resolver

The harness derives jurisdiction_context through a jurisdiction_role_map record (JURIS-ROLE-MAP-v1) rather than from a code path, and the resolver reads its facts through its own input map record (JURIS-RESOLVER-INPUT-MAP-v1); both are seeded and approved . What the role map encodes beyond that is not yet documented. A caller-supplied state that contradicts the document fails the run with both values named; one early run applied California law to a Texas document because a --state flag routed straight to the resolver with no cross-check.

Anchors

The anchor for a deadline is a record, not a code path. date_of_loss is the only core anchor; WC's date_of_injury lives in the WC extension. The seeded anchor record (RESOLVER-ANCHOR-FIELD-v1) carries no fallback: a fallback was removed by ruling, and header.stage is required with no default . A deadline with no anchored date is never computed; the brief says deadlines will compute once the anchor is available and that this is not to be read as no deadline.

The resolver derives notice_of_claim_days itself. Deadlines on a thesis are limited to causes actually on the thesis, each with its anchor shown.

Rules do not always resolve as of the loss date. The New York amendment described below applies to actions commenced on or after enactment, so a 2025 loss litigated later falls under the new bar while a 2026 loss already in suit does not. Records need an explicit as_of_basis rather than an assumed loss date; whether the whole jurisdiction set has been checked for this property is not yet documented.

A missing section stops the run

An error is never a decision. If the resolver, a section or an upstream output is missing, the run stops with a named error . The rule was earned: a no-fault section once missing for a state fell back to the fault_system record, and the fallback was reverted by ruling. Earlier, all 66 jurisdiction rules had null obligation records, so no claim in any state could compute a deadline, and every review had passed because every review was of code.

An indeterminate output looks the same whether a parameter is missing or the lookup is broken. The standing practice is to seed one jurisdiction properly and exercise both branches: one state resolving and another naming the missing parameter is the multi-state path proven, and worth more than a second seeded state.

The team's curation discipline

The testing team hand-curates jurisdiction data from authorised state websites in a 13-field YAML discipline: the cite, the source URL, a verbatim snippet, verification status, effective date and caveats among them. Testers return YAML in the database record shape with curation_status left at draft; promotion happens through the recorded path. Two tickets extend the discipline to the sections Claude Code drafted: the AUTO subrogation section (51 states, six fields; the twelve no-fault states FL, HI, KS, KY, MA, MI, MN, ND, NJ, NY, PA and UT are the work) and governmental notice. A statute of repose pass follows.

The verification pass over Tier B already shows its value. North Dakota's loss-transfer rule was repealed in 2005; Michigan's mini-tort belongs to the owner, so pd_subrogation_permitted is false; Minnesota's indemnity trigger is 5,500 lb curb weight; Hawaii reimburses only 50 percent from the insured's recovery; South Dakota is a plain tort state.

The public-data catalog

The team catalog (dated 2026-09-17, 16 sections) holds AUTO fault_system (evidence for 51 of 51, four case-law holdings missing for AL, KY, MO and NM), um_uim, total_loss and negligence_standard; sol with 153 rows; GL litigation_procedure, punitive_damages, anti_subrogation, made_whole, governmental_immunity and anti_indemnity; and PROPERTY anti_concurrent_causation. WC sections are not loaded. The AUTO subrogation section, governmental notice and statute of repose are absent from it, and none was ever a team ticket .

Housekeeping identified from the pinpoint: record the SOL snippets as source evidence, since the YAML carries cites and snippets but no evidence is recorded; check whether governmental_immunity can be keyed to AUTO and PROPERTY for the sovereign immunity defense; and let the general P&C anti-subrogation rows serve the tenant negligence theory once a structured tenant_co_insured_rule enum exists.

Verification beats recall: the New York correction

Domain review was wrong and the curated record was right. CPLR § 1411 gained a subsection (b) on 27 May 2026, moving New York from pure to modified comparative negligence for motor vehicle cases with a 51 percent bar. The curator had verified it against the primary source on 6 September; expert review asserted twice, in writing, that no such subsection existed, reasoning from a rule settled for decades and superseded days before the reviewer's information ended.

Three standing rules follow. A domain ruling never supersedes a primary-source verification; it triggers re-verification, and the source decides the direction. Domain review and verification are separate fields on a record, and the reviewer's name never goes in the verifier field. Every record carries its own verification date, because what read as a conflict between two curations was a temporal difference nobody could see.

Being right about a provision is not being right about its scope. The same amendment excludes actions for death or property damage, so on a property-damage-only recovery the bar does not apply, and the record needs a damage-type scope condition rather than a state and a percentage. A correction is incomplete if it misses its companions: the same package eliminated the 90/180-day serious injury category, added a fault-before-damages sequencing rule and capped non-economic damages in defined circumstances, all of which belong in the same state's records.

What Property reads

A Property claim reads fewer sections than an Auto claim, and the ones it needs most are the least curated.

Section	Use on Property	State
statute_of_limitations	Property-damage period from the date of loss; feeds PROP-SUBRO-DEF-002	Served; the Florida row carries four years where the 2023 amendment gives two for negligence accruing after 2023-03-24
fault_system	Comparative gate, shared with Auto	Served; the gate is not_applicable without stated fault facts; the brief must print the record's own label (pure, modified 50 or 51 percent, contributory)
statute_of_repose	Construction (from completion) and product (from sale or delivery); bar_type absolute or rebuttable presumption	Drafted and reviewed; not wired to the Property path
governmental_notice	Notice-of-claim deadline on a municipal target; feeds notice_of_claim_days and PROP-SUBRO-DEF-003	Withdrawn pending re-draft; municipal referrals carry a material condition instead
anti_subrogation	General P&C own-insured and implied co-insured tenant rules	Rows exist; the tenant theory cannot read them until a structured tenant_co_insured_rule exists
anti_concurrent_causation (PROPERTY)	A coverage concept, not a subrogation input	Catalogued; not read by the screener

The government notice re-draft has to carry claim class as well as entity class: California's Gov. Code § 911.2 gives six months for injury to personal property and one year for other causes, so a building head and a business personal property head on the same loss can carry different deadlines.

Open items

• The resolver returns product-liability and contract SOL rows for a claim with no such theory.
• Governmental notice re-draft; HI, MA and UT AUTO records held pending sourcing; effective_from for remaining states.
• Two provenance questions on the SOL section: 174 of 204 rows are single-source, and no source evidence is recorded against them in the catalog.
• The UM/UIM preservation section (PD-1 Tier 1) is not yet built.
• The whole registry has not yet been checked for the as_of_basis property.
• Property: wire statute_of_repose; re-draft governmental_notice by deadline type, entity class and claim class; add tenant_co_insured_rule; approve the Florida limitation change.