Beyond enabling task completion, the framework library is the Foundation's primary instrument for chokepoint elimination. Each launch-critical framework is selected because it addresses an underlying need where commercial chokepoints have extracted excess value. A framework that lets a household file its own taxes for free dissolves a specific commercial pinch point that has been lobbied to remain in place for decades.

Launch list

The framework library is launch-critical, not long-term. Whatever isn't in the library at launch may not exist when people need it most because the disruption itself disrupts framework-development capacity. The launch list:

  • Tax preparation — 1040-EZ as the paradigm case. The TurboTax monopoly Intuit has lobbied to preserve for years dissolves when a free framework can guide any household through filing.
  • Public benefits applications — IHSS California as the complexity demonstration. Veterans benefits, Social Security, immigration, SNAP as natural extensions. The gap between need and access for low-income populations is structural; frameworks close it.
  • Basic legal documents — wills, contracts, leases. Routine legal work that should not require paying gatekeepers.
  • Basic medical information synthesis — synthesis only, not advice. Helps users prepare for clinical conversations.
  • Basic financial planning — household-level budgeting, debt management, retirement planning. Dissolves the advisory-fee structure that prices out moderate-income households.
  • Basic business operations — small enterprises, business plans, operating agreements, basic bookkeeping.

Governance model

Framework library governance follows the Apache / Wikipedia / Creative Commons pattern. The Foundation publishes specifications for what frameworks should look like — input format conventions, output format conventions, version-control conventions, documentation requirements, testing requirements. Contributors develop frameworks that meet the specifications. Frameworks meeting the specifications enter the library. Multiple frameworks for the same task can coexist; the library is not exclusive.

The Foundation's role is specification authorship and library infrastructure, not authorial control over individual frameworks. This distributes the cultural power that would otherwise concentrate in Foundation staff. The Foundation does not gatekeep alternative frameworks: forks, modifications, and entirely independent collections are welcomed and expected.

Contribution flow

Standard open-source patterns adapted for natural-language artifacts rather than code. The contribution barrier is domain expertise, not technical skill. A legal aid attorney can contribute a benefits application framework because she knows what the form requires; she does not need to write code. Natural language is the source code. This inverts the traditional open-source contribution model in a way that opens contribution to populations conventional open source largely excludes.

  1. A contributor identifies a framework need or develops a framework prototype.
  2. The contributor publishes the framework against the Foundation's specification standard.
  3. The framework is reviewed by domain experts and active library contributors against the specification.
  4. If accepted, the framework enters the library with attribution and version-control history.
  5. Subsequent revisions follow the same flow, with prior versions preserved.

Relationship to Ora and to external maintenance

The framework library is distributed with Ora and operates as the in-system menu of available capabilities. New frameworks added to the Foundation's library propagate to user installations through standard update mechanisms. Users can also install frameworks from forks or independent collections; the Foundation's library is one option, not the only one.

For domain-specific frameworks with high maintenance burden — government forms that change annually, regulations that update jurisdiction by jurisdiction — the Foundation distributes the methodology and worked examples rather than maintaining the specific form libraries indefinitely. The maintenance work is properly placed with organizations that already have the domain expertise.

Programs operated under this component

The framework library's launch programs are the launch-critical frameworks themselves, each of which addresses a specific commercial chokepoint:

  • Tax preparation framework — 1040-EZ as the paradigm case, in development. Dissolves the TurboTax monopoly Intuit has lobbied to preserve for decades. Natural extensions: 1040 long form, common state returns, and small-business filings.
  • Public benefits application framework — IHSS California as the complexity demonstration, in development. Closes the gap between need and access for low-income populations. Natural extensions: veterans benefits, Social Security, immigration applications, SNAP.
  • Basic legal documents framework — wills, contracts, leases. Routine legal work that should not require paying gatekeepers.
  • Basic medical information synthesis framework — synthesis only, not advice. Helps users prepare for clinical conversations.
  • Basic financial planning framework — household-level budgeting, debt management, retirement planning. Dissolves the advisory-fee structure that prices out moderate-income households.
  • Basic business operations framework — small enterprises, business plans, operating agreements, basic bookkeeping logic.

The canonical framework library is hosted at stable URLs.