<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.3.8) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>


<rfc ipr="trust200902" docName="draft-dkg-reports-json-00" category="info" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="reports.json">Automated Discovery Of Self-Published Reports (reports.json)</title>

    <author initials="D. K." surname="Gillmor" fullname="Daniel Kahn Gillmor">
      <organization abbrev="ACLU">American Civil Liberties Union</organization>
      <address>
        <email>dkg@fifthhorseman.net</email>
      </address>
    </author>
    <author initials="M. K." surname="Gerchick" fullname="Marissa Kumar Gerchick">
      <organization abbrev="ACLU">American Civil Liberties Union</organization>
      <address>
        <email>mgerchick@aclu.org</email>
      </address>
    </author>

    <date year="2026" month="November" day="20"/>

    <area>int</area>
    <workgroup>intarea</workgroup>
    <keyword>Internet-Draft</keyword>

    <abstract>


<?line 48?>

<t>This document describes a mechanism that
an organization can use to enable automatic discovery
of documents associated with regulatory compliance.
It is motivated by regulations that require, for example,
publicly accessible reports of audits of automated decision-making processes in hiring,
or reports on sustainable business practices.</t>



    </abstract>

    <note title="About This Document" removeInRFC="true">
      <t>
        The latest revision of this draft can be found at <eref target="https://dkg.github.io/reports.json/"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-dkg-reports-json/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/dkg/reports.json/"/>.</t>
    </note>


  </front>

  <middle>


<?line 57?>

<section anchor="introduction"><name>Introduction</name>

<t>An increasing number of regulatory regimes require
organizations involved in certain business practices
to provide a degree of transparency
in their business operations
by posting reports in an accessible location.
For example, New York City's 2021 Local Law 144 (<xref target="NYC-LL144"/>)
established auditing requirements
for employers who use automated decision-making tools
in the employment process,
but it has proved challenging
to even find these audit reports effectively
(see <xref target="Auditing-the-Audits"/>).</t>

<t>For a business that has a website,
the natural place to provide access
to the audit report is on that website.
This document describes a standard mechanism
that can be used to point to any report posted
associated with regulatory compliance.</t>

<t>The mechanism is a <spanx style="verb">reports.json</spanx> summary document,
found at a well-known URL,
which allows the hosting domain
to refer to specific business operations,
relevant regulatory regimes, and
their associated reports.</t>

<t>Adoption of this mechanism should make it easier
for businesses to comply with these requirements,
while also making it easier for
researchers, analysts, and regulators
to assess compliance and
evaluate the overall effectiveness of the regulations.</t>

<section anchor="requirements-language"><name>Requirements Language</name>

<t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>

<?line -18?>

</section>
<section anchor="terminology"><name>Terminology</name>

<t><list style="symbols">
  <t>A "report" is a document
produced by an organization or
an independent entity commissioned by the organization
to describe
-- according to some kind of regulatory compliance --
a part of the organization's business operations.</t>
</list></t>

</section>
<section anchor="goals"><name>Goals</name>

<t><list style="symbols">
  <t>Provide a standardized way for
an organization to publicize reports
associated with given regulatory requirements.</t>
  <t>Provide a standardized way for
a reviewer of reports
associated with a regulatory requirement
to find those reports.</t>
</list></t>

</section>
<section anchor="non-goals"><name>Non-Goals</name>

<t>Discovering a report is
merely the first step in
a process of having an effective
regulatory regime based on these self-hosted reports.
This specification is focused on
satisfying this necessary but
insufficient stage of larger work.</t>

<t><list style="symbols">
  <t>This specification makes no attempt
to describe the syntax or semantics
of any particular report.
The underlying assumption is
that the reports for different regulations or compliance measures
will have different requirements
for content, structure, syntax, and so on.</t>
  <t>This specification also does not associate
a real-world organization with a particular domain name.
If a researcher wants to find the reports
associated with Example Corp,
they need to associate Example Corp with the <spanx style="verb">example.com</spanx> domain name
independently in order to use this specification.
Likewise, any regulation making use of this mechanism
needs to explicitly describe the link between
the regulated entity and the domain name or domain names
on which it is expected to publish this summary.</t>
  <t>This specification does not describe
a way for a casual visitor
to a given website to find these reports.
A regulation that requires
easy public accessibility of a report
may need to offer additional
user interface or user experience guidance
in addition to requiring the use of this mechanism.</t>
</list></t>

</section>
</section>
<section anchor="location"><name>Locating The reports.json Summary</name>

<t>This specification uses
the <spanx style="verb">.well-known</spanx> URL space defined by <xref target="RFC8615"/>.</t>

<t>A given domain hosts the <spanx style="verb">reports.json</spanx> summary
in <spanx style="verb">/.well-known/reports.json</spanx>
within the website operated by the organization.</t>

<t>If Example Corporation operates <spanx style="verb">https://example.com/</spanx>,
then the summary report would be found at
<spanx style="verb">https://example.com/.well-known/reports.json</spanx>.</t>

</section>
<section anchor="reportsjson-structure"><name><spanx style="verb">reports.json</spanx> Structure</name>

<t>The object served from the URL described in <xref target="location"/>
will have <spanx style="verb">Content-Type: application/json</spanx>,
and will consist of a single dictionary object
with at least two top-level keys: <spanx style="verb">operations</spanx> and <spanx style="verb">reports</spanx>.</t>

