Transparency Infrastructure Protection

Summary

Field	Description
Scope	All federal public transparency mechanisms (databases, dashboards, FOIA portals, APIs)
Problem	Transparency tools removed without notice or replacement; data access degraded without accountability
Reform	90-day notice + functional replacement + GAO certification required before removal; automatic restoration for violations
Implementation	Agencies must register transparency tools; removal triggers notice/replacement/certification process
Enforcement	Non-compliant removal = automatic restoration order; officials personally liable for restoration costs
ROI	Net +$2.59B over 10 years (4.5:1 ROI)
Prerequisites	None identified

Current Status

Existing Law: Freedom of Information Act (5 U.S.C. § 552); E-Government Act of 2002 (44 U.S.C. § 3501 note); Open Government Directive (M-10-06); OPEN Government Data Act (44 U.S.C. § 3502); Federal Funding Accountability and Transparency Act (31 U.S.C. § 6101 note)

Current Authority: Agencies must publish certain data under various statutes. FOIA requires disclosure upon request. Data.gov aggregates federal datasets. USAspending.gov tracks federal expenditures. Individual agencies maintain program-specific dashboards and APIs.

Existing Limitations: No protection against removal of existing transparency tools. Agencies may discontinue databases, dashboards, or APIs without notice. No requirement for functional replacement. No certification that replacement maintains access quality. FOIA covers disclosure upon request but not proactive publication infrastructure. Data.gov listing is voluntary for many datasets.

Problem

Specific Harm: EPA air quality dashboards taken offline without replacement (2017).¹ USDA food safety data access degraded.² DOL workplace injury database discontinued.³ Census data API changes broke dependent applications without notice.⁴ Researchers, journalists, and public lose access to data used for accountability, with no recourse. Once transparency infrastructure is removed, rebuilding it requires years and significant resources.

Who is Affected: Journalists using federal data for accountability reporting. Researchers dependent on federal datasets. Civic technology organizations building on federal APIs. State/local governments using federal data for planning. General public seeking government accountability information. Businesses using federal data for market analysis.

Gaps in Current Law: No notice requirement before transparency tool removal. No replacement adequacy standard. No certification process for changes. No automatic remedy for improper removal. No registry of existing transparency infrastructure. Officials face no consequence for degrading public access.

Accountability Failures: Transparency tools removed during administration transitions without documentation. Budget cuts used to justify discontinuation without assessing public impact. API changes made without stakeholder notice. No mechanism to challenge removal decisions. Restoration requires litigation or Congressional intervention taking years.

Proposed Reform

Primary Policy Change: Protect existing public transparency infrastructure by requiring notice, functional replacement, and certification before removal, with automatic restoration for non-compliant removal.

New Requirements:

Federal Transparency Registry

GSA shall establish and maintain Federal Transparency Registry cataloging all federal transparency mechanisms including:

Public databases and data portals
Performance dashboards
FOIA portals and reading rooms
Public APIs providing government data
Reporting systems and public filings databases
Real-time data feeds

Agencies must register all existing transparency tools within 180 days of enactment and register new tools within 30 days of deployment. Registry published at Transparency.gov with: tool name, agency, URL, data description, user documentation, API specifications (if applicable), and creation date.

Public Accessibility Requirement: Any system accessible via public internet, including those nominally designated "internal" but accessible without authentication from non-agency IP addresses, shall be registered and subject to removal protections.

Removal Protection Process

Before removing, disabling, or materially degrading any registered transparency mechanism, agency must:

Step 1 - Public Notice (90 days before removal)

Publish notice in Federal Register
Post notice on agency website and affected tool
Notify registered API users directly (for APIs)
Notice must include: reason for removal, timeline, description of replacement (if any), public comment instructions

Step 2 - Functional Replacement Demonstration

If replacement planned: demonstrate equivalent or superior public access
Replacement must provide: same data scope, comparable query capability, equivalent update frequency, compatible formats for existing users
If no replacement: document why data/function is no longer needed with supporting evidence

