<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<rfc ipr="trust200902" docName="draft-singh-apex-psi-05-01" category="info" submissionType="independent">
  <front>
    <title abbrev="draft-singh-apex-psi-05">PSI-05: Financial Disclosure Integrity</title>
    <author initials="K" surname="Singh" fullname="Kawaljeet Singh">
      <organization>Apex Intelligence Empire / ROCKYFILMS888 PTY LTD</organization>
      <address>
        <email>kawaljeet.singh3008@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="July" day="19"/>
    <area>General</area>
    <keyword>PSI</keyword>
    <keyword>cryptographic verification</keyword>
    <abstract>
      <t>PSI-05 defines the royalty schedule that MAY be levied by a publishing foundation for commercial, litigation, regulatory, or AI-training reuse of PSI public ledger data above a threshold defined by the foundation's charter.  It establishes a flat-rate per-row fee schedule, exemption categories, and an audit protocol.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="s-1" title="Introduction">
      <t>Public ledgers under PSI-04 are free to read and cite.  This
document defines a royalty framework for commercial reuse tiers,
ensuring the publishing foundation can sustain operations.</t>
    </section>
    <section anchor="s-2" title="Royalty Tiers">
      <t>Tier | Annual Row Threshold  | Per-Row Fee (AUD)
-----+----------------------+------------------
A  | &lt;= 1,000             | Free
B  | 1,001 - 100,000      | $0.001
C  | &gt; 100,000            | $0.0001 (negotiable)</t>
    </section>
    <section anchor="s-3" title="Exemptions">
      <t>The following uses are always royalty-free:
- Personal research and academic citation.
- Journalism and public-interest reporting.
- Regulatory compliance audits.</t>
    </section>
    <section anchor="s-4" title="Audit Protocol">
      <t>Any user may request a signed royalty statement from the
foundation.  The statement includes total rows served per entity
and the fee calculation.</t>
    </section>
    <section anchor="s-5" title="Security Considerations">
      <t>Royalty enforcement depends on honest self-reporting until a
regulatory framework mandates audit.</t>
    </section>
    <section anchor="s-6" title="IANA Considerations">
      <t>None.</t>
    </section>
    <section anchor="s-7" title="References">
      <t>[RFC2119]  Bradner, S., &quot;Key words for use in RFCs to Indicate
Requirement Levels&quot;, BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997.
[RFC8174]  Leiba, B., &quot;Ambiguity of Uppercase vs Lowercase in
RFC 2119 Key Words&quot;, BCP 14, RFC 8174,
DOI 10.17487/RFC8174, May 2017.
[RFC8785]  Rundgren, A., Jordan, B., and S. Erdtman, &quot;JSON
Canonicalization Scheme (JCS)&quot;, RFC 8785,
DOI 10.17487/RFC8785, June 2020.
Author's Address
Kawaljeet Singh
Apex Intelligence Empire
Balaclava, Victoria, Australia
Email: kawaljeet.singh3008@gmail.com
URI: https://apex-infrastructure.com</t>
    </section>
  </middle>
</rfc>