<t>The overall object relationship looks like this:</t>

<figure title="Data Structure For `reports.json`"><artset><artwork  type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="352" width="304" viewBox="0 0 304 352" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px">
<path d="M 8,32 L 8,128" fill="none" stroke="black"/>
<path d="M 112,32 L 112,128" fill="none" stroke="black"/>
<path d="M 136,64 L 136,80" fill="none" stroke="black"/>
<path d="M 136,128 L 136,160" fill="none" stroke="black"/>
<path d="M 176,48 L 176,80" fill="none" stroke="black"/>
<path d="M 176,160 L 176,256" fill="none" stroke="black"/>
<path d="M 256,160 L 256,256" fill="none" stroke="black"/>
<path d="M 296,48 L 296,80" fill="none" stroke="black"/>
<path d="M 8,32 L 112,32" fill="none" stroke="black"/>
<path d="M 192,32 L 280,32" fill="none" stroke="black"/>
<path d="M 152,48 L 168,48" fill="none" stroke="black"/>
<path d="M 8,64 L 112,64" fill="none" stroke="black"/>
<path d="M 112,96 L 120,96" fill="none" stroke="black"/>
<path d="M 192,96 L 280,96" fill="none" stroke="black"/>
<path d="M 112,112 L 120,112" fill="none" stroke="black"/>
<path d="M 8,128 L 112,128" fill="none" stroke="black"/>
<path d="M 176,160 L 256,160" fill="none" stroke="black"/>
<path d="M 152,176 L 168,176" fill="none" stroke="black"/>
<path d="M 176,192 L 256,192" fill="none" stroke="black"/>
<path d="M 176,256 L 256,256" fill="none" stroke="black"/>
<path d="M 192,32 C 183.16936,32 176,39.16936 176,48" fill="none" stroke="black"/>
<path d="M 280,32 C 288.83064,32 296,39.16936 296,48" fill="none" stroke="black"/>
<path d="M 152,48 C 143.16936,48 136,55.16936 136,64" fill="none" stroke="black"/>
<path d="M 120,96 C 128.83064,96 136,88.83064 136,80" fill="none" stroke="black"/>
<path d="M 192,96 C 183.16936,96 176,88.83064 176,80" fill="none" stroke="black"/>
<path d="M 280,96 C 288.83064,96 296,88.83064 296,80" fill="none" stroke="black"/>
<path d="M 120,112 C 128.83064,112 136,119.16936 136,128" fill="none" stroke="black"/>
<path d="M 152,176 C 143.16936,176 136,168.83064 136,160" fill="none" stroke="black"/>
<polygon class="arrowhead" points="176,176 164,170.4 164,181.6" fill="black" transform="rotate(0,168,176)"/>
<polygon class="arrowhead" points="176,48 164,42.4 164,53.6" fill="black" transform="rotate(0,168,48)"/>
<g class="text">
<text x="60" y="52">operations</text>
<text x="200" y="52">uri</text>
<text x="236" y="68">[not_before]</text>
<text x="36" y="84">urls</text>
<text x="232" y="84">[not_after]</text>
<text x="36" y="100">regs</text>
<text x="48" y="116">reports</text>
<text x="216" y="180">reports</text>
<text x="208" y="212">title</text>
<text x="204" y="228">date</text>
<text x="204" y="244">urls</text>
</g>
</svg>
</artwork><artwork  type="ascii-art"><![CDATA[
+------------+        .------------.
| operations |   .-->| uri          |
+------------+  |    | [not_before] |
| urls       |  |    | [not_after]  |
| regs       +-'      '------------'
| reports    +-.
+------------+  |
                |
                |    +---------+
                 '-->| reports |
                     +---------+
                     | title   |
                     | date    |
                     | urls    |
                     +---------+





]]></artwork></artset></figure>

<section anchor="reports-content"><name><spanx style="verb">reports</spanx> Content</name>

<t>The <spanx style="verb">reports</spanx> member is an object where each named member is
an object with the following members:</t>

<t><list style="symbols">
  <t><spanx style="verb">title</spanx>, simple textual string describing the report, and</t>
  <t><spanx style="verb">date</spanx>, date object describing the calendar date
(year, month, and day) of the report's publication, and</t>
  <t><spanx style="verb">urls</spanx>, an array of URLs that point to
the relevant materials for the report</t>
</list></t>

</section>
<section anchor="operations-content"><name>operations Content</name>

<t>The <spanx style="verb">operations</spanx> member is a list of objects,
each of which describes some set of business operations,
via the following members:</t>

<t><list style="symbols">
  <t><spanx style="verb">urls</spanx>, an array of URLs,
each of which describes a business operation
covered by this object (for example, a job listing),</t>
  <t><spanx style="verb">regs</spanx>, an array of "Regulation" objects, described in <xref target="regulation"/>.</t>
  <t><spanx style="verb">reports</spanx>, an array of keys which can be used to point to
specific reports by name</t>
</list></t>

<section anchor="regulation"><name>Regulation objects</name>

<t>A Regulations object is one element in an array within an <spanx style="verb">operations</spanx> object
that indicates the range of regulations that are
relevant for the regulation and the operation.</t>

<t>The only required member for this object is:</t>

<t><list style="symbols">
  <t><spanx style="verb">uri</spanx>, a URI which refers to a specific piece of regulatory guidance
