Whether a jurisdiction is served, and its notice rules

Served status, handling, jurisdiction ids and the grounds. With a live key every US state and DC is served with handling: "attorney_direct", action: null and, for each ground, notice: null and the facts intake requires (requiredFacts) and, where fullService is true, the facts that place's documents ask for beyond them (documentFacts: notice and filing, by where the case starts, and conditional, facts asked for only when another holds (with past: true, when that fact is a date before today, such as a lease end date that has passed), ledgerItemised, where the place's documents itemise the ledger by kind of charge (notice: the notice demands only what is past due on its date; filing: the filing states the amounts by kind), and defaults, the pack's own default where a fact has one). They apply only to a case created with service: "full": ask an attorney-path case for the intake facts alone; anything else is served: false. With a test key (handling: "automated") the fictional test state answers with its notice rules for each ground. fullService says whether a case created here with service: "full" is handled by us as your agent (no attorney reviews it); where it is false, a managed-service request answers 409 service_unavailable with its operational reason. This does not establish a legal requirement for counsel. county may be written as the US Census Bureau lists it or by its short name, in any case ("Henry County", "henry"); a county the state does not have answers 400 invalid_request. court is the court the place's rules say a case goes to, with the county ("Magistrate court of Henry County"), or null where no rule pack covers the place. courts lists, where fullService is true, the courts a full-service case's managedContext.courtId may name, each with the forums its managedContext.forum may name; it is empty otherwise.