// RFC Process

Propose changes to the protocol.

OXP evolves through a lightweight RFC process. Anyone can draft — maintainers review for scope, security, and cross-host implications. Discussion happens in the open.

// Lifecycle

  1. STAGE 0
    Draft

    Sketch the problem and a rough proposal in GitHub Discussions. No format required.

  2. STAGE 1
    Proposal

    Open a PR against `spec/rfcs/` with a numbered RFC document. Solicit feedback from maintainers.

  3. STAGE 2
    Review

    Maintainers review for scope, security, and cross-host implications. Iterate in the PR.

  4. STAGE 3
    Accepted

    Merged with a stable RFC number. Implementation tracked in a follow-up issue.

  5. STAGE 4
    Shipped

    Reflected in the spec, host adapters, and CLI. Released under semver.

// RFC template

# RFC-NNNN: <title>

- **Author(s):** <github handle(s)>
- **Status:** Draft
- **Created:** YYYY-MM-DD
- **Target:** spec | runtime | host-* | cli | sdk

## Summary
One paragraph: what changes and why.

## Motivation
The problem this solves. Concrete use cases.

## Detailed design
The proposal. Be precise — include schemas, API shapes, error modes.

## Security considerations
Permissions, sandbox impact, supply-chain implications.

## Backwards compatibility
What breaks. Migration path.

## Alternatives
What else was considered and why it was rejected.

## Unresolved questions
Open items to resolve before acceptance.
← Back to Community