(i.e., a unique identifier that is associated with the requirements that
the operation needs to comply with).</t>
</list></t>

<t>The other defined (but not required) members are:</t>

<t><list style="symbols">
  <t><spanx style="verb">not_before</spanx>, a time marker indicating the calendar date (year, month, and day)
when the regulation first became relevant for the operation.</t>
  <t><spanx style="verb">not_after</spanx>, a time marker indicating the calendar date (year, month, and day)
at which point the regulation is no longer relevant for the operation.</t>
</list></t>

<t>When both are present, <spanx style="verb">not_after</spanx> <bcp14>MUST</bcp14> be later than <spanx style="verb">not_before</spanx>,
but both values <bcp14>MAY</bcp14> be in the future or the past,
as a way to indicate prospective or retrospective compliance.</t>

</section>
</section>
</section>
<section anchor="iana-considerations"><name>IANA Considerations</name>

<t>IANA should register <spanx style="verb">reports.json</spanx>
in the "Well-Known URIs" registry,
with the following values:</t>

<t><list style="symbols">
  <t>URI suffix: <spanx style="verb">reports.json</spanx></t>
  <t>Change controller: IETF
(is this the right choice,
if this is an informational draft?
is there a better group to control
updates to this specification?)</t>
  <t>Specification document(s): This document</t>
  <t>Status: provisional (unless we see wider adoption,
in which case we should ask for permanent)</t>
  <t>Related information: Any other examples we want to point to?</t>
</list></t>

</section>


  </middle>

  <back>


<references title='References' anchor="sec-combined-references">

    <references title='Normative References' anchor="sec-normative-references">



<reference anchor="RFC2119">
  <front>
    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
    <author fullname="S. Bradner" initials="S." surname="Bradner"/>
    <date month="March" year="1997"/>
    <abstract>
      <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="2119"/>
  <seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="RFC8174">
  <front>
    <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
    <author fullname="B. Leiba" initials="B." surname="Leiba"/>
    <date month="May" year="2017"/>
    <abstract>
      <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="8174"/>
  <seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference>
<reference anchor="RFC8615">
  <front>
    <title>Well-Known Uniform Resource Identifiers (URIs)</title>
    <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
    <date month="May" year="2019"/>
    <abstract>
      <t>This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes.</t>
      <t>In doing so, it obsoletes RFC 5785 and updates the URI schemes defined in RFC 7230 to reserve that space. It also updates RFC 7595 to track URI schemes that support well-known URIs in their registry.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8615"/>
  <seriesInfo name="DOI" value="10.17487/RFC8615"/>
</reference>



    </references>

    <references title='Informative References' anchor="sec-informative-references">

<reference anchor="NYC-LL144" target="https://codelibrary.amlegal.com/codes/newyorkcity/latest/NYCrules/0-0-0-138391">
  <front>
    <title>Rules of the City of New York: Automated Employment Decision Tools</title>
    <author >
      <organization></organization>
    </author>
    <date year="2023" month="April"/>
  </front>
</reference>
<reference anchor="CO-SB26189" target="https://leg.colorado.gov/bills/sb26-189">
  <front>
    <title>Colorado Senate Bill 26-189</title>
    <author >
      <organization></organization>
    </author>
    <date year="2026" month="May"/>
  </front>
</reference>
<reference anchor="CCPA" target="https://cppa.ca.gov/regulations/pdf/ccpa_statute_eff_20260101.pdf">
  <front>
    <title>California Consumer Privacy Act Regulations</title>
    <author >
      <organization></organization>
    </author>
    <date year="2026" month="January"/>
  </front>
</reference>
<reference anchor="JV" target="https://github.com/santhosh-tekuri/jsonschema">
  <front>
    <title>JSONSchema Validation using Go</title>
    <author initials="S. K." surname="Tekuri" fullname="Santhosh Kumar Tekuri">
      <organization></organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>


<reference anchor="Auditing-the-Audits">
  <front>
    <title>Auditing the Audits: Lessons for Algorithmic Accountability from Local Law 144's Bias Audits</title>
    <author fullname="Marissa Kumar Gerchick" initials="M." surname="Gerchick">
      <organization>American Civil Liberties Union, New York, NY, USA</organization>
    </author>
    <author fullname="Ro Encarnación" initials="R." surname="Encarnación">
      <organization>University of Pennsylvania, Philadelphia, PA, USA</organization>
    </author>
    <author fullname="Cole Tanigawa-Lau" initials="C." surname="Tanigawa-Lau">
      <organization>Political Science, Stanford University, Stanford, CA, USA</organization>
    </author>
    <author fullname="Lena Armstrong" initials="L." surname="Armstrong">
      <organization>Harvard University, Cambridge, MA, USA</organization>
    </author>
    <author fullname="Ana Gutiérrez" initials="A." surname="Gutiérrez">
      <organization>American Civil Liberties Union, San Francisco, CA, USA</organization>
    </author>
    <author fullname="Danaé Metaxa" initials="D." surname="Metaxa">
      <organization>University of Pennsylvania, Philadelphia, PA, USA</organization>
    </author>
    <date month="June" year="2025"/>
  </front>
  <seriesInfo name="Proceedings of the 2025 ACM Conference on Fairness, Accountability, and Transparency" value="pp. 29-44"/>
  <seriesInfo name="DOI" value="10.1145/3715275.3732004"/>
<refcontent>ACM</refcontent></reference>

