> For the complete documentation index, see [llms.txt](https://docs.assembly.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.assembly.digital/problem-were-tackling.md).

# PROBLEM WE'RE TACKLING

Everyone wants a good government that is open, transparent, and effective. To get there, we need access to government data to build better tools accessible to the public.

But government data is unique: Government entities generate data used by the government, private industry, public groups, and citizens.

* The data is publicly owned.
* The data source is also a primary consumer.
* And often, the data requires heavy compliance because it can be sensitive for privacy or security purposes.

**The Challenge**

There are two related challenges.

First, government data policies, practices, and technology are fragmented. The lack of technical, policy and procedural standards creates inefficiencies at all levels of government —federal, state, local, and municipal— and prevents government entities from sharing data.

And second, the vast majority of the 19k government entities in the United States lack the resources, technical, financial, and know-how to build technology solutions.

**Why this matters**

As a result, a small group of large tech companies controls the market. But this creates vendor lock-in and high prices, preventing the vast majority of government entities from entirely publishing their data and making it accessible.

Instead, small government entities hack together legacy digital tools, paper, and a la carte services.

It’s no surprise that government data is inaccessible and the $3T open data economy is untapped. It’s an underground freshwater lake we all know exists, but nobody knows how to pump the water out.

But if there were a standard that allowed government entities to share data more efficiently, it would benefit the economy, reduce the costs of government services, and strengthen democracy.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.assembly.digital/problem-were-tackling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.