| Internet-Draft | draft-singh-apex-psi-07 | July 2026 |
| Singh | Expires 20 January 2027 | [Page] |
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.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 20 January 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.¶
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.¶
{ "psi": "07", "event_id": "<UUID v4>", "classification": "<taxonomy code from registry>", "severity": "info | warning | breach", "jurisdiction": "<ISO 3166-2 or regulator code>", "evidence": "<sha256 bundle>", "detected_at": "<RFC 3339>", "reported_to": ["<regulator endpoint URL>"], "signature": "<Ed25519 base64url>" }¶
A conformant monitor MUST attempt delivery to at least one endpoint in reported_to. A conformant regulator gateway MUST accept signals without prior registration.¶
Signals may trigger enforcement action. Monitors SHOULD include sufficient evidence to permit independent verification without requiring access to the monitor's internal state.¶
None.¶
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017. [RFC8785] Rundgren, A., Jordan, B., and S. Erdtman, "JSON Canonicalization Scheme (JCS)", 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¶