<reference anchor="I-D.ietf-jsonschema-json-schema">
   <front>
      <title>JSON Schema</title>
      <author fullname="Lisa M. Dusseault" initials="L. M." surname="Dusseault">
         <organization>Data Transfer Initiative</organization>
      </author>
      <author fullname="Austin Wright" initials="A." surname="Wright">
         </author>
      <author fullname="Henry H. Andrews" initials="H. H." surname="Andrews">
         </author>
      <date day="13" month="October" year="2026"/>
      <abstract>
	 <t>   JSON Schema defines the media type &quot;application/schema+json&quot;, a JSON-
   based format for describing the structure of JSON data.  A JSON
   Schema may assert constraints on a JSON value, ways to extract
   information from it, and how to interact with it.  The &quot;application/
   schema-instance+json&quot; media type provides additional feature-rich
   integration with &quot;application/schema+json&quot; beyond what can be offered
   for &quot;application/json&quot; documents.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-jsonschema-json-schema-04"/>
   
</reference>



    </references>

</references>


<?line 289?>

<section anchor="test-vectors"><name>Test Vectors</name>

<section anchor="example-reportsjson"><name>Example <spanx style="verb">reports.json</spanx></name>

<figure><sourcecode type="json" name="reports.json"><![CDATA[
{
  "operations": [
    {
      "urls": [
        "https://example.com/jobs/sysadmin",
        "https://example.com/jobs/clerk"
      ],
      "regs": [
        {"uri":
         "https://codelibrary.amlegal.com/codes/newyorkcity/latest/NYCrules/0-0-0-138391"}
      ],
      "reports": [ "fizz", "sparkle" ]
    },
    {
      "urls": [
        "https://example.com/jobs/cfo",
        "https://example.com/jobs/cto"
      ],
      "regs": [
        {"uri":
         "https://codelibrary.amlegal.com/codes/newyorkcity/latest/NYCrules/0-0-0-138391"}
      ],
      "reports": [ "fizz" ]
    }
  ],
  "reports": {
    "fizz": {
      "title": "Fizz Resume Prioritization Service",
      "urls": [
        "https://fizz.example/bias_audits/aedt_audit_2024.pdf",
        "https://fizz.example/bias_audits/aedt_2024_data.tgz"
      ],
      "date": "2024-12-13"
    },
    "sparkle": {
      "title": "Sparkle Video Analytics Assessment",
      "urls": [
        "https://sparkle.example/video_analytics_2023_audit.pdf"
      ],
      "date": "2024-01-15"
    }
  }
}
]]></sourcecode></figure>

</section>
</section>
<section anchor="json-schema-for-reportsjson"><name>JSON Schema For <spanx style="verb">reports.json</spanx></name>

<t>The following JSON Schema
(see <xref target="I-D.ietf-jsonschema-json-schema"/>)
can be used to validate an <spanx style="verb">reports.json</spanx> summary file.</t>

<figure><sourcecode type="json" name="reports-schema.json"><![CDATA[
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "http://ietf.org/json_schemas/reports_schema.json",
  "title": "Report Summary",
  "description": "Automated Discovery of Reports",
  "type": "object",
  "properties": {
    "operations": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "urls": {
            "type": "array",
            "items": {
              "type": "string",
              "format": "uri"
            },
            "uniqueItems": true,
            "minItems": 1
          },
          "regs": {
            "type": "array",
            "items": {
              "type": "object",
              "properties": {
                "uri": {
                  "type": "string",
                  "format": "uri"
                },
                "not_before": {
                  "type": "string",
                  "format": "date"
                },
                "not_after": {
                  "type": "string",
                  "format": "date"
                }
              },
              "required": [
                "uri"
              ]
            },
            "uniqueItems": true,
            "minItems": 1
          },
          "reports": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "property of top-level 'reports' object",
            "uniqueItems": true,
            "minItems": 1
          }
        },
        "required": [
          "urls",
          "regs",
          "reports"
        ]
      }
    },
    "reports": {
      "type": "object",
      "additionalProperties": {
        "type": "object",
        "properties": {
          "date": {
            "type": "string",
            "format": "date"
          },
          "title": {
            "type": "string"
          },
          "urls": {
            "type": "array",
            "items": {
              "type": "string",
              "format": "uri"
            },
            "uniqueItems": true,
            "minItems": 1
          }
        },
        "required": [
          "date",
          "title",
          "urls"
        ]
      }
    }
  },
  "required": [
    "operations",
    "reports"
  ]
}
]]></sourcecode></figure>

<t>For example, you can validate this using with <xref target="JV"/>:</t>

<figure><artwork><![CDATA[
jv reports-schema.json reports.json
]]></artwork></figure>

