Contributing to the Reciprium Spec

This repository is maintained as a standard, not just a code drop. Changes to normative behavior should follow a lightweight RFC flow.

RFC Process (Minimal)

  1. Propose
    • Open an issue titled RFC: <short title>.
    • Include problem statement, proposed change, compatibility impact, and alternatives considered.
  2. Discuss
    • Maintainers and contributors review in the RFC issue (or linked PR).
    • Keep discussion focused on interoperability, backward compatibility, and implementation burden.
  3. Accept or Reject (with rationale)
    • A maintainer records one of:
      • Accepted: merge path + rollout notes.
      • Rejected: clear rationale and, when possible, guidance for revisions.
    • Every final decision must include rationale in writing.

Pull Requests

  • Keep changes scoped.
  • Update relevant schemas/docs/examples together.
  • Include verification evidence (commands and outcomes).
  • For signature/canonicalization changes, include or update shared test vectors.

Compatibility Rule

Backward-incompatible changes require explicit RFC acceptance and versioning impact notes before merge.