Document Version: 2.0.0 Last Updated: 2026-01-04 Status: Ready for Submission

This document declares the academic intent of the Rotational Packet Protocol (RPP) specification and provides guidance for citation, reproduction, and scholarly use.

This specification is published as defensive prior art under the following principles:

1. Public Domain Intent: The RPP addressing architecture is released to establish public domain status for the core technical concepts.

2. Patent Prevention: This publication is intended to prevent patent enclosure by any party, including the original authors, by establishing documented prior art with verifiable timestamps.

3. Open Implementation: Any party may implement this specification without licensing obligations, subject only to attribution requirements of the applicable licenses (Apache 2.0 for code, CC BY 4.0 for documentation).

4. Irrevocability: This prior art declaration is irrevocable. Future versions of this specification may add features but cannot retract the public domain status of concepts published herein.

• Purpose: DOI assignment for permanent citation
• Status: Ready for submission
• Expected DOI: Pending assignment
• Repository Integration: GitHub release → Zenodo automatic archival

• Purpose: Visibility in computer science community
• Category: cs.OS (Operating Systems) or cs.DC (Distributed Computing)
• Status: Ready for submission pending endorsement
• Document: DEFENSIVE_PUBLICATION.md

@techreport{rpp2026,
  title     = {Rotational Packet Protocol ({RPP}): A Ra-Canonical Semantic
               Addressing Architecture for Consent-Aware Memory Systems},
  author    = {Lennon, Alexander Liam},
  year      = {2026},
  month     = {January},
  version   = {2.0.0},
  url       = {https://github.com/anywave/rpp-spec},
  note      = {Open specification, Apache 2.0 + CC BY 4.0}
}

Lennon, A. L. (2026). Rotational Packet Protocol (RPP): A Ra-Canonical semantic
addressing architecture for consent-aware memory systems (Version 2.0.0).
https://github.com/anywave/rpp-spec

A. L. Lennon, "Rotational Packet Protocol (RPP): A Ra-Canonical Semantic Addressing
Architecture for Consent-Aware Memory Systems," version 2.0.0, Jan. 2026.
[Online]. Available: https://github.com/anywave/rpp-spec

Once a Zenodo DOI is assigned, citations should include:

@techreport{rpp2026,
  title     = {Rotational Packet Protocol ({RPP}): A Ra-Canonical Semantic
               Addressing Architecture for Consent-Aware Memory Systems},
  author    = {Lennon, Alexander Liam},
  year      = {2026},
  month     = {January},
  version   = {2.0.0},
  doi       = {10.5281/zenodo.XXXXXXX},
  url       = {https://github.com/anywave/rpp-spec}
}

For reproducibility, cite the specific version used:

Lennon, A. L. (2026). Rotational Packet Protocol (RPP) (Version 2.0.0).

Git tags and GitHub releases provide permanent references to specific versions.

• Research: Use RPP concepts in academic research without restriction
• Publication: Publish analyses, extensions, or critiques with attribution
• Teaching: Use specification in educational contexts with attribution
• Implementation: Create conforming implementations under Apache 2.0

1. For Specification Use: Cite using formats above
2. For Code Derivation: Include Apache 2.0 license notice
3. For Documentation Derivation: Include CC BY 4.0 attribution

• Commercial use of implementations
• Modification and redistribution
• Creation of derivative works
• Competitive implementations

The canonical Python implementation (reference/python/rpp_address.py) serves as the authoritative reference for resolving ambiguities in the specification text.

Official test vectors (tests/test_vectors.json) enable independent verification of implementation correctness.

All specification history is preserved in Git. Any statement about RPP can be verified against the historical record.

For questions regarding:

• Citation format
• Academic collaboration
• Endorsement for arXiv submission
• Clarification of specification intent

Open an issue on GitHub: https://github.com/anywave/rpp-spec/issues

Publication timestamps can be independently verified via:

• Git commit history
• GitHub release timestamps
• Zenodo archival timestamp (after DOI assignment)
• arXiv submission timestamp (after acceptance)

This publication establishes prior art for:

1. 32-bit Ra-Canonical semantic addressing format with θ/φ/h/r fields (v2.0)
2. Ra-derived field semantics: 27 Repitans, 6 RAC levels, 5 Omega tiers
3. Legacy 28-bit semantic addressing format with Shell/Theta/Phi/Harmonic fields (v1.0)
4. Spherical coordinate addressing for functional classification
5. Consent-aware address resolution as intrinsic property
6. Bridge architecture for semantic routing to existing storage
7. Sector-based functional classification mapped to Ra System constants
8. RAC-level encoding for access sensitivity

This list is illustrative, not exhaustive. The complete prior art scope encompasses all concepts described in the specification documents.

This document is part of the RPP specification and is released under CC BY 4.0.