<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<rfc ipr="trust200902" docName="draft-singh-apex-psi-07-01" category="info" submissionType="independent">
  <front>
    <title abbrev="draft-singh-apex-psi-07">PSI-07: Organic Production Attestation</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-07 defines a standard signal format for regulatory events detected by automated monitoring systems.  The format is a signed JSON envelope carrying the event classification, evidence hash, and jurisdiction code, enabling autonomous reporting to one or more regulators without human intervention.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="s-1" title="Introduction">
      <t>Current regulatory reporting requires human triage.  PSI-07
defines an automated signal format that monitoring systems emit
when a predicate triggers, and that regulator gateways accept
as a valid filing.</t>
    </section>
    <section anchor="s-2" title="Signal Envelope">
      <t>{
&quot;psi&quot;: &quot;07&quot;,
&quot;event_id&quot;:     &quot;&lt;UUID v4&gt;&quot;,
&quot;classification&quot;: &quot;&lt;taxonomy code from registry&gt;&quot;,
&quot;severity&quot;:     &quot;info | warning | breach&quot;,
&quot;jurisdiction&quot;: &quot;&lt;ISO 3166-2 or regulator code&gt;&quot;,
&quot;evidence&quot;:     &quot;&lt;sha256 bundle&gt;&quot;,
&quot;detected_at&quot;:  &quot;&lt;RFC 3339&gt;&quot;,
&quot;reported_to&quot;:  [&quot;&lt;regulator endpoint URL&gt;&quot;],
&quot;signature&quot;:    &quot;&lt;Ed25519 base64url&gt;&quot;
}</t>
    </section>
    <section anchor="s-3" title="Autonomous Reporting">
      <t>A conformant monitor MUST attempt delivery to at least one
endpoint in reported_to.  A conformant regulator gateway MUST
accept signals without prior registration.</t>
    </section>
    <section anchor="s-4" title="Security Considerations">
      <t>Signals may trigger enforcement action.  Monitors SHOULD
include sufficient evidence to permit independent verification
without requiring access to the monitor's internal state.</t>
    </section>
    <section anchor="s-5" title="IANA Considerations">
      <t>None.</t>
    </section>
    <section anchor="s-6" 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>