Ecosystem/Foundation Governance
Foundation Charter & Open Governance

Open Governance for Sovereign Finance

OpenSource Finance is organized as an independent, transparent open-source collective. We build high-rigor financial infrastructure governed by community consensus, mathematical determinism, and permissive Apache 2.0 licensing.

Founding Principles

The constitutional commitments that guide every architectural decision across all OSF projects.

Sovereign-by-Design

Financial institutions must maintain complete custody of transaction telemetry and customer PII. Our infrastructure is 100% self-hosted within your VPC or bare metal, with zero mandatory third-party data egress.

Performance Without Bloat

We reject the enterprise habit of wrapping simple tasks in 10+ Kubernetes microservices. Every engine is engineered as an efficient, single binary runnable by a single engineer.

Auditable & Deterministic Algorithms

Black-box AI and opaque proprietary scoring algorithms create severe regulatory risks. We use Google Common Expression Language (CEL) and open model architectures with cryptographically verifiable audit trails.

Global Equity & Inclusion

Rooted in the Bill & Melinda Gates Foundation LevelOne Project, our mission is to eliminate multi-million dollar vendor taxes so fintechs worldwide can access world-class fraud vigilance.

Project Maturity Lifecycle

Structured stages ensuring architectural stability, audit readiness, and production reliability.

Graduated (Flagship)

Production-ready, battle-tested in high-throughput environments, comprehensive documentation, and stable API guarantees.

Active Projects
Osprey (Core Monitoring Engine)
Incubating

Active development, public releases available for testing and integration, moving toward stable v1.0 specifications.

Active Projects
Osprey Narrator (Compliance AI)
Osprey Studio (Visual Policy IDE)
Sandbox & Emerging

Experimental tooling, community prototypes, and standard rail adapters undergoing architectural validation.

Active Projects
Osprey Cases (Triage Workbench)
Universal Financial Adapters (ISO 20022)

Request for Comments (RFC) Process

Major architectural changes, new protocol adapters, or rule syntax extensions follow our open RFC workflow.

01

Draft Proposal

Author an RFC markdown document outlining motivation, proposed interface specs, security considerations, and alternatives considered.

02

Public Review Period

Open pull request reviewed by community maintainers, risk officers, and infrastructure engineers over a 14-day consultation window.

03

Consensus & Implementation

Once consensus is reached, the RFC is merged into the specifications repository and scheduled for reference implementation.

Responsible Security Disclosure

Because OpenSource Finance projects handle live financial wire transactions and risk evaluations, we treat security reports with the highest urgency. Please report any potential vulnerabilities privately via GitHub Security Advisories or by emailing [email protected] before public disclosure.