<t>Note that JSON Schema
cannot represent foreign key constraints,
so the fact that each <spanx style="verb">/operations/*/reports</spanx>
must reference a named member of <spanx style="verb">/reports</spanx>
needs to be enforced separately.</t>

</section>
<section anchor="examples-of-regulatory-regimes"><name>Examples of Regulatory Regimes</name>

<t>Please propose more pointers for this subsection!</t>

<t><list style="symbols">
  <t><xref target="NYC-LL144"/> established requirements for
employers in New York City
to publish reports of audits about
automated decision-making tools used for hiring.</t>
  <t>Colorado's SB 289 <xref target="CO-SB26189"/> requires
deployers of automated decision-making systems
to provide consumers with pre-use notices
about the design and deployment of such systems
on their websites.</t>
  <t>The California Consumer Privacy Act <xref target="CCPA"/>
requires businesses
to create "Risk Assessment Reports"
about their use of
Automated Decision-Making Technology (ADMT)
as well as pre-use notices about ADMT use
and regular cybersecurity audits.</t>
</list></t>

<section anchor="example-regulatory-text"><name>Example Regulatory Text</name>

<t>A regulation or law
that relies on this mechanism
to point toward relevant reports
can cite it using text similar to the following:</t>

<ul empty="true"><li>
  <t>Any Covered Organization that has
a public website shall
publicly point to the Required Reports
associated with each Covered Operation using
a widely understood mechanism such as
the <spanx style="verb">reports.json</spanx> specification.
The Required Reports associated with this act
shall refer to the act as
<spanx style="verb">https://springfield.example/citycouncil/acts/2025/114</spanx></t>
</li></ul>

<t>(note that this text presumes that the regulation
has defined the terms
"Covered Organization",
"Covered Operation", and
"Required Reports")</t>

</section>
</section>
<section anchor="third-party-hosting"><name>Third-party Hosting</name>

<t>Some entities subject to regulatory obligations
might find it challenging to host a reliably up-to-date <spanx style="verb">reports.json</spanx>
on their website.</t>

<t>Such an entity may want to contract with
a regulatory compliance consultancy
in order to keep this record up-to-date without
providing the consultancy write privileges for the entity's entire website,
or even for material in the website's <spanx style="verb">.well-known/</spanx> directory.</t>

<t>Such a consultancy might themselves have multiple clients.
The consultancy could host a repository of their clients' <spanx style="verb">reports.json</spanx> files,
for example in locations like:</t>

<figure><artwork><![CDATA[
https://consultancy.example/clients/example.com/reports.json
https://consultancy.example/clients/entity1.example/reports.json
]]></artwork></figure>

<t>And then ask each client to set up
a one-time HTTP 302 redirect from the appropriate location on their site, like so:</t>

<t>https://example.com/.well-known/reports.json redirects to
   https://consultancy.example/clients/example.com/reports.json</t>

<t>and</t>

<t>https://entity1.example/.well-known/reports.json redirects to
   https://consultancy.example/clients/entity1.example/reports.json</t>

<t>This standard should continue to meet its
goals of responsiveness and discoverability
under such a third-party-hosted arrangement.</t>

</section>
<section numbered="false" anchor="acknowledgements"><name>Acknowledgements</name>

</section>
<section numbered="false" removeInRFC="true" anchor="document-history"><name>Document History</name>

<section numbered="false" removeInRFC="true" anchor="changes-between-auditsjson-01-and-reportsjson-00"><name>Changes between audits.json-01 and reports.json-00</name>

<t><list style="symbols">
  <t>rename from <spanx style="verb">audits.json</spanx> to <spanx style="verb">reports.json</spanx></t>
  <t>add date ranges for <spanx style="verb">operations</spanx></t>
  <t>describe third-party hosting</t>
</list></t>

</section>
<section numbered="false" removeInRFC="true" anchor="changes-between-auditsjson-00-and-auditsjson-01"><name>Changes between audits.json-00 and audits.json-01</name>

<t><list style="symbols">
  <t>added references to CCPA</t>
  <t>align schema test for jv CLI API 0.7</t>
</list></t>

</section>
</section>


  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA91b63LbRpb+j6fooafK8oQXUbZzUU3sUSQnUSLbGknOVCrl
Mptgk+wIBDBoQDKjKM8yz7JPtt853Q00SEjxZLxbtatUErDRl3O/9cFgMIhK
XSZqXxxUZbaSpZqJI23i7EoVa/F6Ls5VMh+cVtNEmyXenak8K0ojdgr7MPzZ
ZOmjSE6nhbraF+FoNMviVK6w9ayQ83Iwu1wM3PsBvR/s7kYxDlxkxXpf6HSe
RdjhcaTzYl+URWXKvd3dL3b3IlkoSRPK6DorLhdFVuX8k8ajS7XG6GxfHKel
KlJVDo7otMhU05U2RmfpxToHDMcvLr6OTCnT2TuZZClG1spEud4XP5VZ3BcG
cBVqbvC0XtHD20hW5TIr9iMxiAT+dGr2xdFQfD8U3+gkWWUFD1sUj2SqVSK+
l8u09TYrFiDtShU6lqk41Fc6ESd6qopSKyPepICP53kCHhyevOEBtZI6Aeku
F3+b63m5BCQGY+kQKHqI7NEvZQFEpfi+WslCfKOKeKnjy49y+mrhdvubjJNq
iO2iK5VWCjRhVu+L3rIsc7M/Gi10uaymwzhbjQDzKBSEUQ/TE3DalMECzBq6
RTrbnE/SUEAa9RWf9erHw8HJyfjJk32GDpxfKOzlt4qzmUr0tJDFeihXiVrI
hAGhcTNK1fUachPrcj2yUIywX1EleLc7oH/Gjz9//MXYbm2VoXdGr0U2F+VS
gXDlmp5fqWvxI7YKleXFKk+y9UqlpThSsSaBExdZlpge7zfDJEzPC1B+b3fv
MQYPXw/Ov9r7dPz5F93YAH5An2SFnGXDRXY1mkKezMhM9z4dYFELzEM3D2qa
4iTxFaYKOy88/6Vc0+mf0umHpwd3UDHP5TCWfGShFhVoBWTMKJ/NR3Gcy3fQ
nrIq1Ts1n7+j3XbHu+Mh3rYhkokG71ItxSFWVxA+cVroKxmvxUFcwoDUO4cQ
fifTCuzzUH73QzeMgZQZmUI9zXJQqsuq0COSHBMvIbkhPN+dv351zqPiB0A2
45NFZXS6EN9kVvi9motGp87d5k6pLviIKBoMBtAVUxYyLqPoYqmNgJGrmPsQ
tbiAbhkhxUrFSxgEs4L4yDKC7kF1MPCLPZ6UsTJKlJkA26aJIhhInnQsZt74
RhA4vzn2NCaLNUvcNWggHINgOgWIkSdaprEaRselAEyrDIrDc6drEbCSocHA
PytdqL4Am4R6L7Fa9aOcTHycrIWMYwW7SVA5pSTRl9VM+ycv+jMn74OVvCR6
5kVGS0EBnYqlLjDWj3BGvU0qDKy61BbnKXEB87EO5NRYOrQUXunZLFFR9IBs
epHNqpigj6KDFBvHMPrMvbRawZARRAEt8KhXAMDhGIVkJ7CusuQKkAO+GEYQ
kHRAEYEtQOVKz8AXILkolGJLUMjU5HA6abyGgSLLoItmfZarwp4Tgep5ZkqC
0uOO+WB6QNski3n2MPo6YENtYtjmPDSkD2Nxgrkw3PJawASKnZub2h7e3j6K
YNCkd8/MJnsuE4CFJ2JGs51ShRHXy4yl725GlmS/HIpuIYu4Y3A/mlaQs1Is
pWFKYQvIe5KodIHlRD8FNyHmOp3RFnwW4KqJAQOiYrLtyTraMaDuzc3zAwf5
AAsG/MN8efT6eDjeHY7HT56OHn82frr32dPh488eIywgxCEtRDrZsIDFm4CS
4lpNjS4h14QCTGNVgIJ5ImPWupq9zA8CmKaFQJIaZand0e01vEfhObCQxazR
/IiXkqZPFZF7xudmCFvoQaZrfxBJippFH6jggEEF5kXT4ZPQeU6gY6sVmVIP
aB/8r8AJgEN0SZLBZZpdp+LN2Uk/uoZ3XwrwLrs2TISlE9wZZEOnRBoEQ9Az
PJgccjKHjeqQ+X5UqERdwWx2qGMf+M4iqy8Bnh5saPYsy9kyssMlC1ZjaJZZ
lYCu8lKRyJHyq4Il2kMBBgA4JtLa0s7KXKgCjCjZ2cRkwkl5vRsZQoBvlESw
Aw0hcGWyNqUFvEGIJUXSiSZgCiMH1JOKPDDRkOw3SNrIuSWWDSYCewzMHzyA
R2zghJKni0oulGU0gltB0a0RvZdvzi96fft/8eo1P5+9+Pub47MXR/R8/u3B
yUn9ELkZ59++fnNy1Dw1Kw9fv3z54tWRXYxR0RqKei8PfuxZ9HuvTy+OX786
OOkJNgmhDsAaEvEh4prC77xQxFhpIq8cbGu/Ojz9r3+Nn0DN/3T29eHeePzF
7a378fn4M+gybJJK7WlZSlzkn6DWOpJ5Dr6w/QRFY5nrEkzEXEOiATEGx0gv
/vITUebtvvjrNM7HT565AUK4Nehp1hpkmm2PbC22ROwY6jimpmZrfIPSbXgP
fmz99nQPBv/6PIHMC8R3z59FLD0XqljpFGHgYg3vKQ5Ez6pVz9oGzylENzm7
UhsUbEYknK1I8q8zlSv8B7zFvxT3QtBdImWXsoAHa7EQEuD5jV8UI8UxpNa6
EmRWK0gy+YK2rw40aED5jBRwrqVXk/AI+MEOk2O155sM4kCYn9Yu2xtj/QsZ
U4S+c49eC2eyxxz0YJ63RTRtwxAvSH/bRq3R1+GHnYw1V1pd+3DlrqPkHcdY
Ejt3mhkVWE5Q4BUct6OCz9yJ8rLxZBGCcPhaputcF6YEoCoHsyPpfToBtpRX
vDBtDFe0ZczFVJIzY99IVtZQfWDJPqwBix2ldxeW2hiYQxbt2shg0MzXLCE0
N1UEBHkthBaIPEw1x0pNYgiaLjj+SigXKMgeXjLZOw4hL4HNYKTLEnFL2ZZN
xt+s01K+hyQITqcR8REnKK6FSyYB1DEQ9kHrEO/IEMN/qiJheMG0apU7nOgA
8vPWsNvohnzTTIOChWq8IcefeBEI/Qrep4LbwR7XlLaB/Kq1MIjgBO8aZzCy
cOigSYGguKIg3uJjbSd8GwWU3bRh1zfLmD5lI3pOPGUyAGHhaFsq4qQyIIsN
CzhLItocz3m1d52QeXJijbDep1gvbMyLNLHI+0xIeLtU2UipntyaVrt3MXER
M6WCkxCqSIRGDEKvSe1nNoLhpGuLNITIib5U19qovgvNPNN8sEArt4ITrCN4
GWH1PidTQie25A32+hL+sbxWKrVI+t2BqDOx0tEqQINkJfjJMgp+cLSmOTrF
gdBRF1fa+pzDzcZ/hFW3JNRCEBht6c0VnmLIJaLlK+QEJdsv4oezgy4WDlkc
2iMBBxQQL8w3CQVI/NoZ3ToX0omrrniDhXkr2UhCRgoh5IzSgwxxGV6DGYUN
OOYU0ANoHiGKFLAZGFpUSPXxwNJQLxYczRI01vCobraSWeWciwPhi0aIOcAW
5y6+vnngc7jbqMviYW/D6cdk2ETdEwq7MZHgnimQ0DpVFwx9On56e0vxsKO2
kwAyrzY67w71KVWbjIJTWuW0SURa47I5zz/rRrs9OgCAXod6lxUuTLCrjJj4
gkyghqMJZ1v2HJ+EOB90zUE8VMKnIlHnDneiwCzZQP7cG0EbK2fTn6EPsOoF
5aPzIlsxIETuVjB6c1Oz7TZqDO/k0BrXgS0XI+xMHCO5sgTcSEt5Psyw0aa0
Mku1iITsNhcpCGULSGRtZykSCD0cxDVyzCwfIEdSCcX1Zl9MmlhmwjbAIzhx
eZ7PIxxq8OF29lLnIsmySwPrcmkt2n4U3ezboteXvSNZyoY8grLkNu16t9Fv
v/0mpDRXi+iTQfD3iXB/w3B0GP0aBF7iV/v+2a+iKrSo/37d2upXHhY/wdi8
mypYF/UWs2hZYvyi9iw5h1a/FTwLhsTP+mTw0D48DE94yJOs1+VJw20IIrHx
1zFiF9ertibQqc+ao7Z3EL+7gz2H+dMJg5tAxdBuIN0ET7kPgIH/wGYOEmvR
Ek7OrYQ1wyvF5TRKGlIvcNeUW8Fow+eQE5o1k6JgknfJ84yqCGQy7TSSyYGY
MM4TBCqazUmp3pfkXRDCcJnBqqa3xxYcWy/AWiIHljJV3HEbC2KZKAq5eQ5o
srNGKNIXKyC5tEHRTK4fNbk3bY90wvogFuf6MCLtpM9luqKQ7JJgPFxVyVdu
ahfuih1UQCs0Yiv2nc0ZTPRAZdpUDxU/IDzU2ZoVi6vpR0x7DFjH31ScOKcy
iid3VmOutLyPKXfg2mcf3X2k7DgI0znf8H6EimaWTTthcRlrf86mjB0gedQn
CEi5NyDoNXcDvZoEm8a7iS7IUw4aCW7vRRbWoXBHDQ6w1wUtr9lAgmNIMO9B
cFPhgYHLD44nN30WRvcWcy4cQmsSDt194Zfhcn4Yv1sS4BwGyxliKpJLZd19
IVOb+2wV8WWhmopbI3o1xD6krM/xLoXKKy4iq/XZrtcBCl5KNJEVonHsaMm1
QGMDwpp6uVax2kjugwBsRw/VkLapUv3PSglNgTkWUkjOKG/fblhkgrIYX6OI
NkZN7B3U/h55PEtKR3yEtUMFa4p4PeaPvDoQIS2yjY9inEvKdRHCXHKoyUzp
tDl3WBxK6nwsFLDFZt9TFVOIv8W/gFkOIHaHHwkeqmQzE50GtCHTnDcnWUo5
9n2QRf8gvKYZRTfwDjllf5STBvAKrrxB5yjLYS6nbfryBQJvQWVTCPvLgx9t
EdEarYrjFnd2jvgJ0ZdxOQr47ZWEihckhVSpEHzRVAYDrbL5A3F88OqAryQh
f/6iJuJBV2Km+oYheNuxkr8H6f2DYtPvXen82PTcgmLdjzp8oEWMRYvUhwsa
7/c398bbwyUrOeX2BVarwvUqkOIYq5bMKr1YliJeZjpWZKa1y1qsw67vyylD
sv0Wz2kSry2oNIUUlHDj7gmrM3weZVP5zBqcrCM3fv6IYDzfyB9tTXHHPNoX
rTsRnku3xIhu+Y7FWIB2qjQhx3FNTgtJCLEAWZkt+vdtkuaNtVE8zfJEmkuW
QYjfSqY4gcE5UzZ9DrDeFwfI263WO7fDx1FBIrT6z+0V41TGlyQUFwrq+AME
hor75LJ91rPJJwTXJquKWFFPwYCcxJe9cIqLqLnv5QYI9RoD39sXP3G0duNi
th5533qUR7qSIbhMMzJrI2crnfb6HzA5hvRc9tzEt35Fj1xt67gbQKB7+00I
2fu4nRQgxjYMTCsCQ/Tm+pdf6NqBblMvE9UTb3nabf8PkymeZx9GoTL7v0If
T5TITQumWArZafsNvTjSxkDva7yAklDzBfVeZIUufUXvHOkxLEhNrHuITNsP
HQVHUy3NO9sEMJJqVtpnagN5Qi0gXcS/fz2tfAfDI4fl4pdtnpBJIlRo2mC8
B8L1QhmpRacL/XP7TvwAM5PBLshkTWVeccA3d2SnPgR9d0KNAZX4s3fS70YI
PLYYMQHux2B3PBg/7dUMvY1uXWbGDSrCdahsJ+o2mGm8SjC7vjk/HhwNtSrn
g6YDxvbX2WdqEdgIga9sJ4ziSLT78niuE3Kb95g9t3239fuzfdkL+r0CkKiR
bMROagTqQCv2Rm4+C/qf9cwvxDpCjRfQBu/sPOOrQ+9CIHhxLQW2U9FX6+xL
m0uw16EpXS2PCGNdj6Pbb53zdjY0tmNwbbntoWuUsWXvG5l0qzn+b6ROl2oV
zus+x73pOK0tvOHYnWfeefLGKpuXbywjY8OelmaQbWy9vd04w8b5x+6ksqjU
xgT4M/92HN2xj7fKHxW5LeK693eS2GNE7qDjxe/TjefcQ7stvN2SJlr+OAez
NfrgkzmM/x89eGNkC5Cez9Raxrl+20HHt/8rMtl2wfWLj6Jz9yKwYbqcxLK9
aurKDx2AD0WnpP9xKtTPAVh3sciapW1d7qRkPebZd9ty89sEv0uXe80N0Wm3
Nv8hE+u8+B3s7lSBe4S/LU3eVd2/+Z3L/79Z/39LxpiyHdTcptBdEha5g7aP
CH35hhxSMO5jt1bf5jqruNBYh1acSts+Y64O3Nx898Pt7b6tyP98JTqiqPbX
E3zGq4y3kmUr8sNBtpjlii+UIiu9SLlfjG6nykJq7noztrNxLuPSbsPV3cmo
wXD0Fx9LTaJVZUpb4uNLVNmu+sPSTJq5dfENcaWiPJw6i4xC0AzskzWXXF74
RJyDqro2eGa7AqPolO7GuIqTU1fLKqN6UsYXu6YpSppqahTfrv2Jkv9W96sI
m19bFUPbedN0veq03VsbifDifLvTWU6zikqOv9Mla2NqgtU2PFPlzjflPzTi
/Cux9/kXgLlp+gfQwY34THkA722tNmtDKuOAdv1GseuvN1bCIAwDus+GaHAb
s7A42M4CZUg+uBqo6n5eHGkqyEOze+bbmt09sRlyC4ESv9fWDwwPTw9uSas8
dkGDpoWbWrchzr0zbS6DZKyOt0OIdeHu5jEYhOmeLC8tWS5UvLS9b2Ln4Ojl
BZc5DTe5Cu5NblHE7U4TaXOaW3d3FiJeUz1YxTBw1JLBUjBs1YQCEb5Q70uq
/wcFVIhAIq8j1/KQ0Ac2WbrZMBJUoq6pXThomrVtMmRDYrqg16WzHnRhRpdn
moB0ncp1Qgh78owrX4fuGuZ1q8PN9UNjjvRtF74BwFDDNl7Uff91bzIdcOZv
CBxvaIeNGj1bkvrYuijPQPOBVOXDvtw6ZaAss7Crl8SOAevqamg35zxjAdyE
qOPOgEqhcYn5jFvTt8y93XFpz5s0+T3p61yrZFbn+FS5ibMqjXUywgpD6enT
0Xj8BIn4TlrbYluUJb6QAa5WyoRdYF4iIupE9zcQ9ApmDUrW62IVddxu0dL2
30a9TdR7j7h0CYMzG1Br1lp8a5u2o+ic7gW5q4jkD5aT73O47aWW3QwMX7gC
+IqrytzJo8uwiZ/WUNsJd+UkGjYWnMwHZTZg77ZRpdg0G9Cbc+Zw6lucqKPH
12K59Czd1XHUanoM2uPYuiWldF9b1D1cl0rllgOFoi7TECzakMy2tZD1/Uiz
k7guNN8b0KdwaqGaa1sLJ0w2PRSq+YCAvDx/zYAHf9sr2t00WBX2+IwmYoYt
qKi8rinRgsKSHTusjEquAAW3oKzwWpOhiRNtm0svNqCPuShe8wVeU1uWzh39
3cqHmypF5RzTj4JLWULBN8LYPhLYEop1mlJnfW6jH3b7Vl21FbR88AZM7XE9
3tokOrCXlymX/9nO2HXcTaxgGHNITZaqAV+KfXtxcSoe7+6BIJbsTfOPzCm2
KLiP0CPb+Djmr22hMZnF/t9pSqrPM/Y2+T+jHLUXtUHYINHHBeNe+ttmNv9J
i7uKIa3VacWtfyul6AMgEy2o79he/Zqc7tbctw4caLiamrQtfhE7Amf5SYG9
9fLdw5SxpAsO37jyaD/wUrMve3Mconq3MHoHMREgUbOFa4ztmAdYVjj3OD37
+vDLHiUgvPTIf7PwrTakNB++9IG7ozO+j9NHB/Yr5rELIxoK0pfNiJsQRdM1
L0vjJFgyIRJuWNABNSnaC9zCnkW6GrYJYErQWNrY/qW3/R8JnV1Gp41hZOHj
GNtlBxz7U8xHrxIKLm0mI+jag4FHknN4ciwOTo/F7vCz6L8Br8DSdWs+AAA=

-->

</rfc>

