Sourcing · claim classification · dates · architecture · revised
Methodology
This page exists so a reader can check the machinery rather than trust it. Everything here is enforced by build gates, not by intention — and where a rule was added because something went wrong, this page says so.
Source hierarchy
Journalism is used to find documents, never to substitute for them. If a government source is reachable, the government source is what gets cited — citing an article that cites a rule is source laundering, and it hides whether anyone read the rule.
Tier 1 · Primary / authoritative
statute · regulation · rulemaking docket · court opinion · docket document · agency enforcement release · official guidance · government report · official dataset · regulator decision · SEC filing · legislative text · chamber action history · FDA record · CMS record · ClinicalTrials.gov · WHO/EMA/MHRA/TGA/Health Canada publication · peer-reviewed original research
Tier 2 · High-quality secondary
systematic reviews · respected academic analysis · official professional guidelines
Tier 3 · Journalism
Discovery of primary documents only. Never a substitute where the primary document is reasonably available.
Tier 4 · Trade and secondary commentary
Lead generation only.
Tier D · Community reports
For the IMG vertical: applicant forums identify questions. They never establish a programme requirement or a visa rule. Rendered only under an explicit UNVERIFIED APPLICANT REPORT label.
Claim classification — and the conversions that are forbidden
Every material statement fits one of ten classes, and the classes are not interchangeable. The list below is not abstract: each prohibited conversion is a specific error this site either made and corrected, or came close to making.
- DOCUMENTED_FACT — A primary source states it.
- REPORTED_ALLEGATION — A complaint, charge or report asserts it. Never rendered as occurrence.
- LEGAL_CLAIM — A party asserts it as a legal position.
- AGENCY_POSITION — An agency states it. Distinct from law.
- COURT_FINDING — A court found it. Level and finality must be stated.
- RESEARCH_FINDING — A study reports it. Design and effect size must be stated.
- INTERPRETATION — KPSGILL reads the source this way. Labelled.
- INFERENCE — KPSGILL infers it. Labelled, with the inference shown.
- FORECAST — KPSGILL predicts it. Requires confidence, assumptions, competing scenario and falsification condition.
- POLICY_PROPOSAL — KPSGILL recommends it. Never rendered as law.
- "Complaint alleges X" → "X occurred"
- "Settled without admission" → "Defendant did X"
- "Agency proposes" → "Law requires"
- "Passed one house" → "Passed the Legislature"
- "Passed the Legislature" → "Enacted"
- "Signed" → "In effect"
- "In trials" → "Approved" or "Available"
- "Licensed for pathogen A" → "Effective against pathogen B"
- "Convened expert report" → "Formal WHO position"
- "Grant announced" → "Funds obligated"
- "Prioritised for review" → "Approved" or "Standard lowered"
- "Organisational enforcement priority" → "Wrongdoing by a named party"
- "Cap-exempt employer" → "Fee-exempt petition"
- "Not publicly stated" → "No"
Two are worth spelling out because they cost real accuracy in the last week. Passed one house is not passed the Legislature when a bill was amended after the first house acted — AB 2575 passed the Senate 21–10 and still required Assembly concurrence, which it got, 43–12, and the distinction was live for a full day. And licensed for one pathogen is not effective against another: Ervebo is a licensed Ebola vaccine whose protection against Bundibugyo virus WHO says is unestablished, so both “there is no vaccine” and “the vaccine protects” are wrong.
Dates, snapshots and what a redesign does not mean
Five date fields, never used as synonyms: contentModifiedAt (the page changed), sourcesCheckedAt (a human re-read the sources), recordThrough (the record is complete to this date), effectiveDate (an instrument takes effect) and lastSubstantiveUpdate. A template or navigation change advances the first only. This is the rule that stops a redesign from silently claiming re-verification — and it is why pages that received only a navigation change this week still carry their existing approval and their original source-check date.
Snapshots accumulate rather than overwrite. Publication state is fixed at an instant and recorded in data/snapshots.json. Three snapshots exist for 31 August and 1 September alone, because the California legislature moved three times in that window. An earlier snapshot is never rewritten because a later action became known — it was correct for its instant, and rewriting it would destroy the only evidence of what was knowable when.
Deadlines are computed, not typed. Where an authority states a closing instant, the registry stores the instant — the CY 2027 Home Health comment window closed at 5:00 PM EDT on 31 August, not at the end of that calendar day. Where no time is stated, the row is marked date-only and midnight is never invented.
Object taxonomy — including what is not built
The article is no longer the only first-class object. 23 types are defined; the status column is honest, and a planned type counts as zero everywhere on the site.
| Object type | Status | Live | Note |
|---|---|---|---|
| Analysis /policy/<slug>/ | PUBLISHED | 470 | Long-form documentary examination. The existing policy corpus. |
| Explainer /how-medicine-works/<slug>/ | PLANNED | 0 | Institutional mechanics for non-specialists. Template designed; not populated. |
| Intelligence record /records/<id>/ | PUBLISHED | 24 | Structured event record with establishes / does-not-establish. Built 1 September. |
| Case record /litigation/<case-slug>/ | PLANNED | 0 | Schema designed in data/schemas.json; no case records published. |
| Enforcement record /enforcement/ | PARTIAL | 0 | Enforcement ledger exists as a tracker; per-action records not yet split out. |
| Legislation record /bills/<bill>/ | PUBLISHED | 14 | Bill dossiers, session-scoped identity. |
| Regulation record /regulations/<slug>/ | PARTIAL | 0 | Regulations currently appear inside analyses and date rows; no standalone record type yet. |
| Agency record /agencies/<id>/ | PLANNED | 0 | Entity IDs assigned in data/entities-registry.json. |
| Organization record /entities/<id>/ | PLANNED | 0 | Requires ownership sourcing before publication. |
| Jurisdiction record /jurisdictions/<id>/ | PARTIAL | 1 | /california/ functions as a jurisdiction hub; formal jurisdiction records not yet built. |
| Topic dossier /dossiers/<topic>/ | PLANNED | 0 | Living synthesis. Template designed. |
| Tracker /intelligence/<slug>/ | PUBLISHED | 11 | Continuously updated status or chronological data. |
| Dataset /data/<file>.json | PUBLISHED | 12 | The registries. Publicly fetchable JSON; no download page yet. |
| Index /research/indexes/<id>/ | PLANNED | 0 | Methodology frameworks written; NO SCORES PUBLISHED — see the deliberate hold below. |
| Map /research/maps/<id>/ | PLANNED | 0 | Corporate Medicine Map. Requires the ownership database first. |
| Timeline /timeline/ | PARTIAL | 1 | data/chronology-2026.json holds 155 dated records; the public /timeline/ route is built this batch. |
| Policy proposal /reform/proposals/<slug>/ | PUBLISHED | 18 | Never typed as Legislation in JSON-LD. |
| Evidence review /evidence/<slug>/ | PLANNED | 0 | |
| Patient guide /patient-education/<slug>/ | PUBLISHED | 128 | Plus 60 translation routes. |
| Physician guide /physicians/<slug>/ | PARTIAL | 0 | Physician-facing material currently sits inside the policy corpus. |
| Student / IMG guide /img/<slug>/ | PUBLISHED | 8 | Built 1 September. Every page carries a Match-year label. |
| Institutional profile /entities/<id>/ | PLANNED | 0 | The synthesised dossier. Depends on ownership, enforcement and litigation records existing first. |
| Legislator brief /reform/briefs/<slug>/ | PUBLISHED | 9 | Compression of a published proposal; not a separate normative object. |
The relationship graph, and its empty predicates
Relationships live in data/graph.json as 286 edges, each carrying the registry that asserts it. Entity IDs in the entity registry are stable, so renaming a page cannot break a relationship.
Some predicates are defined and carry zero edges: owns, subsidiary_of, controlled_by, acquired, sued_by, sued, sanctioned_by, contracts_with and others. That is deliberate. Ownership, litigation and enforcement relationships require corporate, docket and agency sourcing per entity, and none of that research is done. An empty predicate is honest; a speculative edge would be the single most damaging thing this architecture could contain, because a graph makes assertions look derived.
Original analysis, and how it is labelled
Where KPSGILL computes or synthesises something, it is labelled KPSGILL analysis or KPSGILL original dataset, with methodology, source data, assumptions, limitations and an update date. Nothing on this site is presented as official-government data.
Trade-off directions and stakeholder tables in the reform layer are impact analysis — explicitly not projections, and not the stated positions of the groups named. Forecasts carry confidence, assumptions, a competing scenario and a falsification condition, and a resolved forecast is scored on the ledger whether it was right or wrong. Four index products are designed and deliberately unpublished, and that page says why.
Research status, and why breadth does not imply completeness
A node moves through 9 internal states — proposed, collecting, primary-sources-located, drafted, verification-pending, ready, published, update-required, archived. Only published appears publicly. This is what allows the architecture to be broad without implying that every branch is populated.
Freshness is tiered. Legislation, litigation, regulation, enforcement, healthcare AI and physician immigration are Tier A and go stale in thirty days. Scope of practice, corporate-practice doctrine and certification are Tier B at six months. Institutional mechanics and historical law are Tier C. An IMG immigration page older than ninety days during Match season enters update-required automatically, because a court order can invalidate a correct statement overnight — as one did to the $100,000 H-1B proclamation fee.
Editorial standards and the review model · Research products · Event timeline · The schema file itself