PAGI
Bare-Metal Infrastructure Standard

Community-driven specification for sovereign, decentralized infrastructure

PAGI is a Rust-based bare-metal runtime enabling decentralized MESH and COMPUTE infrastructure. Open standards adopted by choice, not coercion. Any DePIN, sovereign infrastructure, or decentralized network can build on PAGI.

Read Specifications Submit Proposal Join Community

Open by Design

All specifications, discussions, and implementations are public. No hidden processes. Transparency is the foundation of trust.

Immutable Specs

Published specifications never change. Updates require new versions. Corrections are tracked separately as errata—just like RFCs.

🌍

Vendor Neutral

No corporate veto power. Consensus-driven decisions. Funded transparently. Maintained by the community, for the community.

🔧

Production Ready

Reference implementations prove the spec works. Test suites validate compatibility. Real projects use PAGI in production.

📖

RFC-Style Process

Draft → Proposed → Final. Clear advancement criteria. Community reviews. Documented decision-making that respects prior art.

🚀

Driven by Adoption

PAGI succeeds because implementations prove it works—not because there's a committee saying so. The spec is the brand.

Active Specifications

PAG-001: Core Runtime Specification

Rust bare-metal runtime, initialization, module loading

Final
PAG-002: MESH Protocol Definition

Networking, topology discovery, peer communication

Proposed
PAG-003: COMPUTE Orchestration Model

Task scheduling, resource verification, allocation

Draft
PAG-004: Proof-of-Physical-Work

Hardware attestation, cryptographic verification, incentive proofs

Draft

View all specifications →

Community

Mailing Lists

Join discussions on proposals, specifications, and implementation challenges.

GitHub

Submit drafts, propose changes, review specs. Everything is version controlled.

Monthly Calls

Spec review meetings, recorded and transcribed. Async-first, synchronous optional.

How to Submit a Proposal

Anyone can propose a new specification. The process is:

  1. Discuss: Post your idea to pagi-proposals@pagi.community (2+ weeks feedback)
  2. Draft: Create a formal Internet-Draft style document
  3. Submit: Open a PR to the community repository
  4. Review: Community feedback for 4+ weeks (DRAFT phase)
  5. Propose: Request advancement to PROPOSED status
  6. Consensus: 30-day review, maintainer vote
  7. Final: Assign PAG number, publish immutably

Read Full Submission Guide