Step 3 - GAO Certification

GAO reviews replacement adequacy within 60 days of agency submission
Certification criteria: data completeness, access quality, user transition support, format compatibility
GAO publishes certification decision with rationale
Denial requires agency remediation before proceeding

Step 4 - Implementation

Only after GAO certification (or 60-day deemed approval if GAO fails to act) may agency proceed with removal
30-day transition period after certification for user migration
Agency must maintain redirect/notice at old URLs for minimum 2 years

72-Hour Technical Correction Window (Safety Valve)

Before GAO denial triggers remediation requirement:

Agency may invoke 72-hour window demonstrating specific procedural or technical error in GAO assessment
Must identify: specific error, correct information, why certification should be granted
GAO reviews and issues final determination
Bad-faith invocation = expedited denial + fee assessment
Does not apply to substantive adequacy disputes (those proceed through normal appeal)

Temporary Suspension Provisions

Transparency mechanisms may be temporarily suspended without full removal process only when:

Documented security vulnerability requires immediate action
Relevant agency IG reviews and approves security justification within 48 hours
Maximum suspension: 30 days
Automatic restoration if not extended by Congressional notification
Extension requires: written justification to relevant Congressional committees, IG continued approval, 30-day increments maximum

Suspension may NOT be used to:

Avoid removal process requirements
Respond to politically unfavorable data
Address resource constraints (budget is not security justification)

Deemed Approval Fallback

If GAO fails to issue certification decision within 60 days:

Deemed approval does not apply if GAO requests extension (maximum 30 days additional)
GAO extension requests limited to 2 per agency per year to prevent gaming
If no extension requested and 60 days elapsed, agency removal request deemed approved
GAO must publish explanation for any delay
Pattern of missed deadlines (3+ in 12 months) triggers Congressional notification and GAO IG review

Enforcement

Automatic Restoration: Removal without compliant process triggers automatic restoration order:

GAO issues restoration directive within 14 days of identifying non-compliance
Directive enforceable as subpoena in U.S. District Court
Agency must restore tool within 30 days or show cause
Court may order restoration with contempt sanctions for non-compliance

Personal Liability: Officials who directed non-compliant removal are personally liable for:

Restoration costs (technical, administrative, legal)
User harm remediation (documented losses from access interruption)
Not dischargeable in bankruptcy
Enforced through Court of Federal Claims

Pattern Violations: Agency with 3+ non-compliant removal attempts in 24 months:

Automatic GAO pre-approval required for ANY transparency tool changes
Agency CIO personally certifies compliance for each change
IG audit of transparency practices within 90 days

New Prohibitions:

Removing registered transparency tool without completing protection process
Using security suspension to circumvent removal requirements
Degrading tool performance to discourage use without triggering removal process
Removing API access while maintaining internal functionality
Altering data retroactively without public notice and versioning
Deleting historical data from public access (archival required)

Enforcement:

Violation	Consequence
Removal without process	Automatic restoration order (14 days)
Failure to restore	Court enforcement + contempt
Official directing violation	Personal liability for costs
Pattern violations	Mandatory pre-approval + IG audit
Security suspension abuse	Immediate restoration + referral
Data deletion	Restoration from backup + criminal referral if willful

Definitions:

"Transparency mechanism": Any federal system providing public access to government data, including databases, dashboards, portals, APIs, and reporting systems, whether required by statute or voluntarily established
"Material degradation": Change that reduces data scope by >10%, increases access latency by >100%, removes query capabilities, changes formats incompatibly, reduces update frequency by >50%, or for APIs: breaking changes to endpoints without 90-day deprecation notice, removal of query parameters, or changes to response schemas incompatible with documented usage patterns
"Functional replacement": Successor system providing equivalent data scope, comparable access quality, compatible formats, and adequate transition support for existing users
"Registered API users": Developers who have obtained API keys or registered for access notifications through agency developer portal

