Submit a proposal

1. Start a discussion

• Email proposals@pagi.community with subject [PRE-DRAFT] Your Idea Here.
• Describe the problem, proposed solution, and rough direction.
• Aim for at least two weeks of discussion before opening a formal draft PR.

2. Write the draft

Use Markdown. Recommended sections: Abstract; Introduction; Requirements / design goals; Technical specification; Implementation considerations; Security and privacy; References to other PAGs; Authors and contributors.

Follow RFC 2119 / BCP 14 for MUST / SHOULD / MAY.

File name: pagi-draft-<topic>-<version>.md (example: pagi-draft-mesh-discovery-01.md).

3. Open a pull request

• Fork the repository.
• Add your file under specs/drafts/.
• Request review; iterate with version bumps (01 → 02) for substantive changes.

4. DRAFT phase

Minimum four weeks of community feedback for typical documents. Six months without activity may retire a draft — renew with an update if still relevant.

5. Advance to PROPOSED

Request advancement on the mailing list with evidence of addressed feedback and interest from implementers where applicable.

6. PROPOSED review

Thirty days minimum; blocking technical issues must be resolved before a consensus call.

7. FINAL

After successful review, editors assign a permanent PAG number and move the document to specs/final/. FINAL texts are immutable; fixes use errata and successor specs.

Full detail: spec-process.md in the repository.