---
title: "The Open Framework"
description: "An early digital public infrastructure concept for civil-society coordination, published as a front-end prototype rather than as live national infrastructure."
canonical: "https://www.ayushrai.site/products/the-open-framework/"
last-updated: "2026-10-11"
---

# The Open Framework

Source: https://www.ayushrai.site/products/the-open-framework/
Markdown: https://www.ayushrai.site/products/the-open-framework.md

An early digital public infrastructure concept for civil-society coordination, published as a front-end prototype rather than as live national infrastructure.

Stage: Building. A public website explains the intended trust and discovery layer. The repository is a Vite and React prototype with mock sign-in. It does not run verification, consent, or a durable institutional backend.
Category: Digital public infrastructure.

## Thesis

NGOs, donors, talent, and oversight institutions need a shared way to find one another and to see which claims have been checked, without a vendor owning the sector.

## Audience

- NGO and civil-society operators
- Donors looking for credible discovery
- People exploring civil-society work
- Policy and oversight institutions

## Problem

Civil-society organizations, donors, talent, and institutions lack a shared, consent-aware way to discover one another and to tell which organizational claims have been checked.

## Approach

Treat verification, consent, governance, and auditability as the product. Publish the concept and a front-end prototype first, and keep backend technology in the design-goal column until it is built.

Discovery, verification, and compliance are fragmented. A coordination layer only helps if consent, governance, and auditability are product requirements, not a later policy memo.

1. An organization would submit identity and statutory records once.
2. A trust layer would check what it can, keep documents consent-scoped, and leave a review trail.
3. Donors and talent would discover organizations from those verified claims, not from an unscoped directory.

## Architecture

- Frontend: Implemented: Vite, React, TypeScript, Tailwind CSS, shadcn/ui, React Router, and TanStack Query.
- Auth: Implemented as a demo: login writes a mock user to localStorage. There is no identity provider.
- Infra: The public site is deployed on Vercel as a single-page app.
- Design goals, not present as services in this repository: federated discovery, progressive verification, consent-scoped documents, immutable audit logs, and a cloud-agnostic institutional backend.

## Implemented

- Public narrative, role entry points, and screens for NGOs, donors, talent, governance, and a registry search.
- Client-side routing and a mock authenticated session.

## Experimental

- The live site still presents illustrative scale figures, partner names, and an operational-status badge. Those are prototype copy, not measured deployment.

## Planned

- A real verification workflow, consent records, governance stewardship, and any backend that could support them.

## Open questions

- What is the thinnest verification step an organization will actually complete?
- How federated can discovery be while remaining auditable?
- Who stewards a neutral layer if no single vendor should own it?

## Trade-offs

- A wide prototype makes the product idea visitable, and it also makes unfinished portals look more real than they are.
- Institutional backends (and the choice between them) stay out of the architecture claim until a service exists to compare.

Live site: https://the-open-frameworks.vercel.app/
Source repository: https://github.com/ayushrai-hub/the-open-framework
Case study: /work/the-open-framework

_Unverified award metrics are omitted. Wording matches the public site._