What Changes

Before: Agencies remove transparency tools without notice—EPA dashboards disappear, DOL databases go offline, APIs change without warning. No replacement requirement. No certification process. Users discover removal after the fact. Restoration requires litigation or Congressional intervention taking years. Officials face no consequence. Public accountability data lost permanently.

After: All transparency tools registered at Transparency.gov. Removal requires 90-day public notice + functional replacement demonstration + GAO certification. Security suspension limited to 30 days with IG approval. Non-compliant removal triggers automatic restoration order enforceable in court within 14 days. Officials personally liable for restoration costs. Pattern violators require pre-approval for any changes. Historical data must be archived, not deleted.

Structural Prerequisites

Prerequisite	Dependency Type	Notes
None identified	—	Builds on existing GAO, GSA, IG infrastructure

ROI

Federal Budget Impact (10-Year, CBO-Scoreable)

Costs:

Item	10-Year
Federal Transparency Registry (GSA)	$0.08B
GAO certification capacity	$0.15B
Agency compliance (notice, documentation)	$0.22B
Transition support for users	$0.05B
Contingency (15%)	$0.08B
Total	$0.58B

Savings:

Item	Gross	Capture	Net
Avoided rebuilding costs (prevented removal)	$3.5B	40%	$1.40B
Reduced FOIA burden (maintained proactive access)	$2.0B	35%	$0.70B
Research continuity (uninterrupted data access)	$1.5B	30%	$0.45B
Civic tech ecosystem preservation	$1.2B	25%	$0.30B
Litigation avoidance (clear process)	$0.8B	40%	$0.32B
Total	$9.0B		$3.17B

Result: Net +$2.59B · ROI 4.5:1

Societal Benefits

Benefit	Annual	NPV (3%)	NPV (7%)
Journalism/accountability continuity	$0.8B	$6.8B	$5.6B
Research data access preservation	$0.5B	$4.3B	$3.5B
Public trust in government transparency	$0.4B	$3.4B	$2.8B
Civic technology ecosystem	$0.3B	$2.6B	$2.1B
Total	$2.0B	$17.1B	$14.0B

Summary

Category	10-Year	Notes
Federal Budget	+$2.59B (4.5:1)	CBO-scoreable
Societal	$14.0B - $17.1B	NPV at 7% - 3%

Confidence: MEDIUM for avoided rebuilding (depends on removal prevention rate). MEDIUM-HIGH for FOIA burden reduction (well-documented relationship). MEDIUM for civic tech value (ecosystem effects difficult to quantify).

ROI Verification Checklist

Totals verified: $0.58B costs, $3.17B net savings
Capture rates conservative: 25-40% reflects behavioral uncertainty
NPV timing: Registry costs year 1, savings accrue years 2-10
ROI calculation: ($3.17B - $0.58B) / $0.58B = 4.5:1

References

Environmental Data & Governance Initiative (EPA data removal documentation, 2017-2020)
Data Coalition reports (federal data access degradation incidents)
Sunlight Foundation (transparency tool discontinuation tracking)
Census Bureau API change documentation and developer feedback
OPEN Government Data Act, 44 U.S.C. § 3502
Federal Data Strategy (data.gov requirements)
GAO-21-200 (federal data management practices)
18F API Standards (federal API best practices)
UK Open Government National Action Plan (transparency protection model)
EU Open Data Directive 2019/1024

Change Log

2025-01-20 - Initial Draft: Created to implement Design Principle 26 (Transparency Infrastructure Protection). New principle added 2025-01-18; no prior implementing legislation.
2025-01-20 - Red Team Fixes: Fixed Summary ROI (4.2:1 → 4.5:1, $2.1B → $2.59B). Added public accessibility requirement (closes "internal tool" labeling loophole). Added deemed approval extension limit (prevents gaming). Added API versioning to material degradation definition.