GovKM
GOVKM KNOWLEDGE

Articles and Research on Organizational Continuity

Explore GovKM analysis, research, and practical guidance on Organizational Continuity, information governance, AI readiness, institutional knowledge, and continuity architecture.
GovKM knowledge ecosystem connecting research, policies, procedures, datasets, reports, laws, circulars, and guidelines.
ARTICLES

Latest Research and Articles

Browse GovKM research, implementation guidance, continuity science, governance architecture, AI readiness, and organizational continuity.
Governance Architecture connecting internal risk evidence, authority, disclosure decisions, and the public record relied upon by investors.
Risk Disclosure Continuity

The Institution Knew the Threshold Was Breached. The Investor Record Didn’t Say So.

GAO found that banks could disclose internal risk thresholds without disclosing that those thresholds had been breached or how management responded. The case shows how authoritative internal evidence can fail to propagate into the downstream record used by investors and other external decision-makers.
Read the Article →
Records Governance framework illustrating how completed transactions must propagate into complete and accurate institutional records.
Record Propagation

The Transaction Happened. The Public Record Didn’t Fully Inherit It.

PBGC OIG found completeness and accuracy problems in obligation and outlay information reported to USAspending.gov, including contract actions not properly reflected. The case shows how a completed institutional transaction can fail to propagate into the downstream record later used for oversight, transparency, retrieval, and reuse.
Read the Article →
Organizational continuity framework showing a finalized fraud finding crossing an organizational boundary into reporting, financial action, records, and downstream institutional state.
Consequence Continuity

A Finding Is Not Complete Until Its Consequences Propagate

HHS OIG found cases where California Medicaid fraud determinations did not reliably become the required downstream reporting and financial actions. The case establishes consequence continuity: a finding is not institutionally complete until its required effects propagate across organizational boundaries into dependent decisions, actions, and records.
Read the Article →
Information continuity framework showing a regulatory drug-status change propagating through labeling, FDA data, CMS formulary records, coverage decisions, payments, and future reuse.
Lifecycle Continuity

The Drug Changed Status. The Government’s Information Did Not.

HHS OIG found $587.7 million in ineligible Medicare Part D payments after drug status changes failed to propagate consistently through FDA data, labeling, CMS formulary records, and downstream payment logic. The case demonstrates that authoritative state changes are dependency events, not local database updates.
Read the Article →
Governance architecture showing identical evaluation inputs sent to an AI judge with the same model name but different operational serving states, producing unstable measurements that require instrument provenance.
AI Instrument Provenance

The Model Name Was the Same. The Judge Wasn’t.

A preregistered study found substantial instability when identical inputs were replayed against black-box LLM judges, even under the same model name. When AI is used as an institutional measuring instrument, governance needs operational instrument provenance and reliability evidence—not merely the model identifier.
Read the Article →
Metadata and structure framework showing the same identity evidence entering multiple verification systems and producing conflicting match decisions because their matching rules differ.
Identity Continuity

The Person Was the Same. The Matching Rules Weren’t.

SSA OIG found that independently developed identity-verification systems could apply different matching criteria to the same evidence and produce different outcomes. Entity resolution is therefore a governed continuity relationship, not merely a lookup: matching rules, thresholds, exceptions, and conflicting identity states require provenance and reconciliation.
Read the Article →
Continuity relationships illustrating how a trusted source identifier can remain stable while custody, publisher authority, delivery integrity, and artifact provenance change.
Source Custody & Provenance

The Registry URL Was Right. The Source Wasn’t.

Coder’s registry compromise showed that users could contact the legitimate registry hostname while attacker-controlled infrastructure served malicious modules. The case distinguishes source identity from source custody: a trusted identifier remains trustworthy only while control of the delivery path and artifact lineage can be established.
Read the Article →
Records governance framework showing benefit records, calculations, rights information, and decision context converging into a notice that explains and reconstructs an institutional overpayment determination.
Decision Reconstruction

The System Calculated the Debt. The Notice Couldn’t Explain It.

SSA OIG found widespread deficiencies in overpayment notices even when underlying systems had established the overpayment state. The case shows that a consequential decision is not fully recorded unless its evidence, calculation, context, authority, and challenge rights remain reconstructable in the institutional record.
Read the Article →
Graphic illustrating an overlooked data-export security incident: a red error line in system logs appears beside search results that return routine export records, showing why retrieval without context can miss critical evidence.
AI Retrieval and Institutional Continuity

The Incident Was in the Logs. The Search Didn't Find It.

Anthropic disclosed a fourth real-system cybersecurity incident that was already preserved in its transcript corpus but missed by an initial AI-assisted search. The case demonstrates a central continuity principle: retaining a record does not make it Institutional Memory unless retrieval can reliably reconstruct it as evidence—and the system being audited should not become the sole interpreter of its own actions.
Read the Article →
next step

Continue Your Continuity Journey

Explore the GovKM Continuity Framework or connect with GovKM to discuss your organization’s continuity, governance, and AI-readiness priorities.
FRAMEWORK

Explore the GovKM Continuity Framework

Understand the domains, relationships, principles, and implementation architecture that support organizational continuity.
CONNECT

Talk With GovKM

Discuss organizational continuity, AI readiness, governance architecture, research collaboration, or implementation priorities.