Litepaper v0.1 // August 2026

AI Needs Permission.

“Build the network first. Distribute ownership later.”

A human-rooted authority and defense layer for the autonomous internet — with a proposed community-first PZRO economic layer targeted for 2027.

Forward-looking document. Architecture, token supply, allocations, roadmap, governance and launch mechanics are proposed and may change before implementation. No token is offered for sale through this Litepaper and Genesis participation does not guarantee a future allocation.
01 / Executive Summary

Permission should scale with intelligence.

Permission Zero proposes five connected layers: Human Proof, Agent Identity, Delegated Authority, Action-Time Policy and Swarm Defense. Genesis is the research/community phase. PZRO is a proposed future network asset — not a token currently offered for sale.

02 / The Problem

The internet was built for human operators.

Autonomous agents separate human intent from machine execution, while one operator can coordinate a machine-scale population. The web needs to reason about authority and aggregate behavior, not only accounts and credentials.

03 / Permission Zero Thesis

Human-rooted authority. Machine-speed execution.

ROOTHuman / org
IDAgent identity
GRANTDelegation
POLICYAction time
DEFENDSwarm layer
04 / Human Layer

Prove human. Reveal less.

Use the minimum proof required by the relying service at an accepted assurance level rather than treating every trust decision as permanent full-identity disclosure.

05 / Agent Identity & Delegated Authority

Authority is explicit, scoped, time-bound and revocable.

An agent should identify itself as software and present the authority it received — capability, resource, limits, expiry and revocation state — instead of inheriting broad permanent account power.

06 / Swarm Defense & League

Defend against coordinated objectives.

Swarm Defense studies population-level abuse across accounts and endpoints. Swarm League is the controlled Red-vs-Blue research environment for testing those defenses safely.

07 / Genesis Community

Genesis starts before PZRO.

The first phase centers on research, builders, specifications, simulations and meaningful contribution history. X is the public channel; Discord the builder/support layer; GitHub the technical evidence layer; Telegram is announcement-only.

No guaranteed airdrop. Genesis participation does not itself create a right to PZRO. A future community distribution, if approved, will depend on final eligibility, anti-Sybil, legal and network requirements.
08 / PZRO — Proposed 2027

1B proposed fixed supply. 90% public/community ecosystem target. No public presale.

50%Genesis Community
20%Long-term Rewards
10%Community Treasury
5%Builder / Security Grants
5%Protocol Liquidity
8%Company / Core
2%Strategic Reserve

Allocation is not circulation. The model anticipates staged community release, long-term rewards, timelocks and vesting rather than putting 90% into circulation on day one.

09 / Contract & Governance Principles

Immutable supply after final deployment.

The preferred future architecture is a non-upgradeable fixed-supply core token with no post-genesis mint function, plus separate audited distribution, vesting, treasury and governance contracts with transparent roles and timelocks.

10 / Indicative Roadmap

Research → Community → Prototype → Validation → Final issuance decision.

2027 is a target, not a commitment. The roadmap may change, slow down or stop because of regulation, security, technical evidence, community behavior or market conditions.

11 / Forward-Looking Notice

This Litepaper is a living design document.

Nothing here is an offer to sell, investment advice, a guarantee of token allocation, exchange listing, liquidity or future value. If Permission Zero proceeds to issuance, formal jurisdiction-specific issuance documents, disclosures and security reviews will be prepared as required.