Knowledge Foundation

Cognitive infrastructure as public domain

The Free Framework Library

Frameworks are the operational interface between cognitive automation and applied use. Without frameworks, cognitive automation is raw capability that many people cannot deploy effectively. With frameworks, the capability can become usable for specific tasks that matter.

Current status. Ora publishes a working public catalog and framework material. It is not a complete canonical Foundation library, and no Foundation contribution, review, certification, or distribution system is operating. The earlier seven-component proposal and the separate provisional Passion/Operation model remain unresolved.

Beyond enabling task completion, a future Foundation library could be one instrument for chokepoint response. The proposed selection logic asks whether a framework addresses an underlying need where a commercial chokepoint extracts excess value. A framework that helps a household file its own taxes for free is an example of the kind of public-domain alternative this proposal has in mind.

Launch list

The following is a proposed work list, not a settled Foundation catalog. It is a set of examples of needs that future framework work might address:

  • 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

The proposed governance pattern draws on Apache, Wikipedia, and Creative Commons. A future Foundation could publish specifications for framework structure, documentation, testing, and version history. Contributors could develop alternatives against those specifications, and multiple frameworks for the same task could coexist. None of that intake or review machinery exists yet.

The intended role would be specification authorship and library infrastructure, not authorial control over individual frameworks. Forks, modifications, and independent collections would remain possible whether or not a future Foundation accepts a contribution.

Contribution flow

The intended contribution pattern adapts open-source ideas to natural-language artifacts rather than code. The contribution barrier is domain expertise, not necessarily technical skill. A legal aid attorney could contribute a benefits-application framework because she knows what the form requires; she would not need to write the runtime. Natural language is the source code. This is a design proposition, not a current intake promise.

  1. A future contributor identifies a framework need or develops a prototype.
  2. The contributor could publish it against a future specification standard.
  3. A future review process could compare it with that standard.
  4. If a future library adopted it, attribution and version history would be preserved.
  5. Revisions would remain public and could follow the same proposed pattern.

Relationship to Ora and to external maintenance

Existing Ora installations can use the framework material that is currently shipped with the project. No Foundation-managed propagation system is claimed. Users can also use material from forks or independent collections; a future Foundation library would be 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 — a future Foundation library could distribute the methodology and worked examples rather than maintaining the specific form libraries indefinitely. The maintenance work would be properly placed with organizations that already have the domain expertise.

Candidate future framework areas

Possible future work could include frameworks addressing the following needs:

  • Tax preparation framework — 1040-EZ as a paradigm case. A future project could consider the gap between simple filing needs and commercial tax preparation. Natural extensions might include 1040 long form, common state returns, and small-business filings.
  • Public benefits application framework — IHSS California as a complexity demonstration. A future project could consider ways to close the gap between need and access for low-income populations. Natural extensions might include veterans benefits, Social Security, immigration applications, and 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 working framework catalog is available at stable preview URLs. It should not be read as a claim that a complete canonical Foundation library already exists.