<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.39 (Ruby 3.3.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-dogru-scitt-disclosure-evidence-08" category="info" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.34.0 -->
  <front>
    <title abbrev="Disclosure Evidence">Transformation Evidence and Coverage Reconciliation for Auditable Data Disclosure</title>
    <seriesInfo name="Internet-Draft" value="draft-dogru-scitt-disclosure-evidence-08"/>
    <author fullname="Emek Can Doğru" asciiFullname="Emek Can Dogru">
      <organization>VERAX TEKNOLOJİ LİMİTED ŞİRKETİ</organization>
      <address>
        <postal>
          <country>TR</country>
        </postal>
        <email>e.dogru@conarium.dev</email>
      </address>
    </author>
    <date year="2026" month="November" day="19"/>
    <area>Security</area>
    <workgroup>SCITT</workgroup>
    <keyword>receipt</keyword>
    <keyword>masking</keyword>
    <keyword>reconciliation</keyword>
    <keyword>transparency</keyword>
    <keyword>disclosure</keyword>
    <abstract>
      <?line 50?>

<t>Audit receipts record what a gateway wrote about an access. They omit how
data changed and whether every access left a receipt. This document defines
two evidence payloads for those gaps. Transformation Evidence states which
value classes were transformed, and how, without carrying values. Coverage
Reconciliation compares source activity counters with a receipt set over a
window. Each item is matched, observed without a receipt, receipted without
an observation, excluded, or indeterminate. The result is not a bare pass.
Both payloads register as Signed Statements on a SCITT Transparency
Service. This document defines no new receipt format, transparency
mechanism, or signature format.</t>
    </abstract>
  </front>
  <middle>
    <?line 63?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Systems place a policy gateway between an automated client and a data
source. Those systems increasingly emit signed, hash-chained access
receipts. Several receipt formats exist. They share a limit. A receipt is
evidence from the party that performed the access. It is about an event
that party chose to record.</t>
      <t>Two gaps follow from that property.</t>
      <t>First, receipts typically state that access happened. They name the policy
decision. They do not say what happened to the data between the source and
the client. A gateway may mask, redact, or tokenize values before
disclosure. That transformation is the privacy claim. A conventional
receipt does not describe it. An auditor learns that a table was read.
The auditor does not learn whether protected columns left the gateway
transformed or in the clear.</t>
      <t>Second, a receipt set only covers accesses that produced receipts. A
client that reaches the data source without the gateway produces no
receipt. The receipt chain does not reveal this. Hash chains detect
removal and reordering of records that exist. They are silent about
records that were never created. Completeness needs a second account of
activity. That account comes from a party other than the gateway: the
data source.</t>
      <t>This document defines two evidence structures for these gaps.</t>
      <ul spacing="normal">
        <li>
          <t>Transformation Evidence (<xref target="transformation-evidence"/>): a statement bound
to one disclosure. It names which classes of values were transformed,
by which action, and in what count. It never carries the values.</t>
        </li>
        <li>
          <t>Coverage Reconciliation (<xref target="coverage-reconciliation"/>): a procedure and a
signed result. It compares source activity snapshots at the window
bounds with the receipt set for that window. It classifies each Item of
either account. Neither population is assumed complete. The operator
declares the correspondence (<xref target="cr-mapping"/>). The result names what was
matched, observed without a receipt, receipted without an observation,
excluded, or left undecided.</t>
        </li>
      </ul>
      <t>Both structures are payloads. They are meant to be Signed Statements on a
Transparency Service as in <xref target="RFC9943"/>. SCITT supplies append-only,
third-party-auditable registration. This document does not reinvent that.
This document defines no new receipt format, no policy evaluation
semantics, and no transparency mechanism.</t>
      <t>Other individual drafts record signed decisions about automated access.
Farley <xref target="I-D.farley-acta-signed-receipts"/>, Marques
<xref target="I-D.marques-asqav-compliance-receipts"/>, and Chueayen
<xref target="I-D.chueayen-attestation-receipts"/> use Ed25519 <xref target="RFC8032"/> and JSON
Canonicalization <xref target="RFC8785"/>. Aylward <xref target="I-D.aylward-aiga-2"/> uses Ed25519
in a hybrid signature suite and does not specify JCS. None of those drafts
defines Transformation Evidence or Coverage Reconciliation.</t>
      <section anchor="threat-model">
        <name>Threat model and applicability</name>
        <t>The full account is in <xref target="security"/>. This subsection states the bound so a
reader meets it before the procedure.</t>
        <t>The Gateway and the Data Source are often run by one party. That party can
suppress the source counters. A counter reset must fail the Window
(<xref target="cr-procedure"/>). It must not yield a clean report. The Mapping Profile
is written by the Gateway operator. It can absorb unreceipted activity or
exclude it. The defence is visibility: a digest-bound profile, reported
exclusions, and a stated standing for each bound. Digests reject unknown
prefixes. Issuer key compromise is a SCITT-layer problem. A truncated
receipt set still verifies internally; detecting the cut needs a quantity
from outside that file (<xref target="sec-completeness"/>).</t>
      </section>
      <section anchor="what-these-structures-do-not-claim">
        <name>What these structures do not claim</name>
        <t>Both structures state the limits of their own evidence. Transformation
Evidence describes the disclosure surface. It does not claim a value is
unlearnable. It is the Issuer's signed assertion that a transformation
was applied, not proof that it was (<xref target="te-limits"/>). A Coverage
Reconciliation result that reports activity without a receipt is a
statement about absent evidence. It is not, and <bcp14>MUST NOT</bcp14> be presented as,
proof of intent or of a breach (<xref target="cr-semantics"/>).</t>
        <t>Neither structure reports a bare pass. A reconciliation against an
operator-declared correspondence cannot be stronger than that declaration
(<xref target="cr-mapping"/>). An undecided outcome is reported as undecided. It is
not folded into a proportion.</t>
      </section>
      <section anchor="relationship-to-coverage-attestation">
        <name>Relationship to coverage attestation</name>
        <t>A record can be intact and silent about what is missing. A report can be
complete and silent about what it examined. These are two failures. They
close in different places.</t>
        <t>This document is about the first. It states what a mediator recorded. It
states what that record leaves open. A chain that verifies says nothing
about entries that were never written. The vocabulary here lets a record
say so in its own terms.</t>
        <t>The second belongs to coverage attestation. An examination declares the
population it drew from. It names the basis for that population. It
accounts for every unit it did not examine. Work on that layer is under
way on this list.</t>
        <t>The two compose in one direction. They substitute in neither. A coverage
attestation states what was examined. The structures here state what the
mediator recorded of it. An attestation over a mediated examination
inherits whatever the mediator's record leaves open. It inherits that
silently unless the record says so. That silence is the failure this
document names. The other way is no rescue either. A complete access
record over a population chosen after the results were known is an exact
record of a decided question.</t>
        <t>Neither layer rescues the other. One artefact answers half of a two-part
question.</t>
      </section>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</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?>

<t>The following terms are used throughout:</t>
      <dl>
        <dt>Data Source:</dt>
        <dd>
          <t>The system holding the data, with its own accounting of query or access
activity (for example, a database's statement statistics).</t>
        </dd>
        <dt>Gateway:</dt>
        <dd>
          <t>The component that mediates access between an automated client and a
Data Source, applies policy, transforms results, and emits receipts.</t>
        </dd>
        <dt>Disclosure:</dt>
        <dd>
          <t>A single delivery of data (possibly transformed) from the Gateway to a
client.</t>
        </dd>
        <dt>Receipt:</dt>
        <dd>
          <t>A signed record of a Disclosure produced by the Gateway. This document
is agnostic to the receipt format in use.</t>
        </dd>
        <dt>Protected Class:</dt>
        <dd>
          <t>A named category of values that policy subjects to transformation (for
example, "email", "national-id", "phone").</t>
        </dd>
        <dt>Window:</dt>
        <dd>
          <t>A time interval over which reconciliation is performed, bounded by two
snapshots of the Data Source's activity counters. Both bounds are stamped by
the Data Source; whether a Receipt falls inside them is a question about a
second clock, the Gateway's (<xref target="cr-procedure"/>).</t>
        </dd>
        <dt>Mapping Profile:</dt>
        <dd>
          <t>A versioned statement, declared by the operator, of the correspondence
expected between one client-level operation and the source-level activity
it produces — including the bound on that multiplicity, the clock source on
each side and the skew bound between them, and the rules by which activity
is excluded from comparison. A Mapping Profile is a
declaration about a deployment, not a measurement performed by the
Gateway (<xref target="cr-mapping"/>).</t>
        </dd>
        <dt>Item:</dt>
        <dd>
          <t>One unit the reconciliation procedure classifies. On the source side,
one snapshot entry whose pattern counter increased in the Window — one
pattern, not one (pattern, Data Object) pair. On the receipt side, one
Receipt that names a Data Object the snapshots do not account for.
Counting each (pattern, Data Object) pair as an Item changes
<tt>observed-without-receipt</tt>.</t>
        </dd>
        <dt>Data Object:</dt>
        <dd>
          <t>A named target of source activity or of a Receipt. In the shipped
reconciler this is a table (or equivalent schema object), not a column.
The result records these as <tt>objects</tt> on an Item.</t>
        </dd>
        <dt>Consumer:</dt>
        <dd>
          <t>A party that reads Transformation Evidence or a Coverage Reconciliation
result and presents it to a human or to another system. This document
uses Consumer for that role.</t>
        </dd>
        <dt>Reconciler:</dt>
        <dd>
          <t>The party that performs Coverage Reconciliation and produces the result
statement. This document uses Reconciler for that role.</t>
        </dd>
        <dt>Protocol-defined:</dt>
        <dd>
          <t>A standing this document itself assigns to a bound. Example: the
invalid-window rule. It is not a measurement.</t>
        </dd>
        <dt>Measured:</dt>
        <dd>
          <t>A standing a bound has when it was obtained by observation of the
deployment. It is not operator-declared and not assigned by this
document.</t>
        </dd>
        <dt>Client-level operation:</dt>
        <dd>
          <t>One Disclosure, or one client request as seen by the Gateway.</t>
        </dd>
        <dt>Source-level statement:</dt>
        <dd>
          <t>One increment of a Data Source activity counter. That is one snapshot
entry for one pattern. It is not interchangeable with a Client-level
operation.</t>
        </dd>
        <dt>Gateway operator:</dt>
        <dd>
          <t>The party that operates the Gateway.</t>
        </dd>
        <dt>Data Source operator:</dt>
        <dd>
          <t>The party that operates the Data Source. This document does not use
"the operator" without saying which. Where both are the same party,
<xref target="security"/> states the limit.</t>
        </dd>
        <dt>Issuer:</dt>
        <dd>
          <t>In the sense of <xref target="RFC9943"/>: the party that signs a Signed Statement.
For Transformation Evidence that is the Gateway operator. For a
Coverage Reconciliation result that is the Reconciler.</t>
        </dd>
        <dt>Verifier:</dt>
        <dd>
          <t>A party that checks a signature, a digest, or a Transparency Service
receipt. This document uses the term once, for independent checking of
a disclosed result against the Issuer's Transformation Evidence
assertion (<xref target="te-limits"/>).</t>
        </dd>
      </dl>
    </section>
    <section anchor="transformation-evidence">
      <name>Transformation Evidence</name>
      <section anchor="purpose">
        <name>Purpose</name>
        <t>Transformation Evidence answers, for one Disclosure: which Protected
Classes were transformed in the disclosed result, by which action, and in
what count. It exists so that the transformation claim is a first-class,
signed, registrable artifact rather than prose in an operator's
documentation.</t>
      </section>
      <section anchor="te-structure">
        <name>Structure</name>
        <t>Transformation Evidence is a JSON object with the following members:</t>
        <dl>
          <dt><tt>v</tt>:</dt>
          <dd>
            <t>Structure version string. For this document: <tt>transformation-evidence/1</tt>.</t>
          </dd>
          <dt><tt>disclosure</tt>:</dt>
          <dd>
            <t>A digest binding this evidence to exactly one Disclosure, computed over
the receipt for that Disclosure (or, where the receipt format defines a
canonical record hash, that hash). Digest form is defined in
<xref target="digests"/>.</t>
          </dd>
          <dt><tt>request</tt>:</dt>
          <dd>
            <t>A digest of the request that produced the Disclosure. The digest of the
request, never the request text: query text can itself contain protected
values.</t>
          </dd>
          <dt><tt>policy</tt>:</dt>
          <dd>
            <t>An object with <tt>id</tt> (an identifier of the policy version applied) and
<tt>decision</tt> (the policy outcome under which disclosure proceeded).</t>
          </dd>
          <dt><tt>classes</tt>:</dt>
          <dd>
            <t>An array of objects, one per Protected Class that the applied policy
recognizes and that occurred in the disclosed result, each with:
</t>
            <dl>
              <dt><tt>class</tt>:</dt>
              <dd>
                <t>The Protected Class name, as named by the policy.</t>
              </dd>
              <dt><tt>action</tt>:</dt>
              <dd>
                <t>One of <tt>mask</tt>, <tt>redact</tt>, <tt>tokenize</tt>, <tt>truncate</tt>, or <tt>none</tt>. The value
<tt>none</tt> states that the class occurred and was disclosed
untransformed — an honest statement some deployments need to make.</t>
              </dd>
              <dt><tt>count</tt>:</dt>
              <dd>
                <t>The number of values of this class in the disclosed result to which
the action was applied.</t>
              </dd>
            </dl>
          </dd>
        </dl>
        <t>The structure <bcp14>MUST NOT</bcp14> carry data values, transformed or otherwise. Only
class names, action names, counts, digests, and identifiers appear. An
implementation encountering a value in a field defined here <bcp14>MUST</bcp14> reject
the structure.</t>
      </section>
      <section anchor="digests">
        <name>Serialization and digests</name>
        <t>For digesting and signing, the structure is serialized with the JSON
Canonicalization Scheme <xref target="RFC8785"/>. Digests in this document are SHA-256
and are written as strings prefixed with <tt>sha256:</tt> followed by lowercase
hexadecimal. Future documents may register alternative digest prefixes;
an implementation <bcp14>MUST</bcp14> reject a digest whose prefix it does not
recognize rather than guessing.</t>
        <t>A CBOR/COSE serialization <xref target="RFC9052"/> of the same data model is expected
to be specified once the JSON model has received review; nothing in the
model depends on JSON specifically.</t>
      </section>
      <section anchor="te-limits">
        <name>What Transformation Evidence does not prove</name>
        <t>Transformation Evidence describes the disclosure surface of one result.
It does not state that a protected value is unlearnable by the client.
Request languages can permit predicates over protected columns. An allowed
request can then answer questions about a masked value. The value itself
is never disclosed. A result-count of one versus zero is one bit. The
evidence for such a Disclosure is still accurate. The value was
transformed in the result. The client may still have learned something.</t>
        <t>Consumers <bcp14>MUST NOT</bcp14> present Transformation Evidence as proof of
non-exposure. Nor is it proof that the transformation was applied: the
payload is a signed assertion by the Issuer that it was. A Verifier may
check the disclosed bytes against that assertion. Until then, the
evidence is what the pinned Issuer asserted. Where the Issuer is the
Gateway that performed the transformation, the assertion is self-attested.
A Consumer who treats it as verified has dropped the Issuer from the
trust statement. Nothing replaces that Issuer. A deployment that needs a
class to be unlearnable must enforce that in policy. It can refuse the
objects that carry the class. No evidence structure substitutes for that.</t>
        <t>The <tt>classes</tt> array is bounded by what the applied policy recognizes. A
value belonging to a class the policy does not name is not counted. The
absence of a class from the array is therefore a statement about the
policy's vocabulary as much as about the data, and <bcp14>MUST</bcp14> be read that way.</t>
      </section>
    </section>
    <section anchor="coverage-reconciliation">
      <name>Coverage Reconciliation</name>
      <section anchor="purpose-1">
        <name>Purpose</name>
        <t>Coverage Reconciliation answers, for one Window: did the Data Source's
own accounting record activity for which no Receipt exists? It is the
mechanism by which "the gateway was bypassed" or "the receipt sink
failed" becomes detectable, rather than invisible.</t>
        <t>The essential property is that the two accounts being compared originate
from different components: the receipt set from the Gateway, the activity
counters from the Data Source. A Gateway cannot make bypassed activity
disappear from an account it does not produce. Where those components
share one operator, that separation is administrative. The same-operator
limit is in <xref target="security"/>.</t>
      </section>
      <section anchor="cr-snapshots">
        <name>Activity snapshots</name>
        <t>A snapshot is a JSON object capturing the Data Source's cumulative
activity counters at a point in time:</t>
        <dl>
          <dt><tt>v</tt>:</dt>
          <dd>
            <t>Snapshot version string. For this document: <tt>activity-snapshot/1</tt>.</t>
          </dd>
          <dt><tt>ts</tt>:</dt>
          <dd>
            <t>The time the snapshot was taken (ISO 8601).</t>
          </dd>
          <dt><tt>source</tt>:</dt>
          <dd>
            <t>An identifier of the Data Source and the accounting scope within it
(for example, the database role whose activity is counted). Both
snapshots of a Window <bcp14>MUST</bcp14> carry the same <tt>source</tt>; a mismatch
invalidates the Window.</t>
          </dd>
          <dt><tt>entries</tt>:</dt>
          <dd>
            <t>An array of objects, one per activity pattern the source's accounting
distinguishes, each with:
</t>
            <dl>
              <dt><tt>pattern</tt>:</dt>
              <dd>
                <t>A digest of the normalized activity pattern (for example, a
normalized statement with constants removed). The digest, not
necessarily the text: pattern text can embed protected values and
schema detail. Deployments <bcp14>MAY</bcp14> retain pattern text privately for
diagnosis; only the digest is required here.</t>
              </dd>
              <dt><tt>count</tt>:</dt>
              <dd>
                <t>The cumulative counter value for this pattern at <tt>ts</tt>.</t>
              </dd>
            </dl>
          </dd>
        </dl>
      </section>
      <section anchor="cr-procedure">
        <name>Reconciliation procedure</name>
        <t>Given a start snapshot, an end snapshot, and the receipt set for the
Window, a reconciler proceeds as follows.</t>
        <t>Window validity is checked first. The two snapshots <bcp14>MUST</bcp14> carry the same
<tt>v</tt> and <tt>source</tt>, the end <tt>ts</tt> <bcp14>MUST</bcp14> be later than the start <tt>ts</tt>, and no
pattern's counter may be lower at the end than at the start. A counter
regression means the source's accounting was reset or altered inside the
Window; the Window is then unreliable, and the reconciler <bcp14>MUST</bcp14> report
failure for the Window as a whole rather than reconciling the surviving
patterns. An attacker who can reset counters must gain an error, not a
clean report. Why a reset fails the Window, rather than dropping the
reset patterns, is a same-operator concern (<xref target="security"/>).</t>
        <t>Window membership is itself a bound. It is decided across two clocks. The
snapshot timestamps are taken by the Data Source. A Receipt's timestamp is
written by the Gateway. An exact comparison between them fails in one
direction. A Gateway clock that trails the Data Source moves a Receipt
out of the Window. The object that Receipt names then looks like activity
with no Receipt. That outcome is the one whose semantics name gateway
bypass (<xref target="cr-semantics"/>). A clock difference of seconds can produce the
accusation. No real gap is required. The measured case was three seconds
(<xref target="implementation-status"/>). The procedure sets no floor. A smaller
offset is harder for a reader to suspect. The Mapping Profile states the
skew bound (<xref target="cr-mapping"/>).</t>
        <t>A Mapping Profile therefore declares the clock source on each side and the skew
bound between them, as it declares multiplicity (<xref target="cr-mapping"/>), and both are
covered by the profile digest as every other part of it is. Where the bound is
undeclared, the rule below applies and the affected items are <tt>indeterminate</tt>
rather than absent evidence, unless they exceed a declared multiplicity bound
under either reading of the clock. Where it is declared and a Receipt falls further
outside the Window than the bound allows, the boundary does not explain it: the
item takes the outcome it would have had, and a reconciler <bcp14>MUST</bcp14> report which
bound it applied to reach that.</t>
        <t>For each pattern whose counter increased during the Window, the
reconciler attributes the pattern to the data objects it touches and
checks whether any Receipt in the Window names those objects. Matching is
per pattern and per data object, not per call count: one client-level
request may legitimately produce more than one source-level statement, so
call counts and receipt counts <bcp14>MUST NOT</bcp14> be compared at any ratio other than
a multiplicity bound the Mapping Profile declares (<xref target="cr-mapping"/>). A pattern
whose target objects cannot be determined <bcp14>MUST NOT</bcp14> be silently ignored; it
receives the <tt>indeterminate</tt> outcome below.</t>
        <t>The comparison is between two populations — source-level activity and
Receipts — and neither population is assumed complete. Each Item in either
population receives exactly one of the following outcomes. The result
statement names these outcomes as fields (<xref target="cr-result"/>):</t>
        <dl>
          <dt><tt>matched</tt>:</dt>
          <dd>
            <t>The item corresponds to an item in the other population within the
bounds of the applicable Mapping Profile (<xref target="cr-mapping"/>), and within the
Window. The profile's two kinds of bound do not act alike here: a
multiplicity bound admits items to this outcome, and the skew bound does
not. A Receipt outside the Window is never <tt>matched</tt>, however small the
declared skew — the bound qualifies how far the boundary can be trusted, not
where the boundary is.</t>
          </dd>
          <dt><tt>observed-without-receipt</tt>:</dt>
          <dd>
            <t>The Data Source recorded activity against an object that no Receipt in
the Window names, or activity beyond what the declared multiplicity bound
admits for the Receipts that name it.</t>
          </dd>
          <dt><tt>receipted-without-observation</tt>:</dt>
          <dd>
            <t>A Receipt in the Window names an object for which the Data Source's
counters record no activity.</t>
          </dd>
          <dt><tt>excluded</tt>:</dt>
          <dd>
            <t>The item was removed from comparison before matching by a rule stated in
the Mapping Profile (<xref target="cr-exclusions"/>).</t>
          </dd>
          <dt><tt>indeterminate</tt>:</dt>
          <dd>
            <t>The evidence or the Mapping Profile does not determine an outcome — the
pattern's objects could not be attributed, a required multiplicity or skew
bound is undeclared, the item's only naming Receipt falls outside the Window
by no more than a declared skew bound, or with no skew bound declared, and
the item does not exceed a declared multiplicity bound with that Receipt
admitted, or the Window's evidence is insufficient to decide.</t>
          </dd>
        </dl>
        <t>An implementation <bcp14>MUST NOT</bcp14> report an item as <tt>matched</tt> when the outcome is
<tt>indeterminate</tt>; the absence of a decision is not a decision. In
particular, where a Mapping Profile does not declare the multiplicity bound
that the comparison requires, the affected items are <tt>indeterminate</tt> and
not clean coverage.</t>
        <t>The same rule binds the temporal bound, in the opposite direction. Where every
object an item leaves unaccounted for is named by a Receipt that falls outside
the Window, the item is <tt>indeterminate</tt>, and an implementation <bcp14>MUST NOT</bcp14> report
it as <tt>observed-without-receipt</tt>. A reconciler cannot distinguish a Gateway
clock that trails the Data Source from a Receipt written late, and reporting
absent evidence asserts a distinction it did not make. An item that leaves even
one object named by no Receipt at all is not affected by this rule: that is a
genuine absence, and a neighbouring object's clock does not make it
undecidable.</t>
        <t>The rule above applies only where the clock decides the outcome. Where a
Mapping Profile declares a multiplicity bound and an item's statement count
exceeds what that bound admits even with every Receipt naming its objects
counted, both readings of the clock give <tt>observed-without-receipt</tt>: with the
Receipts admitted, they do not cover the count; without them, no Receipt in
the Window names the object. Such an item is <tt>observed-without-receipt</tt>, and
the prohibition above does not apply. The result statement <bcp14>MUST</bcp14> carry the
offset and the bound. An implementation <bcp14>MUST NOT</bcp14> apply this exception where
the multiplicity bound is undeclared.</t>
        <t><tt>indeterminate</tt> here is not a weaker pass. The comparison did not come out
clean, and a result statement <bcp14>MUST</bcp14> carry the outcome and the offset that
produced it. What the implementation is forbidden to do is state the cause.</t>
        <t>A reconciliation with no <tt>observed-without-receipt</tt> items establishes that
each observed source-level item is attributable to a Receipt naming the
same object, under the declared correspondence. It does not establish that
every source-level statement was itself receipted, and a result <bcp14>MUST NOT</bcp14> be
stated in terms that assert it. Where one Receipt naming an object clears
an unbounded number of further statements against that object inside the
Window, the procedure has established object attribution and nothing
stronger.</t>
      </section>
      <section anchor="cr-mapping">
        <name>Mapping profiles</name>
        <t>One Client-level operation may produce several Source-level statements. The
multiplicity is not a property of the Gateway. It is a property of the
deployment. A pooler or an object-relational mapper can produce it. A
Gateway cannot measure a correspondence it does not produce.</t>
        <t>A Mapping Profile is therefore declared by the operator. For each
Client-level operation it covers, it states the expected source-level
patterns. It states the multiplicity bound. It states the exclusion rules
(<xref target="cr-exclusions"/>). It carries a version identifier. It is serialized
and digested as in <xref target="digests"/>.</t>
        <t>The multiplicity bound states how many source-level statements one Receipt
may cover, however many objects the Receipt names. A statement is covered by
one Receipt in the Window that names all of its pattern's objects, or by one
Receipt in the Window for each of those objects. Only a pattern whose objects
all have a Receipt in the Window draws on the Receipts; a pattern with an
object that no Receipt in the Window names takes its outcome from that object.
Of the patterns that draw, one whose statement count exceeds, for one of its
objects, the bound times the Receipts in the Window that name that object is
<tt>observed-without-receipt</tt>; its statements still draw on the Receipts, because
they were observed. Any other pattern that draws is <tt>matched</tt> only if every
assignment of statements to Receipts within the bound that covers as many
statements as possible covers all of its statements; otherwise it is
<tt>indeterminate</tt>, because the evidence does not say which statements the
Receipts covered. An implementation that cannot establish this reports
<tt>indeterminate</tt>, not <tt>matched</tt>.</t>
        <t>The profile also declares the temporal correspondence. The operator knows
it. The Gateway cannot measure it. It names the clock on each side. The
Data Source stamps snapshots. The Gateway stamps Receipts. It states the
skew bound between them. Both are operator statements. A claim that both
sides read one clock, so the bound is zero, is still a declaration. One
clock read twice is not read at the same instant. Whether the residue
matters is a judgement about the deployment. The rule below forbids
presenting that as measured. This document also refuses a third case:
zero because nobody looked, declared by nobody, and read as agreement.</t>
        <t>The temporal correspondence is declared in three fields under a <tt>clocks</tt>
member. The encoding is given so another specification can adopt the same
shape:</t>
        <dl>
          <dt><tt>clocks.observation</tt>:</dt>
          <dd>
            <t>String. An identifier for the clock that stamps the activity snapshots — the
Data Source side.</t>
          </dd>
          <dt><tt>clocks.receipt</tt>:</dt>
          <dd>
            <t>String. An identifier for the clock that stamps Receipts — the Gateway side.</t>
          </dd>
          <dt><tt>clocks.skew</tt>:</dt>
          <dd>
            <t>Duration. The bound on how far those two clocks may differ. A duration is a
decimal integer with a unit suffix of <tt>ms</tt>, <tt>s</tt>, <tt>m</tt>, or <tt>h</tt>, or a bare
decimal integer read as milliseconds: <tt>500ms</tt>, <tt>5s</tt>, <tt>2m</tt>, <tt>1h</tt>, <tt>5000</tt>. A
duration that does not parse is an error, not a default.</t>
          </dd>
        </dl>
        <t>An implementation <bcp14>MUST</bcp14> reject a <tt>clocks</tt> member carrying any key other than
these three, and <bcp14>SHOULD</bcp14> name the key it rejected. A silently ignored fourth
field declares less than its author believes. The gap shows up as an
outcome the operator cannot account for.</t>
        <t>A declaration that both sides read one clock writes all three fields: the two
identifiers may be the same string, and <tt>skew</tt> may be <tt>0ms</tt>. A declared zero is
a statement someone is accountable for; an assumed zero is the condition the
rule below forbids.</t>
        <t>Where the skew bound is declared twice — in the profile and through an
interface of the reconciler's own — an implementation <bcp14>MUST NOT</bcp14> select between
them. Two declarations that parse to the same number of milliseconds are one
declaration and proceed. Two that do not are an operator error and <bcp14>MUST</bcp14> fail,
because which declaration prevailed would not be visible on the result, and a
bound whose origin cannot be read from the result is not usefully declared at
all.</t>
        <t>A reconciliation result computed against a Mapping Profile <bcp14>MUST</bcp14> bind that
profile's digest, and <bcp14>MUST</bcp14> state, for each bound it relies on, whether the
bound is protocol-defined, measured, operator-declared, or undeclared. A
result <bcp14>MUST NOT</bcp14> present an operator-declared bound as a measured one.</t>
        <t>The consequence is a ceiling. A coverage outcome against a declared
correspondence cannot be stronger than the declaration. Where the
declaration is an operator statement, the outcome inherits that standing.
The result statement must show it. The same discipline applies to absent
evidence in <xref target="cr-semantics"/>. A declaration presented as a measurement is
an overclaim. Truth of the declaration does not change that.</t>
        <t>Where a required multiplicity bound is undeclared, the affected items are
<tt>indeterminate</tt> (<xref target="cr-procedure"/>). An implementation <bcp14>MUST NOT</bcp14> substitute a
default bound of one; a one-to-one rule reports false
<tt>observed-without-receipt</tt> items on any deployment with a pooler in front of
the Data Source, and a silent default would make that error look like a
finding.</t>
        <t>An undeclared skew bound is treated the same way, and for the same reason. An
implementation <bcp14>MUST NOT</bcp14> substitute a default of zero: zero asserts that the two
clocks agree, which is the assumption that produces the false accusation this
document now guards against. It <bcp14>MUST NOT</bcp14> substitute a bound of its own choosing
either, which would decide the operator's question with a number the operator
never saw. Absent the declaration, items whose only naming Receipt sits outside the
Window are <tt>indeterminate</tt> and the result reports the offset, unless they exceed
a declared multiplicity bound under either reading of the clock. The reader
compares that offset with clocks the reader knows. The Reconciler does
not.</t>
        <t>An implementation <bcp14>MAY</bcp14>, absent a declared bound, decline to offer the boundary
as the explanation for an offset larger than the Window itself, on the ground
that a boundary artefact cannot exceed the interval it bounds. This is a
reporting choice about what an implementation is willing to suggest, not a
change of outcome: the item has the same outcome either way. The
twenty-three hour case that motivated this choice is in
<xref target="implementation-status"/>.</t>
      </section>
      <section anchor="cr-exclusions">
        <name>Exclusions</name>
        <t>Exclusion differs from the other outcomes in kind. <tt>matched</tt>,
<tt>observed-without-receipt</tt>, <tt>receipted-without-observation</tt>, and
<tt>indeterminate</tt> are produced by the comparison. <tt>excluded</tt> is a decision
taken before it. It decides what will be compared at all. A reconciliation
can be made to come out clean through this outcome. It therefore needs
the tightest reporting rules of the five.</t>
        <t>Exclusion rules <bcp14>MUST</bcp14> be stated in the Mapping Profile and are therefore
covered by its digest. A result statement <bcp14>MUST</bcp14> report the count of excluded
items and the rule that excluded each of them. An implementation <bcp14>MUST NOT</bcp14>
exclude items by a rule that is not in the profile.</t>
        <t>Without these constraints a clean result and a result cleaned by
exclusion look the same. The digest that pins what was compared then
misses the step that decided what was compared. Session or catalog
housekeeping is a legitimate exclusion. Exclusions need not be rare.
They must be visible and pinned.</t>
        <t>Pinning is easy to read as more than it is. The rule identifier makes the
exclusion reproducible. A reader sees which rule removed each Item. The
reader can check that the rule was in the profile the digest covers. That
does not establish that the exclusion was correct. A housekeeping rule
and a rule that hides the auditor's target pin the same way. They verify
the same way. The mechanism reproduces the decision. It does not judge
it.
Consumers <bcp14>MUST NOT</bcp14> read a pinned exclusion as a justified one, and a result
statement <bcp14>MUST NOT</bcp14> present the digest as evidence that the exclusions were
appropriate. The same distinction holds between a declared bound and a
measured one (<xref target="cr-mapping"/>). Here it applies to what is compared at
all.</t>
      </section>
      <section anchor="cr-result">
        <name>Result statement</name>
        <t>The reconciliation result is a JSON object:</t>
        <dl>
          <dt><tt>v</tt>:</dt>
          <dd>
            <t><tt>coverage-reconciliation/2</tt>. The outcome vocabulary of
<tt>coverage-reconciliation/1</tt> is not a subset of this one: a <tt>/1</tt> result
reporting <tt>covered</tt> asserts more than the procedure establishes, and is
not re-expressible here. A consumer <bcp14>MUST NOT</bcp14> read a <tt>/1</tt> result as a <tt>/2</tt>
result.</t>
          </dd>
          <dt><tt>window</tt>:</dt>
          <dd>
            <t>Object with <tt>start</tt> and <tt>end</tt> (the two snapshot <tt>ts</tt> values).</t>
          </dd>
          <dt><tt>source</tt>:</dt>
          <dd>
            <t>The common <tt>source</tt> identifier of the two snapshots.</t>
          </dd>
          <dt><tt>snapshots</tt>:</dt>
          <dd>
            <t>Object with <tt>start</tt> and <tt>end</tt> digests of the two snapshot structures.</t>
          </dd>
          <dt><tt>receipts</tt>:</dt>
          <dd>
            <t>A digest identifying the receipt set that was compared (for chained
receipt formats, the chain head digest and the sequence range are
<bcp14>RECOMMENDED</bcp14> as the identifying material).</t>
          </dd>
          <dt/>
          <dd>
            <t>A result <bcp14>SHOULD</bcp14> state whether that identifying material was obtained
independently of the Issuer or read from the receipt set itself. The two
are not equivalent evidence, and a Consumer cannot tell them apart from
the digest (<xref target="sec-completeness"/>).</t>
          </dd>
          <dt><tt>profile</tt>:</dt>
          <dd>
            <t>The digest and version identifier of the Mapping Profile the comparison
was computed against (<xref target="cr-mapping"/>), or <tt>null</tt> when none was declared.
When <tt>null</tt>, every item whose outcome depends on a multiplicity bound is
<tt>indeterminate</tt>, and so is every item whose only naming Receipt falls
outside the Window: with no profile there is no declared skew bound either.</t>
          </dd>
          <dt><tt>bounds</tt>:</dt>
          <dd>
            <t>For each bound the comparison relied on, its source: <tt>protocol-defined</tt>,
<tt>measured</tt>, <tt>operator-declared</tt>, or <tt>undeclared</tt>. A result whose bounds
are <tt>operator-declared</tt> states an outcome of that standing, no stronger.</t>
          </dd>
          <dt><tt>outcome</tt>:</dt>
          <dd>
            <t><tt>invalid-window</tt> when the Window is unreliable (<xref target="cr-procedure"/>);
otherwise <tt>no-exceptions</tt> when every item is <tt>matched</tt> or <tt>excluded</tt>, and
<tt>exceptions</tt> when any item is <tt>observed-without-receipt</tt>,
<tt>receipted-without-observation</tt>, or <tt>indeterminate</tt>.</t>
          </dd>
          <dt/>
          <dd>
            <t>The name states what the comparison left open, not what it proved. A
result <bcp14>MUST NOT</bcp14> carry an outcome name that asserts coverage of the source
activity, and <tt>no-exceptions</tt> is not such an assertion: it says the
comparison produced no open item under the declared correspondence, which
is bounded by that correspondence (<xref target="cr-mapping"/>) and by the fact that
neither population is assumed complete.</t>
          </dd>
          <dt><tt>items</tt>:</dt>
          <dd>
            <t>The list of items whose outcome is not <tt>matched</tt>, each with its outcome
and, for <tt>excluded</tt>, the profile rule that excluded it. Pattern digests,
not pattern text, for the reasons in <xref target="cr-snapshots"/>.</t>
          </dd>
          <dt><tt>counts</tt>:</dt>
          <dd>
            <t>The number of items in each outcome, including <tt>matched</tt> and <tt>excluded</tt>.
An implementation <bcp14>MUST NOT</bcp14> aggregate <tt>indeterminate</tt> items into a
proportion of coverage: an outcome that does not decide cannot be
averaged into one that does, and reporting it as a percentage restores
precisely the overclaim this vocabulary exists to prevent.</t>
          </dd>
          <dt/>
          <dd>
            <t>A result carries <tt>matched</tt> as a count while carrying every other outcome as
an accounting, and the asymmetry is deliberate. A count a reader cannot
reconstruct is an assertion about a population the producer alone can see.
This one is not that: the result digests both activity snapshots and the
receipt set it compared (<xref target="cr-snapshots"/>, <xref target="digests"/>), and a reader holding
those inputs recomputes the matched set. The size is not an assertion.
The count is a convenience over material the reader already has.</t>
          </dd>
          <dt/>
          <dd>
            <t>That property fails in one named case. The identifying material for the
receipt set may be read from the receipt set itself
(<xref target="sec-completeness"/>). A reader then recomputes the Issuer's answer.
The digest checks transcription, not completeness. The <tt>matched</tt> count
inherits that standing.</t>
          </dd>
        </dl>
        <t>The result statement is serialized and digested as in <xref target="digests"/> and is
intended to be signed by the reconciling party and registered
(<xref target="scitt"/>). The reconciler <bcp14>SHOULD</bcp14> be operationally independent of the
Gateway; where it is not, registration on a Transparency Service at
least makes the result's existence and timing third-party-visible.</t>
      </section>
      <section anchor="cr-semantics">
        <name>Semantics of the outcomes</name>
        <t>An <tt>observed-without-receipt</tt> outcome states that evidence is absent. It
does not state why. Gateway bypass produces it. Receipt sink failure
produces it. Accounting scope mismatch produces it. A Receipt that names
the object but falls outside the Window on the two clocks also produced
it. <xref target="cr-procedure"/> therefore removes that case from this outcome, except
where the Receipt falls further outside the Window than a declared skew bound
allows, or the item exceeds a declared multiplicity bound under either reading
of the clock. An
earlier revision listed the mirror condition under
<tt>receipted-without-observation</tt> only. This text names both directions so
the omission is visible. A result statement <bcp14>MUST NOT</bcp14>
label such activity as an intrusion, a breach, or an intentional act, and
consumers <bcp14>MUST NOT</bcp14> present it as such. The mechanism surfaces the
condition. Cause is investigation, not reconciliation.</t>
        <t>A <tt>receipted-without-observation</tt> outcome is likewise a statement about
evidence. It is not by itself a fault. A counter reset at the Window
boundary produces the same shape. So does an intermediary that collapses
statements. So does an increment outside the snapshot pair. A receipt
that describes activity that did not occur produces it too. An implementation <bcp14>MAY</bcp14> treat it as a
failure condition under a policy of its own; this document does not define
it as one, because the shape does not distinguish the cases.</t>
        <t>An <tt>indeterminate</tt> outcome is a result, not a degraded pass. It <bcp14>MUST NOT</bcp14> be
resolved by assumption in either direction: neither counted as matched
because nothing contradicts it, nor reported as missing activity because
nothing confirms it. An implementation under pressure to produce a single
number will be tempted to fold <tt>indeterminate</tt> into a coverage proportion;
that operation destroys the only property that distinguishes this
vocabulary from a bare pass, and <bcp14>MUST NOT</bcp14> be performed.</t>
        <t>Verification of receipt signatures and chain integrity is out of scope
for reconciliation and is assumed to have happened first, under the rules
of the receipt format in use. Reconciliation compares an
already-verified receipt set against source accounting; it does not
re-verify.</t>
      </section>
    </section>
    <section anchor="scitt">
      <name>Registration on a Transparency Service</name>
      <t>Both structures defined here are payloads for Signed Statements in the
sense of <xref target="RFC9943"/>. The Issuer signs the serialized structure. For
Transformation Evidence that Issuer is the Gateway operator. For a
Coverage Reconciliation result that Issuer is the Reconciler. The Issuer
registers the Signed Statement on a Transparency Service. The SCITT
Receipt is proof of inclusion, at a position, in an append-only log. That
log is operated by a party other than the Issuer.</t>
      <t>This layering is deliberate. The structures gain their audit value from
registration the Issuer cannot quietly rewrite. SCITT already defines
that place, its trust model, and its verification. This document defines
no countersignature, no anchoring, and no log format of its own. Digests
in this document bind evidence to receipts over the payload. The binding
survives registration. It is not over the envelope.</t>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <dl>
        <dt>Same-operator collusion.</dt>
        <dd>
          <t>In many deployments the Gateway and the Data Source are operated by the
same party. Value against that party is reduced. An operator with
administrative access to the source accounting can suppress the
counters. The invalid-window rule (<xref target="cr-procedure"/>) turns a reset
into a visible failure. Registration (<xref target="scitt"/>) makes suppression of
already-issued results detectable. An operator who controls both
accounts and never registers is outside this mechanism. Assurance
against that operator needs an accounting path the operator cannot
write to. That is a deployment property, not a payload property.</t>
        </dd>
        <dt>Counter manipulation.</dt>
        <dd>
          <t>An attacker who can reset or rewind source counters could otherwise
hide activity between snapshots. The <bcp14>MUST</bcp14>-fail rule exists for this
case: a Window containing a regression is reported unreliable in its
entirety. Snapshot frequency bounds the exposure — shorter Windows
mean a reset costs the attacker a visible failure sooner.</t>
        </dd>
        <dt>Declared correspondence as an attack surface.</dt>
        <dd>
          <t>The Mapping Profile (<xref target="cr-mapping"/>) is written by the operator. It
decides what counts as a match. It decides what is excluded before
matching. A wider multiplicity bound can absorb unreceipted activity.
An added exclusion rule can remove it from comparison. This mechanism
does not defend against that operator. Nothing computed against a
declaration can. It makes the declaration part of the evidence. The
profile is versioned. Its digest is bound into the result. Exclusions
are reported with count and rule. The result states that its bounds are
operator-declared. A reader who trusts the result sees that dependency.
Registration (<xref target="scitt"/>) makes the sequence of declared profiles
third-party-visible. A silently edited profile would lose that.</t>
        </dd>
        <dt>Digest agility.</dt>
        <dd>
          <t>Digests are prefixed (<xref target="digests"/>); an implementation <bcp14>MUST</bcp14> reject
unknown prefixes. Accepting an unknown prefix as an opaque match would
let an attacker route around comparison.</t>
        </dd>
        <dt>Signature and key compromise.</dt>
        <dd>
          <t>Signing and registration are inherited from the SCITT layer; key
management, revocation, and the consequences of Issuer key compromise
are governed there, not here. A compromised Issuer key voids the
evidentiary value of statements under that key, as it does for any
signed artifact.</t>
        </dd>
      </dl>
      <section anchor="sec-completeness">
        <name>Receipt set completeness and where the expected count comes from</name>
        <t>A receipt set whose most recent entries have been removed is internally
consistent. Every remaining link verifies. Every signature checks. The
file does not state how many entries it should have contained.
Reconciliation does not close this. It compares the receipt set against
source accounting. An operator who can truncate one can generally
suppress the other. Detecting the removal needs a count, a head digest,
or an equivalent quantity. That quantity must not come from the
truncated file.</t>
        <t>What matters to a Consumer is where that material arrives from. The two
constructions differ in a way a digest does not reveal.</t>
        <t>An implementation may accept the expected quantity as a verifier input.
The check is then only as trustworthy as that input. An auditor who holds
only the receipt file has no source for it except the Issuer. That is
the party under examination. The verification is real. Its independence
is supplied by whoever ran it. It is not a property of the artifacts.</t>
        <t>An implementation may instead carry the quantity inside the signed
material. The set then testifies to its own extent. That closes the first
gap. The cost should be stated. The Issuer is signing an assertion about
a population it has not finished producing. A per-entry counter
constrains only the entries that were kept. A sealed total is also
required. A running count derived from the sequence number it accompanies
adds no information. It restates the position of a present record. It
says nothing about an absent one. The useful property is a sealed
quantity over a held set. It is not a per-record decoration.</t>
        <t>This document requires neither construction. It requires that a result
identifying a receipt set be readable as to which one it used. A Consumer
who cannot tell them apart will read an external pin as if the receipt
set had proved its own completeness. That is the strongest claim in this
area. It is the one least often actually made.</t>
      </section>
    </section>
    <section anchor="privacy-considerations">
      <name>Privacy Considerations</name>
      <t>Every structure in this document follows one rule. Evidence about
protected data must not itself become a disclosure channel.
Transformation Evidence carries class names, action names, and counts.
It never carries values. Request and pattern references are digests.
Query and pattern text can embed values and schema detail. Class names
and counts do reveal that a class was present, and in what quantity.
Deployments that treat even that as sensitive can keep the payloads
private. They can register only the digests. Third-party audit then
becomes a permissioned act.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document requests registration of two media types and the creation
of two registries. Registrations follow <xref target="RFC6838"/>. Registry policy is
Specification Required as defined in <xref target="RFC8126"/>.</t>
      <section anchor="media-type-applicationtransformation-evidencejson">
        <name>Media type: application/transformation-evidence+json</name>
        <dl>
          <dt>Type name:</dt>
          <dd>
            <t>application</t>
          </dd>
          <dt>Subtype name:</dt>
          <dd>
            <t>transformation-evidence+json</t>
          </dd>
          <dt>Required parameters:</dt>
          <dd>
            <t>None.</t>
          </dd>
          <dt>Optional parameters:</dt>
          <dd>
            <t>None.</t>
          </dd>
          <dt>Encoding considerations:</dt>
          <dd>
            <t>8bit; binary UTF-8 JSON. For digesting and signing, the payload is
serialized with <xref target="RFC8785"/>.</t>
          </dd>
          <dt>Security considerations:</dt>
          <dd>
            <t>See <xref target="security"/> and <xref target="te-limits"/>. The payload <bcp14>MUST NOT</bcp14> carry data
values.</t>
          </dd>
          <dt>Interoperability considerations:</dt>
          <dd>
            <t>Implementations that do not recognize the <tt>v</tt> member <bcp14>MUST</bcp14> reject the
object.</t>
          </dd>
          <dt>Published specification:</dt>
          <dd>
            <t>This document, <xref target="te-structure"/>.</t>
          </dd>
          <dt>Applications that use this media type:</dt>
          <dd>
            <t>Policy gateways and auditors that record or verify a disclosure
transformation.</t>
          </dd>
          <dt>Fragment identifier considerations:</dt>
          <dd>
            <t>None.</t>
          </dd>
          <dt>Additional information:</dt>
          <dd>
            <t>Deprecated alias names for this type: none. Magic number(s): none.
File extension(s): none. Macintosh file type code(s): none.</t>
          </dd>
          <dt>Person and email address to contact for further information:</dt>
          <dd>
            <t>See the Authors' Addresses section of this document.</t>
          </dd>
          <dt>Intended usage:</dt>
          <dd>
            <t>COMMON</t>
          </dd>
          <dt>Restrictions on usage:</dt>
          <dd>
            <t>None.</t>
          </dd>
          <dt>Author:</dt>
          <dd>
            <t>See the Authors' Addresses section of this document.</t>
          </dd>
          <dt>Change controller:</dt>
          <dd>
            <t>IETF</t>
          </dd>
        </dl>
      </section>
      <section anchor="media-type-applicationcoverage-reconciliationjson">
        <name>Media type: application/coverage-reconciliation+json</name>
        <dl>
          <dt>Type name:</dt>
          <dd>
            <t>application</t>
          </dd>
          <dt>Subtype name:</dt>
          <dd>
            <t>coverage-reconciliation+json</t>
          </dd>
          <dt>Required parameters:</dt>
          <dd>
            <t>None.</t>
          </dd>
          <dt>Optional parameters:</dt>
          <dd>
            <t>None.</t>
          </dd>
          <dt>Encoding considerations:</dt>
          <dd>
            <t>8bit; binary UTF-8 JSON. For digesting and signing, the payload is
serialized with <xref target="RFC8785"/>.</t>
          </dd>
          <dt>Security considerations:</dt>
          <dd>
            <t>See <xref target="security"/> and <xref target="cr-semantics"/>.</t>
          </dd>
          <dt>Interoperability considerations:</dt>
          <dd>
            <t>A consumer <bcp14>MUST NOT</bcp14> read a <tt>coverage-reconciliation/1</tt> result as a
<tt>/2</tt> result (<xref target="cr-result"/>).</t>
          </dd>
          <dt>Published specification:</dt>
          <dd>
            <t>This document, <xref target="cr-result"/>.</t>
          </dd>
          <dt>Applications that use this media type:</dt>
          <dd>
            <t>Reconcilers and auditors that compare source activity with a receipt
set.</t>
          </dd>
          <dt>Fragment identifier considerations:</dt>
          <dd>
            <t>None.</t>
          </dd>
          <dt>Additional information:</dt>
          <dd>
            <t>Deprecated alias names for this type: none. Magic number(s): none.
File extension(s): none. Macintosh file type code(s): none.</t>
          </dd>
          <dt>Person and email address to contact for further information:</dt>
          <dd>
            <t>See the Authors' Addresses section of this document.</t>
          </dd>
          <dt>Intended usage:</dt>
          <dd>
            <t>COMMON</t>
          </dd>
          <dt>Restrictions on usage:</dt>
          <dd>
            <t>None.</t>
          </dd>
          <dt>Author:</dt>
          <dd>
            <t>See the Authors' Addresses section of this document.</t>
          </dd>
          <dt>Change controller:</dt>
          <dd>
            <t>IETF</t>
          </dd>
        </dl>
      </section>
      <section anchor="transformation-actions-registry">
        <name>Transformation Actions registry</name>
        <t>IANA is asked to create a new registry titled "Transformation Actions"
in a new "Disclosure Evidence" group.</t>
        <dl>
          <dt>Registration policy:</dt>
          <dd>
            <t>Specification Required (<xref target="RFC8126"/>).</t>
          </dd>
          <dt>Registration template:</dt>
          <dd>
            <t>Action name (unique ASCII token); description; reference.</t>
          </dd>
        </dl>
        <t>Initial contents:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Action name</th>
              <th align="left">Description</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">mask</td>
              <td align="left">Replace a value with a class-level placeholder</td>
              <td align="left">This document, <xref target="te-structure"/></td>
            </tr>
            <tr>
              <td align="left">redact</td>
              <td align="left">Remove a value</td>
              <td align="left">This document, <xref target="te-structure"/></td>
            </tr>
            <tr>
              <td align="left">tokenize</td>
              <td align="left">Replace a value with a stable token</td>
              <td align="left">This document, <xref target="te-structure"/></td>
            </tr>
            <tr>
              <td align="left">truncate</td>
              <td align="left">Shorten a value</td>
              <td align="left">This document, <xref target="te-structure"/></td>
            </tr>
            <tr>
              <td align="left">none</td>
              <td align="left">The class occurred and was disclosed untransformed</td>
              <td align="left">This document, <xref target="te-structure"/></td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="coverage-reconciliation-outcomes-registry">
        <name>Coverage Reconciliation Outcomes registry</name>
        <t>IANA is asked to create a new registry titled "Coverage Reconciliation
Outcomes" in the same "Disclosure Evidence" group.</t>
        <dl>
          <dt>Registration policy:</dt>
          <dd>
            <t>Specification Required (<xref target="RFC8126"/>).</t>
          </dd>
          <dt>Registration template:</dt>
          <dd>
            <t>Outcome name (unique ASCII token); description; reference.</t>
          </dd>
        </dl>
        <t>Initial contents:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Outcome name</th>
              <th align="left">Description</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">matched</td>
              <td align="left">The Item corresponds to an Item in the other population within the declared bounds</td>
              <td align="left">This document, <xref target="cr-procedure"/></td>
            </tr>
            <tr>
              <td align="left">observed-without-receipt</td>
              <td align="left">The Data Source recorded activity against a Data Object that no Receipt in the Window names, or activity beyond what the declared multiplicity bound admits for the Receipts that name it</td>
              <td align="left">This document, <xref target="cr-procedure"/></td>
            </tr>
            <tr>
              <td align="left">receipted-without-observation</td>
              <td align="left">A Receipt in the Window names a Data Object for which the Data Source recorded no activity</td>
              <td align="left">This document, <xref target="cr-procedure"/></td>
            </tr>
            <tr>
              <td align="left">excluded</td>
              <td align="left">The Item was removed from comparison by a Mapping Profile rule</td>
              <td align="left">This document, <xref target="cr-exclusions"/></td>
            </tr>
            <tr>
              <td align="left">indeterminate</td>
              <td align="left">The evidence or the Mapping Profile does not determine an outcome</td>
              <td align="left">This document, <xref target="cr-procedure"/></td>
            </tr>
            <tr>
              <td align="left">invalid-window</td>
              <td align="left">The Window is unreliable (counter regression or snapshot mismatch)</td>
              <td align="left">This document, <xref target="cr-result"/></td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
    <section anchor="implementation-status">
      <name>Implementation Status</name>
      <t><em>This section is to be removed before publication as an RFC, per
<xref target="RFC7942"/>.</em></t>
      <t>One implementation of both mechanisms exists: the Conarium gateway
(TypeScript, MIT license, <tt>@conarium-ai/core</tt> on npm). It has run at one
site since July 2026. Its receipts carry per-class masking counts as in
<xref target="transformation-evidence"/>. Its <tt>conarium-reconcile</tt> tool implements
<xref target="cr-procedure"/> against PostgreSQL statement statistics, but not all of it:
the gaps found so far are stated below, and others may remain. The tool is a
single file. It has no dependency on the package. A third party can run
it without trusting the implementation under audit. Conformance test
vectors ship with the package.</t>
      <t>The state below was measured against the published 0.2.38 package. It was
not read from the package documentation. It is now checked, not measured
once. Every revision of this section up to -04 described a tool that had
moved past it. Each time it claimed less than the code did. The
correction is at the end of this section. The failure is more instructive
than the current state.</t>
      <t>As of 0.2.38 the tool emits the result statement of <xref target="cr-result"/> as
<tt>coverage-reconciliation/2</tt>, on a flag of its own. The <tt>/1</tt> body is unchanged
and still carries <tt>conarium-reconcile/0.1</tt>. The <tt>/2</tt> result carries
<tt>profile</tt>, <tt>bounds</tt>, <tt>outcome</tt>, <tt>items</tt>, and <tt>counts</tt> under the names used
here. It reads Mapping Profiles (<xref target="cr-mapping"/>), including the three
<tt>clocks</tt> fields.</t>
      <t>The behaviour below was observed on one fixture: a Receipt naming the object,
timestamped three seconds before a two-hour Window, together with one
infrastructure statement.</t>
      <ul spacing="normal">
        <li>
          <t>With no profile, <tt>profile</tt> is <tt>null</tt>, all three entries in <tt>bounds</tt> are
<tt>undeclared</tt>, and both items are <tt>indeterminate</tt> — the data statement for
want of a declared skew bound, the infrastructure statement for want of a
declared exclusion rule. In the <tt>/2</tt> result the tool applies no exclusion
rule that is not in a profile, which is the requirement of
<xref target="cr-exclusions"/>. Its <tt>/1</tt> output still reports such statements under a
category of its own, decided by rules built into the tool; that output is
not a result statement in the sense of <xref target="cr-result"/> and does not claim to
be.</t>
        </li>
        <li>
          <t>With a profile declaring exclusions but no <tt>clocks</tt> member, the excluded item
carries the profile rule that removed it, <tt>bounds.exclusion</tt> is
<tt>operator-declared</tt>, and <tt>bounds.skew</tt> remains <tt>undeclared</tt>.</t>
        </li>
        <li>
          <t>With <tt>clocks.skew</tt> declared larger than the offset, <tt>bounds.skew</tt> is
<tt>operator-declared</tt> and the item remains <tt>indeterminate</tt>. A declaration does
not manufacture a match.</t>
        </li>
        <li>
          <t>With <tt>clocks.skew</tt> declared smaller than the offset, the same item becomes
<tt>observed-without-receipt</tt>. The declared bound reaches the comparison and not
only the report.</t>
        </li>
        <li>
          <t>A skew bound declared both in a profile and through the command line fails
unless the two parse to the same number of milliseconds; a <tt>clocks</tt> member
carrying a fourth key fails and names the key it rejected.</t>
        </li>
      </ul>
      <t>Gaps remain. One is in the tool's exit codes, which predate this
vocabulary. They are not a mapping of it. They were left unchanged on purpose. An exit code is
a compatibility contract. Renumbering them to match this document would
break installations. That would make a specification look implemented.
One code was added rather than renumbered. It is for the temporal
outcome. Existing callers do not notice it.</t>
      <t>The gap that produced this section's own history is closed. The -04
revision carried four statements. They were accurate when written. They
were false within days. Each claimed less than the code did. No mechanism
here found them. A reader holding the document beside the tool's output
did. The -05 revision recorded that the test suite had no check against
this section. Until such a check existed, it said, read the section as a
claim about the date it was measured.</t>
      <t>A check now runs this section instead of reading it. Every behavioural
statement above is bound to a run of the shipped tool. The fixture is
named in this document. Two directions are enforced. Every value a run
produced must appear in the sentence that states it. The number of
statements must equal the number of bound runs. A statement with no run
is unmeasured. A run with no statement is a dropped measurement. The
revision under test is derived from the repository. It is not named in
the check. A hard-coded revision is the same class of stale declaration
the check exists to catch.</t>
      <t>The first thing it caught was the sentence in the paragraph above. From
the commit that added the check, -05's account of its own absence was
false. A posted draft cannot be edited. Revision -06 is where the
correction had to live. A check whose first finding is the sentence
claiming it does not exist has shown the failure mode it was written for.</t>
      <t>Two limits, stated rather than left to be found. The check pins the
behaviour statements. It does not pin the prose around them. A paragraph
can still go stale in a way nothing runs. A failure has two honest
resolutions. Change the code back. Or write the revision that says what
the code now does. Editing a posted draft is not one of them. The cost of
drift is then a document, not a diff.</t>
      <t>More gaps were measured against the published 0.3.7 package, not 0.2.38,
and the check does not run them. Two are against this revision. 0.3.7 does
not implement the exception in <xref target="cr-procedure"/> for an item over a declared
multiplicity bound under either reading of the clock: it reports such an item
<tt>indeterminate</tt>, as -07 required, and the conformance case it ships for that
item expects <tt>indeterminate</tt> and rejects <tt>observed-without-receipt</tt>. And 0.3.7
counts a multiplicity bound per Receipt, but it draws a pattern over several
objects that some Receipt names whole only on those Receipts. Beside such a
pattern it can report <tt>matched</tt> a pattern that <xref target="cr-mapping"/> makes
<tt>indeterminate</tt>. With a bound of 1, Receipts naming customers and orders,
customers, and orders, two statements of a customers-orders join and one on
orders, it reports the orders pattern <tt>matched</tt>.</t>
      <t>Four predate this revision. 0.3.7 digests a Mapping Profile as the bytes of
its file, not as <xref target="digests"/> requires, so the same profile written with
different whitespace has a different digest. On a counter regression it exits
with code 20 and writes no result statement, where <xref target="cr-result"/> gives the
outcome <tt>invalid-window</tt>. It accepts a fractional duration such as
<tt>0.0001ms</tt>, which the grammar for <tt>clocks.skew</tt> does not admit. And it reports
a Receipt as <tt>receipted-without-observation</tt> only when none of the objects the
Receipt names shows activity: a Receipt naming customers and orders, with
activity on customers alone, produces no item for orders.</t>
      <t>A second check covers the conformance class rather than this document.
Every outcome an item in the tool's result can carry has a case that
produces it. The result-level <tt>invalid-window</tt> is not among them, because the
tool writes no result statement for an unreliable Window. Each independent
ground for <tt>indeterminate</tt> has a case of its own. The
list of outcomes is read from the tool's own result. It is not restated
in the check. An outcome added to the vocabulary arrives there without a
reminder. It arrives failing until some case produces it. A conformance
class can lose coverage in silence. Nothing in a test set records what
was removed from it. A class that has lost coverage still passes.</t>
      <t>Earlier revisions of this document, and releases of that implementation
up to 0.2.21, described a clean reconciliation as "covered". That word
asserted more than the procedure establishes. It was corrected in the
implementation in 0.2.22 and in this document in -03.</t>
      <t>The temporal rule added in -04 has the same history, compressed. The
implementation admitted Receipts on an exact comparison across the two
clocks. A Receipt three seconds outside a two-hour Window produced
<tt>observed-without-receipt</tt> and a bypass message. That was raised in
review of -03 on the SCITT mailing list. It was reproduced. It was
corrected in 0.2.27. The correction was then attacked. A Receipt from the
previous day named the same object. It moved a real in-Window absence
into the new outcome. The implementation offered the boundary as its
explanation. A twenty-three hour offset cannot support that. 0.2.28
bounds what the implementation is willing to suggest. That is the
reporting choice in <xref target="cr-mapping"/>. Both defects were in the
implementation first. Neither was found by reading this document. The
first came from review of -03 on the list. The second came from an
adversarial review of the implementation. The fix had loosened a default.
Its author was not the party who should clear it. What made the second
sentence sayable was the tool's own output. This text did not yet exist.
The document's part was smaller and later. It is where the correction has
to be written down. The next implementation should not have to be
attacked to learn it.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <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="RFC6838">
          <front>
            <title>Media Type Specifications and Registration Procedures</title>
            <author fullname="N. Freed" initials="N." surname="Freed"/>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <author fullname="T. Hansen" initials="T." surname="Hansen"/>
            <date month="January" year="2013"/>
            <abstract>
              <t>This document defines procedures for the specification and registration of media types for use in HTTP, MIME, and other Internet protocols. This memo documents an Internet Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="13"/>
          <seriesInfo name="RFC" value="6838"/>
          <seriesInfo name="DOI" value="10.17487/RFC6838"/>
        </reference>
        <reference anchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8785">
          <front>
            <title>JSON Canonicalization Scheme (JCS)</title>
            <author fullname="A. Rundgren" initials="A." surname="Rundgren"/>
            <author fullname="B. Jordan" initials="B." surname="Jordan"/>
            <author fullname="S. Erdtman" initials="S." surname="Erdtman"/>
            <date month="June" year="2020"/>
            <abstract>
              <t>Cryptographic operations like hashing and signing need the data to be expressed in an invariant format so that the operations are reliably repeatable. One way to address this is to create a canonical representation of the data. Canonicalization also permits data to be exchanged in its original form on the "wire" while cryptographic operations performed on the canonicalized counterpart of the data in the producer and consumer endpoints generate consistent results.</t>
              <t>This document describes the JSON Canonicalization Scheme (JCS). This specification defines how to create a canonical representation of JSON data by building on the strict serialization methods for JSON primitives defined by ECMAScript, constraining JSON data to the Internet JSON (I-JSON) subset, and by using deterministic property sorting.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8785"/>
          <seriesInfo name="DOI" value="10.17487/RFC8785"/>
        </reference>
        <reference anchor="RFC9943">
          <front>
            <title>An Architecture for Trustworthy and Transparent Digital Supply Chains</title>
            <author fullname="H. Birkholz" initials="H." surname="Birkholz"/>
            <author fullname="A. Delignat-Lavaud" initials="A." surname="Delignat-Lavaud"/>
            <author fullname="C. Fournet" initials="C." surname="Fournet"/>
            <author fullname="Y. Deshpande" initials="Y." surname="Deshpande"/>
            <author fullname="S. Lasker" initials="S." surname="Lasker"/>
            <date month="June" year="2026"/>
            <abstract>
              <t>Traceability in supply chains is a growing security concern. While Verifiable Data Structures (VDSs) have addressed specific issues, such as equivocation over digital certificates, they lack a universal architecture for all supply chains. This document defines such an architecture for single-issuer signed statement transparency. It ensures extensibility and interoperability between different transparency services as well as compliance with various auditing procedures and regulatory requirements.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9943"/>
          <seriesInfo name="DOI" value="10.17487/RFC9943"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC7942">
          <front>
            <title>Improving Awareness of Running Code: The Implementation Status Section</title>
            <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <date month="July" year="2016"/>
            <abstract>
              <t>This document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature.</t>
              <t>This process is not mandatory. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. This document obsoletes RFC 6982, advancing it to a Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="205"/>
          <seriesInfo name="RFC" value="7942"/>
          <seriesInfo name="DOI" value="10.17487/RFC7942"/>
        </reference>
        <reference anchor="RFC8032">
          <front>
            <title>Edwards-Curve Digital Signature Algorithm (EdDSA)</title>
            <author fullname="S. Josefsson" initials="S." surname="Josefsson"/>
            <author fullname="I. Liusvaara" initials="I." surname="Liusvaara"/>
            <date month="January" year="2017"/>
            <abstract>
              <t>This document describes elliptic curve signature scheme Edwards-curve Digital Signature Algorithm (EdDSA). The algorithm is instantiated with recommended parameters for the edwards25519 and edwards448 curves. An example implementation and test vectors are provided.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8032"/>
          <seriesInfo name="DOI" value="10.17487/RFC8032"/>
        </reference>
        <reference anchor="RFC9052">
          <front>
            <title>CBOR Object Signing and Encryption (COSE): Structures and Process</title>
            <author fullname="J. Schaad" initials="J." surname="Schaad"/>
            <date month="August" year="2022"/>
            <abstract>
              <t>Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need to be able to define basic security services for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR.</t>
              <t>This document, along with RFC 9053, obsoletes RFC 8152.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="96"/>
          <seriesInfo name="RFC" value="9052"/>
          <seriesInfo name="DOI" value="10.17487/RFC9052"/>
        </reference>
        <reference anchor="I-D.farley-acta-signed-receipts">
          <front>
            <title>Signed Decision Receipts for Machine-to-Machine Access Control</title>
            <author fullname="Tom Farley" initials="T." surname="Farley">
              <organization>ScopeBlind (Veritas Acta)</organization>
            </author>
            <date day="3" month="September" year="2026"/>
            <abstract>
              <t>   This document defines a portable, cryptographically signed receipt
   format for recording machine-to-machine access control decisions.
   Each receipt captures the identity of the decision maker, the tool or
   resource being accessed, the policy evaluation result, and a
   timestamp.  All of these are signed with Ed25519 [RFC8032] and
   serialized using deterministic JSON canonicalization [RFC8785].

   The format is designed for environments where AI agents invoke tools
   on behalf of human operators, particularly the Model Context Protocol
   (MCP) ecosystem.  Receipts are independently verifiable without
   contacting the issuer, enabling offline audit, regulatory compliance,
   and cross-organizational trust federation.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-farley-acta-signed-receipts-03"/>
        </reference>
        <reference anchor="I-D.marques-asqav-compliance-receipts">
          <front>
            <title>Compliance Profile of Signed Action Receipts for AI Agents</title>
            <author fullname="João André Gomes Marques" initials="J. A. G." surname="Marques">
              <organization>Asqav</organization>
            </author>
            <date day="21" month="September" year="2026"/>
            <abstract>
              <t>   This document defines a profile for signed action receipts and
   independently checkable evidence about agent activity.  It specifies
   versioned payload and signature semantics, hash-chain linkage,
   timestamp and witness policy, receipt verification and bounded
   regulatory-evidence mappings.  It draws on ACTA-RECEIPTS but states
   its profile-specific overrides explicitly.  A receipt supports checks
   about recorded bytes, identity, linkage and retained evidence; it
   does not by itself establish that an action occurred, that all
   actions were captured, or that an organization complies with a law.
   The profile supports retained historical receipts through explicit
   version and legacy rules rather than rewriting their committed bytes.
   Its intended core and implementation limitations are described in the
   body.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-marques-asqav-compliance-receipts-09"/>
        </reference>
        <reference anchor="I-D.chueayen-attestation-receipts">
          <front>
            <title>Enforcement Attestation Receipts for AI Inference and Agent Action Decisions</title>
            <author fullname="Anya Chueayen" initials="A." surname="Chueayen">
              <organization>Aqta Technologies Limited</organization>
            </author>
            <date day="25" month="October" year="2026"/>
            <abstract>
              <t>   This document specifies two compact JSON records, signed with Ed25519
   and verifiable offline under a pinned public key.  The first is an
   attestation receipt for an AI inference decision, binding an outcome
   to a request hash.  The second, added in this revision, is an action
   record: the decision an enforcement point takes before an agent's
   proposed tool call or other state-changing action runs, whether that
   decision is to allow or to refuse.  An action record is signed by the
   enforcement point, never by the agent, and binds the decision to a
   hash of the exact canonical arguments proposed.  The document also
   describes how a human approval can be bound to exact action values
   with single use and expiry, how either record could be carried as a
   COSE_Sign1 Signed Statement and registered with a SCITT Transparency
   Service, and where the current format does not yet do so.  Both
   formats are intended for settings where an operator-controlled log is
   not, on its own, sufficient evidence of the decision.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-chueayen-attestation-receipts-05"/>
        </reference>
        <reference anchor="I-D.aylward-aiga-2">
          <front>
            <title>AI Governance and Accountability Protocol (AIGA)</title>
            <author fullname="Edward Richard Aylward Jr" initials="E. R." surname="Aylward">
         </author>
            <date day="26" month="January" year="2026"/>
            <abstract>
              <t>   This document specifies the AI Governance and Accountability (AIGA)
   Protocol, a practical, economically viable, and technically
   enforceable framework for governing autonomous AI agents.  AIGA is
   designed to address real-world deployment constraints, adversarial
   agent scenarios, and economic incentive alignment.

   The protocol is founded on a Tiered Risk-Based Governance model,
   applying proportional oversight to agents based on their
   capabilities.  All agents are governed by an Immutable Kernel
   Architecture which provides a non-modifiable Trusted Computing Base
   (TCB) for enforcing policy.  This is combined with Action-Based
   Authorization, where critical operations require real-time approval.

   To solve the single-point-of-failure problem, the protocol uses a
   Federated Authority Network of regional, cross-validating hubs and
   provides a Network-Level Quarantine Protocol for enforcement.  The
   entire framework is designed around Economic Incentive Alignment,
   making compliance the most economically rational choice for
   operators.

   For high-assurance (T3-T4) scenarios, AIGA specifies advanced,
   redundant mechanisms including Multi-Vendor TEE Attestation (M-TACE),
   AI "Warden Triumvirate" Triage, Human Review Board (HRB) Multi-
   Signature, Peer Consensus Failsafe &amp; Identity Rotation, and Double
   Ratchet Cryptography.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-aylward-aiga-2-00"/>
        </reference>
      </references>
    </references>
    <?line 1239?>

<section numbered="false" anchor="changes-from-07">
      <name>Changes from -07</name>
      <t><em>This section is to be removed before publication as an RFC.</em></t>
      <t>Changed the outcome of an item that the temporal rule of <xref target="cr-procedure"/> kept
<tt>indeterminate</tt> and whose statement count exceeds the declared multiplicity
bound even with every Receipt naming its objects counted: it is now
<tt>observed-without-receipt</tt>, where -07 required <tt>indeterminate</tt>. An
implementation of -07 reports such an item differently. Extended the
definition of <tt>observed-without-receipt</tt> to activity beyond the declared
bound, and qualified the definition of <tt>indeterminate</tt> and the semantics
section to match. Stated how a multiplicity bound is counted: one budget per
Receipt, shared by the patterns that draw on it. Qualified the rule against
comparing call counts with receipt counts one-to-one: they are compared at no
ratio other than a declared multiplicity bound. Stated in
<xref target="implementation-status"/> the gaps measured between 0.3.7 and this revision.
Acknowledges a report by giskard09.</t>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The discipline of stating what each structure does not prove is owed to
every auditor who has been handed a green dashboard and asked to trust
it.</t>
      <t>Iman Schrock reviewed revision -02 on the SCITT mailing list. He identified
two overclaims. One was that a clean reconciliation established coverage of
the source activity. The other was that Transformation Evidence proved the
transformation rather than the Issuer's assertion of it. Both were
corrected in -03. The outcome vocabulary of <xref target="cr-procedure"/> follows from
that exchange. So does the rule that a declared bound cannot yield a
stronger outcome. Reviewing -03, the same reviewer established a further
point. An Item whose classification rule does not resolve under the pinned
profile is <tt>indeterminate</tt>, not excluded. Revision -04 applies that rule
one layer up, to bounds.</t>
      <t>Walter Hawkins read the reconciliation implementation. He found the
temporal defect -04 exists to correct. Window membership is decided
across two clocks. An exact comparison manufactures an accusation where
no gap exists. The failure is asymmetric. It produces false findings
rather than missed ones. He also observed that the sub-second case is
the dangerous one. It is the one a reader will believe. That is why
<xref target="cr-procedure"/> sets no floor. The requirement that a source population
declare its own completeness on the same standing ladder is also his.</t>
      <t>Joel Hillier, reviewing -04 on the SCITT mailing list, asked for named
fields. He wanted a stated encoding for the temporal correspondence, not
prose. Another specification could then adopt the same shape. The three
<tt>clocks</tt> fields in <xref target="cr-mapping"/> are written to be copied. They answer
that request. He also observed that a gaps section going stale in the
understating direction is the same failure as one that overstates. That
is why the Implementation Status section of -05 was rewritten
from measurement.</t>
      <t>Henri Sirkkavaara established the distinction in <xref target="sec-completeness"/>.
One construction supplies an expected quantity to a verifier from
outside. The other carries it inside the signed material. He built the
second. He named what the first leaves an auditor unable to do. The
consequence is stated against this document's own implementation, which
does the first. A running count derived from the sequence number it
accompanies adds no information. That narrower observation is this
author's, arrived at while measuring his. It is recorded here because it
bears on the construction. The distinction stands.</t>
      <t>Andrew Yourtchenko reviewed -04 as a reader new to the work and identified
the length and density of the non-normative prose as the document's
primary obstacle, ahead of any technical point. He proposed applying the
principles of ASD-STE100 (Simplified Technical English) to the
non-normative text and published a rule set and a rewritten draft to show
the effect. The sentence-length pass in -07 follows that suggestion.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+297XIk15El+P8+RWzxB8meTKiKokQKNTM96GKxCY3IYheg
5srGxgaBzAAQqsyIVEQkQAxFs32I/b07j6BnGNO+yD7J+jnufu+NyEhUSbNm
a7a7bS0JBUTcuB9+/fO4+3K5DEM9bKrT4tllVzb9Tdtty6Fum+L1fb2umlVV
lM26eNXeV115WxVvq1XbrOpNrQ/J48XZfl0P5fWmKr4qh7L4qu5Xm7bfd9Wz
UF5fd9W9jJ1+Gcd9FlblUN223eNpUTc3bQjrdtWUW5nKuitvhuW6ve32y35V
D/JzfH9Z2fvL51+Gfn+9rfteZjI87uTF89eXX4dmv72uutOwluFPg0y3r5p+
358WN+Wmr4JM55eh7KpSpnVRrfZdPTw+Cw9t9+62a/c7/PbV+eXls/CuepTf
rk9DsSy6alXVuwE/bsv+Xd3c2m+zzcBvBuzhTkZvVo/4d5p3CP0gO/lfyk3b
yEwfqz7s6tPiPw3talH0bTd01U0vPz1u8cN/DqHcD3dth6+HQv7vZr/Z6O68
3lbvildlU3zV/vV/7/b8aynbVH8998itPdF2t2VT/1fO9LT419dvz/7n4vL1
f/zuze/e/Pavfyl+99e/fPvXv1y+/qr4P/63v/7l7X98ffnXv6SR3zzx8nnx
u/Nvz/HmxTneO+drq3bfDDjay7f8d7Ut681pUZ3wVP+D7FvZ1fvtybq6D6FR
oruX4yqKt1+/+uzFi9/Yj1+++OJz+/HXX/7yy/jbz37tP37x5a/sx9/85vNf
noYAYhqP98VvPv/MH3/+S//xN89/xR/Pl1+d3JTdpnpclquhXPb1bVOtl3bk
vT+yLbs/7at+WfZ/Ku+Xq3a7k3MHHU4fXN3tq/KxapblMFRy6Ni0g4fKx81D
2a2XZX1bLmUaYblcFuV1LwS0GkLgnXKq60lo3bp4uCuHoixuhbAfysfioWsH
uZ7X7V5+2xTlalX1/UlxeVc9Fu1W3r9rH3ALymJ1Vza31ZpX+eGuGu6qrqjk
Rj/aS8WmusHI9kGMUfeF3Mf9tmqGYl3d1I0Q7PDQFn79ip0soS3XPXmAkGpf
ycR2+P4RPoKtqHr5fr26C/flZl8Vq03Z9/hdJYxh8Peq9YIzlekviodaxpYF
rsque5R7V/BN+YyzpDBhSTgZuYC9XKp9B/a1EkqQO64kWXU9h0yLLfpqKDBW
UYaHulm3DyfF63J1V9RDtS1kG2QdqzvMqb3uq+5ettHnFMdY+A/pj0FORF/g
tBZF9eNqs19znE4Y3rqSuWzrRvaERyYj9PvNgA82LYa+lkXIJsuJhn9qZcJx
v7vqtu4HzLcvLkirxQW2FkfVF7IDZUEOpgfhzOhCZlKvqiNHK98smuoh7oke
32LMz7YV6Kjut1wCrkk5gKPrwydKw9t6vd4It/uoOBcG0K73K/LGcPEoc972
xW5T4lCKXbupV4+Rlq+r4aGqGtLxfmhlPFnWalNjjqCFsgAhBz1TLAL01tuY
dbMSft4LdWwehdMI5esdXhR3ZX+3lFnX2CWl9eC36qS4wB0oN5NV93JUssF2
kfo7nENZbGoZ96Q4iw/XfYh34aZrt3IHcF6dUNqAe7qrOiVm/sEv5zlPON5Z
mUAzBH2er664sKG1Ky+beimXDhdLZrfZtA/+LbzRtfKR4VEe+rru+kSFfSHi
sF6VG9kO3jp93u76XbnbVbIftkBIDJ07TySsq1UNiWp/Xrekxx78BoP425gj
3iJ/8dPDL/zaNeuAf+oZYuP8qLf8T/8O013L7SQ1De27SiRMZddbRpTNq0KS
n5iOfH4YMxfZS069q+9LoSbhJ/UW3xKOgJ2VR8qNH7gspdLLta76VVdfVwVP
FBQn3FYmsanKrultswrVaR5K3LhSTgKX1J+MQ/GVyFN34Mgrkm672W8bY6yY
oq0+ZFxOGUGhuyTjyDlegJeB/Y25U7MB+7oH89JDrPpIAnLDZKhE1GfBrg0f
kKkL8+rTUdnxOAvLpuaDYWEhkwRVnAsvUlq7qHaV3J5BGMpJ8Y3cNH1AuEuF
XZAxtq0cJ+9vVwk1Vx0YeHtjxG1ryG8b7lpfb3jrcUfC6EmKiQaXtsCFH0DD
ryCI5XsNSLupKnlWFsltxF6B58sXg0sBIyP/iwgLWQyvVGk3sOVJyveafHNO
8Y+Q7SBu5iwnHQlJkefCAPcQRyomKxeTwi2PSspPfvppTOdR6f35509PsT7n
94Vskly0ArdR9Moivy/CanC3TeJGWSvbb3fsQOrKONeP9ni5UrGFw6sbvfvc
Mx1YD0Fkcm3EZWIZyzpmLMiyVvan5Vh1tmUJAQotQ6SQ5ct0lI+bbOSXj4r3
vpFtvWuF+ZVK1irMsSbskYn9ISNnXC09FdCWiX58AjtV32BluD3yK1EEhIZE
i61JHEY9J8V39otdu9tvIkeSt/db8gAlTb1E4NWl8A4ZRljshmvg1W87+XEn
9Opnv+qWW+GycldkX0bKgZ8n5lv2MtLfp5sUE90EK8u1EzIt2TORBPIrOVMq
IBktq2qi+kh2c7dVCb7TCvc+opmEXCcpTCeBIiMk9tNPpsP//POJaTD9fida
Nj4IobNeghEuRKzUojnzti7LaHyqWtRxRQdaTmJZNQUDz/zkyA0+ogvJr01p
qUDsavP1YtiInFn1elPkmVxlKqLKJJv4hqQiZCb0ut4LX6SZG5V7I3UXv1FJ
iNqQqRDha9oqsl3vMVx+/nlRfKtGS9CH32vC4BWa+2bC2HtPWjQ//1zsham9
Xn/2q1+9+I2eIqws+T2G+u3Fm++CmKJtA4XEbEh7Skw3nPWZ2kK2orFlpKP3
PrwYd0LZd4/XXb3ONNB+Xw/KNOJJ9zvZyJvH4revLuSegjcK41MzRfc9+HEf
48JyEY5wMjnMjz4SEoMMKrbtulIZV4JYV+W1PCb86KePBj6w5AM/B+oPsOKj
8KmN7HvzQmAvSJH9Xi4n+a8bTWAUZGPC9uQWQSERWtpWldCPqLuqLZkqZDz0
RL/4zybcMUH8nT6aC+OdHXZFZGfR7RuwfmwT75WJSdNJS6FzuYkdRGym4rlB
pQoXfwajEq663fdyb8Ti5+M/KCNWzhbnR952bs/ixB7ragNFH7qQzKjatZ3p
H98qNyy+79obUQ6CbNGDbBgmfv3IT/gqnckqH4cxcd233bUws8QEo8QQXmxs
j4ogviQ0wbOXL9zLNdSjhGha17dC+Us9g53OY2GTrNY6Dq/twswVHty6oNMH
c4egoTThECfFVxwQt/+PctQywXdN+9AE2eSb+kfYt+ciRWRD31WPFCSiotQ9
J2bm3XIjV5Iqp3A/Kr3Cnxv41NYhl3D9UAvNCR2rRKtxTA1Mg5emp2F2FET7
ISpQf9qDqw2PgaqR8KFeLoUKSqwcUkoodLnKlC+cJ+/FD3cqgPuR+mN2BDX0
Q4HiVkqldlavl7Wqu0I2JapTU99CiHfVNXpTdJO3Uf7rplypNhR5Aychq1Qn
hBhy+4Z6POSIm2gYR4/g4955MxSojtfSTYTxdGArkAlAjuJDcjhciDxcU2RT
tauWukjegLOjjgyT+abGg9D6RLsHYp6UEZJiaNJDGIn8I23guXsYlE6//f3F
ZfHdm0tIbNxveZjrXASduvw/CAY6dId/iKlHi8LUlCj99PBdHYoHm+aduTPU
hs5XWt7CbIBaEvwCL01HWk/1I7nU2NlrElfb3CZdvRxMsdLDOFSkxNKLSg1o
Gso/dsNvMfSQpPXoVgV8TCxvvCI70aqWiuejHHhbqerX39U7KD+u4xaZtAzh
zOU8uBJMz2aQw+Qh5AaPKnfwOsGv3dzqbuF79mLwO3fsVRhU5bZ2A79XNg+r
BAwZt001toArgnnIdbm5EVNAxqFzpj8wbaLHApfiBq4G7k506PEuiMZb4+Rs
nbqDIX/GKJm7IPftHsaIqHUUH7Qs+UDkVH35SEq9g7ddvy+TMYNjbA2aNFAe
ft+KDBZ1vHss7vDIpiIB6ocDHBkiQ+VrZDPCXeCH601amuF4XW2EtPpjp0lS
0l1WAs4V+pAbA0KSXaU+m8wgozQv+7pP5kd6idtmKoI+oJ7afVPzdNf1mrzF
Tvmk+KHt3hXOk1Qo1ErIXaBMbGiiC2ftB1smqAF0ZASglmOnKof7vUQHEQmw
H/hEozdbJb2xq2xDRqQANjciwZzR80SU2xtNVOGAcsh2zDWTfUSdtEZo8lR2
AqIXysg4UYxKmsAm+8gf97N0hxvu72H3gl6nDTZ748qOq+egxr41xYgPqp7A
O6E3i/sc4rXhYZvxR76I0yD3BW9fiejJd9VvdXRS4qu25Iyk6CCUfbkZbI0q
JsyapxLB+0oCXQ1xIPBu530wAox/OctWutFp6ZpandqbBgxkqG6UW/UPcELd
lZsbHVIoiZZYyMb8SESau996sqmvoGrX/LcSILSaBzp2nkEEPVvo/0IU4ee3
r//l9+dvX3+Fny++Ofvd7+IPwZ64+ObN73/3Vfopvfnqzbffvv7uK30Zom30
q/Ds27M/PFPh9+zN95fnb747+90zdcPlLI88szVGXXUiG1VABNc06BX5p1ff
//f/9uJz0eH/Jwtbib2i/0DgSv7xcFeZE4VOPP3nAPYLk7akA1CUMWHuO7Fj
N1AfhczucIq4KrKb//CfsDP/+bT4t9er3YvP/739Agse/dL3bPRL7tnhbw5e
1k2c+dXMZ+Jujn4/2enxfM/+MPq373v2y3/7jxvhF8XyxZf/+O+D2Ur0d1M7
BYfmkYgtCDOma/e3UH9OQ8jsmdNwquyGYYHiTqS267Zw3GksKbJ9Y7HmkRTy
7WAR+P0rkqr1CXmw8JodVH4NRAj3rj7uMz8ceVQPVQiKkJkjPiGy2ib6ZI2B
uS/3/bEPmU22zIXpmL25IxZJDe2dGyjJVVSlo2tYNisqxpjaWcGQCbTnTU0Z
IxtBF+cnIhnE+hGCzdyDn6Ywh5tb0IdkcubjD9Bg8Skf3Hx3iQFlMIDouR5b
cBPPjQwOZnbbtNhbjzmMPTO4QkIX8vnvo/v9FVx4Og1wYWhdijXI3J8md+nR
EWkHM4wSfxJiwPHTQWYE8IyhbDAXFT3lZlmv8c/dnZzxMxy/Grz6+aHeGg+B
K5z8XB2sEx1YlhkjRgs1Em1zHlo4QqN3Uy2jnCA+7g+DnCcFTSxzfZYqdLc7
Dgl38XiElzGCURZvfXOFLcFcNMtPY6FllB1uYGBuqjTJya7eLfLD/LgvZoz+
ECb2vG4UohsyrtrMeqsWRbQCjErcPFj4NoytA57TTknAbxWUGyXQ5UYUg42N
wSWYT0T9GfZn30qQ3pBiIv/n//K/Is642Ueeor4AV7y2cu1q+H/k1YXFdGQ/
3FcCeIja/9zP+OV3oh3qQFkMbbuID3T7DaJhuVfeJ9dHp61eTPWM1z3106nP
RM3DIreQ/ATld7tN+6gbrrHnbVXikpKzpTimnoEM4tf/wMQKAb5ynCfUBmqs
rkJlpJ7c/MnTDkUj9y1hl+CXxuk57VP9x05Abd1BM+ya6HiyGLDK5eR14rnJ
IDKUvaFrxLifxN/wKrwhC/hUnqu7OJ3oScF8bCC/ITx31ejLfAhdR7yw5vlw
r59s5okM8sqFj5rTx6cChUAkA4MQiuOAdLpyh//SPAHuj706MZmoY+Q8cCi7
W0QTbw5iJ27cv/Wo37kdhpi0wjPke36EVDrhuOxjhPQTiMc/7Wvhb5SEKyHg
smh1CU5RGg/FwrNwRgru0UztsSqy4SsGC3TRsh5RJxFR6XQxWYwdftAnHbjl
MRcul8RJlHTo0fVBXypt/Lv9FjGSjv9qVHtXteJQQNE/7VNMFl3XbioVibZx
rg0cYgT6oyEznZyxoKTtg+k6k5zGOjid9NWDCUFItnIcS/V/r01Yu59yrAaL
/lCJqo9betv0ujfmwHytAvHUeELdyPnXIEdeO/CtzNs05ikQAfqv6ddtdOA2
qCu726y9HhTDASd1ilyZFCBfcx6Wf/XQm6RBmsFW5EytxpXyRYPgZuWF87Wk
xTBalgSMnA7FI3X46sA7jfh+LmniEfrA5GHcd9WWclf9RMCbHVr3Iw4JGUMe
eWPzMraS7wl1EWUkCnBQNFS+ZPBdX3TSZuNuzhCy/sloNC03X8GHvp29czSM
JzQuc3yWawTPoktULHWQEgXmSfEDPQ7XUIZKC5H0QLzw85AwefwlD7co4Eck
Gp3AmLUzxarpGU3KApanU/SP3pfyIAwKDvi1HM4xnjXYqc4HNfBmSeExzy5y
l7ENkjiBrOVf1bd2yEiFZ6/eETnhMbVFDHoslJHORW5VMMxBBve9bSNsNyFF
mC03BnxDKBfP8KNqf8Hecrd9jPdHv/DIF39k5zBCdM9PvezwSRzb8Z8+Ooa1
oHf3+30HN1kIx+HR9Iks4p3LjCzT2qJdEl4dATy60jLdgsUxQEaYADIIooGD
Ss+TOz+esAY9KLfpwl1S+VoEh8p5/Bw8QQijpsNH6C6iYUQOqbsQktFI8uPk
7soioxfR/y+bWy2j++/n47vIeSFWbIpDQmskN8C2ArBbzLpwdX8FEk7fMeMB
nkY6zb9uu7EkOy2ujhzzL15AZbpKMaMrvR1K/MV1ncnFiOsRQUj32uZxcuQL
quF7GCC4o2ZqZQarnk9mCH8Ca+aBXGrGtvUgNc1sj6K7TQ1040IHxI+felSR
L2NLTcSDXsDodElyI7Bgk1Xj1ZpV5XJsjDEjdx4B8qrxe2QHfHNhjvnRYNWP
cgzqaMHPDGiYgiE8CgI+AehkqIgoulIjXWfajAjkql5fFZ9gHHAU8jZfg1n2
ThkWl/uUwETRnx1nIa9nT3tUiN5zu3jrkdNiVVVicYGlXBmiyudVdl1J/4Ip
sQuVwDLOxC+RrqhNyqGXqmbfAgfZmwUI6bgS8dQ9xSNoQmA/5GrI0jivKyDN
VdJOPw9rgH5GNQtMSdE5nHAE5TU2xBvFTlwBs3m1KK4UtYmfHLTJny34fEVx
cSWUWl1ZPAbnyCQA/W0SsrYLnG9aJkHqMru4Tr6LdILELmHVyanD49IPuRsO
h5d0QUUE4rZuy3eVro08M9sdTRfJ/EKkH7k8Oq0jm44xFcmOyfEsFbCRxYA9
phS5VIy2Esyurjb96KKY4EJpcjzUfQVLdINgnZ8cfHv6KfuXRooWdhXN9Zfu
g4KnSkQZmlBDZY/cWpRFUydV97Z4eEMRATCG8w9yJ85e4QpE9sZ1GdOXURLA
h1gcgzj89JEznhDAmPVf/GSjKB75WX0maa8Ag7ERDbjGB+bhRBewOasxqsgB
FrOu/Ytvzpaf/erXge5V+bfDSaC4U4T0hSEx7NtX/V0pL5xemTzSe4MfulUp
6sGdiAOwlG25Eemz5xL8iz0hzwm2vyECA/kpzj4d9fESWQOTM8q2Papk7gPh
awwKmmYcIgMZie5bITFGkxGHfvVPb97+4tWbi9dxgzNMFpJiRA82HkpNmWSq
KCf6nNS/FjQ6ojAr8LBW1Vc9Inv+rjT38z0vzn1dPbz0kK7drKBPqlZIkCDf
t3GJYc9gJcfUh2gZCIe+N7XD1L/jOsf7QCPk5Y3b3Cchh5DksPoM9u2IkiJD
lDiDdS/5W5OHGzHB9qLE9xSEO2SDkBLW9Yr8kb7iA0S5RkWVBIOL1pWClRtT
RqOTNoIICbj3+WVs2eQvEFUqsCOfU+ABFr50EDU3A/J03xf/tepatz6vDT2V
5UMgP2QPpTXXdHClCUYqwepj4otOBHjWGYXYkb+XcQN5mXScu/K+UgQ+vMbC
+klYmcOoTyzXXDxHKajsC4e8hAbq4Y87U3O+axlQr0dwnhkFO+P86hQxhKzq
tgcQIqMKg3llGCHsvBtqWGygnTSRQtePDCBFA6kc0tAnxe+F9xN7p8HGdDB1
hGII96gbzMgmoG/j3H+Iuqj9SS3J6AaYyW4Z74Sy8rRSsvLNjaFHIRfPkr9M
OJm8XpXqfJMtNPyH+oDWXQsHZD4bD0IJtexz2Y+DUsbSVYpj0Znqa9jUpBeY
61bBbiZblZ/l95bIxArZhNEwb1xNcnyhcGCgXzGf1kNItMwo4aN2g8nNZAVk
KIuEBTG1IaqXpljKLmZRoYd5FTJTIJEJoldL0Sw0YlriK0uDNtg7kakxFcjc
RKoYKIAjEEamDNHfj7HAODuIG8Wh5gkKETgU9GtiwWcAHTniLflEjjDSYG2E
p11X9PPqvqpf6aOjHpCfPjqWYjC25o87XCfWvMXyCLs5iLuFSSDZ7LLorMMg
akQ0bQwbqKn+jwlnmBLrkrVP31ZM9CwRAgJ4rlo/g3b4bByaaN4FIFDwx+tK
U1oU2gkyXow0gbohrnXj8GDkEsncxab0bDKdlLO4h7aIWKTrCmu0BAxoqfUt
8xcVJJpQZDHc3Z+OYyjIt5iEkBdRd2ZYK+ZoxudG7sCz6BMzGCDU+rg1aRjh
kwav0NSeJmGuh5GuAMM2cTzoVGnyQVP/CB2PYUd17lU7j6GBt6+3dWOpB/cm
06A4LWPGBzWRObg3afLsMINFqLhbxn/+DK0tBsEOPCWrcie8xKOS47iwKKAE
Dt1X4TAPVnWXtm7I2BCozlwr/rkP8az40HHK5lMZ1DbGhjAMnsfFSNSDHF9T
fHJ+8ab48tfPX9Cq1tiUG9WHdv3IK97E7Eq/gv1Ktp06OyF+Yp6N8RvOYIDg
YEjEdOm4PbD8lPd9qkH0afS99NAiuVNi9FSWffovoXPJjUZ+ToqOROeyjoDl
GqTx/U6EOEGPfKZoKQEAvgOIZNQ0r/Z1fwcDceIesPfNBJ66fpiLr0bXwRcn
SBiavtnzienTZELlhaFsiEDZCrtdf5q7jBgY1BEqoGDKrt48mscYfqK4SvcU
wfm3nqravblzCg87Ct8TTijWX+YD+PbsDzIF9S/lozJrdKg25NMcZF0TalL3
LxWuNSQPF3HCf9rXnZnD886EdN9iYFpl8I1fG5+BXD7cD4cQHwmQkxEk9EQI
/yxDNypguyHS5YJ4PxjT2S/Wh8xXUxANn2JZph4nNN8W0tfMxu0jlKUg9frt
gDoK0IECgS9NTKQ7MnMvwFY4Jb8fehExZexCFPSyd3nypa4ST3h6VbD9+7iP
G7xl+rja4p77V6nzrPF/c6AsT0Usp1uks2C3kbXWH7tNlv/LLFwz3WmcOCrG
NuhldqtNqjdMOpEjpQzOjsM33Ax7YLuDA0jthHwkqEXgT5uxOR81G+P5Yqfc
y02Vu2+70zt2tpSTUh1blVWsI/J/6rewIEg9XQf5xthoGKfg/HD3SFIhCclE
cxY21i6ortusgr7gM1qYGZQLRrCIFRlLLhUTgso9/gDW0wLTYLRHoFWBclBr
ueraXtNvibxR5G2I8gYSiBgohUOp6DEjbKJkmKYmhBBfQirAfM6Rg8FXQ4bA
GaF5bNMUaB0yoHWmzhArNFiGu29xLurAQfsE0QhQlo1lmzBRoLEjUGQkVzgj
6LyRS9K+AxL8XaZzkVkn/dQiy1l+BMOsjQvKmPOh5oLntasSNpcXglvH5bmG
qIaEosbM+aGaGMkGzoHekPDfASktuultucsZsC7VAAXA9vWap4+EO8fw90gA
GbvSlhBQ+z4m1SY22yNFQLbgRvaHpqII7o3c0dDe3ICIa0Cekb/OC1oWln8n
5lS/h6dqPk8tiyaHDOg1g5o6hGslY2qcLDzGlB1BlIVZRBkN7Dhajlc7mJLy
Kw+aB5pUWaTA5miSEXB/RY+SESCqrAD+AnUBkjdBJ8VsK4djqBQAVoRG6kNE
tkbFTiiG0r5moQ9c3KtR7ZSrkPOfSbrTIsPxPwIth2BAmUCFoz3QTHoN/Bgo
Hsds+OC4+b6i2plPwpVMsZM3+w7DhJQ+Fxl7lHC6KfTn9Yv0G9jG0U6pftxt
Smqz6ldiYRrwL7uaflNF72r3m7W6xe7KtacizsscC1/YqQzRkcDaIyAr80V8
7YmLrrk8mJ00xd2tkxHiskHFQPy6DNDV13tXgqMyllUScScKgVh7lq6Ahmf4
hIhSbR7jXo/hfs7rMEUb60Qul2jhdDn3YUcSNR0M6Co4PdOXLW+PxQ0Ay8cq
Tw8wpNHxCt1jU93WIidUk3ROttV83FLxp/0s7Ad1v0L6TG+FMqzWhv4qT9CL
ljcMN9kBmqBZvYpQzlA0N2fKXSIXmEmS890Jes4OGrRzSel3fgmrcRZhTKGp
RZOWyb6EEWYxAD32yQWO9EsOYG6JTJLWCSAP2Z5SYRSTO4vdJc289WI4Gixc
exLTe6s1vI5FH4S29J08qSsuJkcAGItIYAVbVZ/Xb8jSM6NM7uMFVs0bcTc/
F30LxTHEULRSD9GiJhdI8GcF5zVWtUrvRDtdrpnFA0P1hg23mXvy+uaQWual
w2isXAUx8fCx6mLvavuIUmMEw8p/qIaAmZ7SlpyhXbhWyAzA/MkmEHLQ7VqM
RF4cnuhY+USmxxUzDDgGPOK+LlBvjL+i8LeFRQbPj4CSEtf+016WwFTFO9Rl
Krsx/7ZET7qpLSFYBnwYy0M8WBPkcBTQ6weea4MxUy5RfMyhHemAmd+RIJAp
q1Rwlw9yXT22zTo5l5+SlIWfjtss8b5FXHRBAN1VTL2PS8sgnIY/eYqbpyUl
f+qhK7ZIho25YZs2royeFkPLj2+Q2nf0T0xh9F5WYevi45p20N41u3Xa0vkr
k6oCqJo34Xw+jyoDLM9y61S3ylgut8TYptFkArh/3CduTX3AGHaUvlZfypwZ
o6NF3A4KZBG1tWKqrWHX8An4RxokYN5O1J7D26Z1heQ4klQsJzeLnyMxujmS
3+o4AfX2+DRyFen9up2DCJJl5DQ8WN2bNOOPM6wX/bb9/uZGxqq0vo3anFDc
58P1kIWmZTlLBrrdWY1Cm0e6Wz8lDvUojAIvDllKmOpUq+28CVC86xXiKo4n
K58iJe4TPzJzuRM2J90GoxhTU9+vmfOwtNwCvAkel3FUDPiDav6UEOr528qe
ib1n1OBibLdrexR4yUxnVcJpd1jgLe60pfjuG/Pi4GJrCDfinZKmriUtcroN
EwU21oGcLM+06/cRQNCo5hP5Glk9BKqdVLAyF67M1twE4f1uAitl5stzlwX8
agvTL1m8gCn1I2PJAra9AnHliVVMYbeMc2Ko6JSnAcJ0c91rlDEMVIP0KOJG
Z+IHSutmE2nXycfw9ySF08KRy2W4rZo9OZ3eALdlRIe7vRPy0Epy/Bpcgepf
cOJmVEjUTivmUKZwFwmuvAZGxE1Nz8u1y2BD8YKP7CunuXKavpa06Vn926lE
2WbSAEmbQRlXXiBhpPlgY5VvqYmduXRozwyR11vojLmDw52brv3Idi1u4Zh+
QtOIOKukPCcGOWTlIHmZjUHIZ1/m9QS3i4nWMWOeOaWcFBcM/zbplh2d3SLW
lBQN866+rj2J7T7jazjVx1HNtLTjY7+0+3ZcizSn4hMcnWMrteLYdqpSgyjC
PBsdi89DBUBxdZGbP1TlO1qnVsU3Z75+ByktUBiRTDVZ+E8uNYoZX6stnTUP
Iry3pqvX+P5kD7RUxXW9Xle019etonm8as+q1Azcg9IuLs2PH6sJELhZrzeM
WOm86HOIZe1GZp7Tims0tFqIbZjcD3reIGjcuFf3zki1HWeQjgsFxUnZlHgH
5415KpLmoY4K7+R8Mjs5RA3SstszCI+dRGXB58makjbMoqE9IIP7xqEhCc1q
3qc0wwlcyAY5CGUs3MdnvlHAcNLhrP0933sHe3qhFq/Ko4EtZ5VmE1pk203J
EIAtnk+2omvFvSm9FeqdT58yT//o/sVLFWENxgij194q8U4fCHkm2ZkYzy2k
Mowk33eh3I1lfhdYiQrtOFcWLglTnIL6qpkIOSpnNIdHmPMHj/A1x7KiNTqP
i3Mkgw2f0zqyC/yYZTvFtOmcurNw0vno6UNWN30imj6awRzmDCLFUGkJ0TIC
DVLE388o4YBDghVruSYCKvK0hst5Rmwzg52+hets/g73+X0LIEBuVvIM8N2E
8xrdTSKuMn5AHIH7zUN+kcc2bp5FLPoRPef9oS1HA0VL9IX5gWKFuVjoMDpA
ASFngdvcg+uKQ+lIyvLIDNdd+dBronuy8l/m4zGFsAlHHQ8zHlq6r6m/mGxK
da1NNQhvbnI3sbFITGaRh6PGCpVZghmASzc0xG1M/hsG98auiyNHM+aY/RPO
mpdcU0ZRilTFrKc7uABYC3IzULNiSpiPCz0kBVQc72HLZ/Z1MiapwNY3Zgxp
YqsnkWYTGdq0zOS7i07i0jkDMXlC5yEXHKg1woogVXwq0Wp68GXKW9AAyVTj
iWtWJnEA39Yy43Dw5DPP9VG7U3OKmgEvm6nkjiXeZqaDZ+NWGv/w+Fa56dtx
+C0aqFOl4TLjwizC1AcvKXlEEtTDpCCYauh5TE/FWm7dWfw6Qi3GX7C/+lZN
WHI4UmvCKoUQ6uYryEXrmWUOmnEy3IWephExmRoYYd2Pvh1F+YgQX2SY77z0
BMtKmTWr2M6HehU1Yf7GgRt0IyqQiEqRRTuo3tfrvYh9Xg+rSPDH/fp2gjsd
pYZHG1DDjarT9sHA4aoyUg+L0eVpYiuJQlG/LIGAWsSMQJ8GYuKdvpv2ul0/
MuAOPTAX2fonN8dLCrLytqs8N/7yOKWNYo68wYh4W9BAldsSyGHgH66Cwid0
1Uj1WWsMjGZgw0qyXtrAsy00UxT+uXW7SycAKOSO6ECDVkwduBeGDhwj9twz
nLktjEbpQTrEPSZf5ojq1dfm38794n/rd0cxoSG/O+Nv4K7wA1/tU0XprORL
cvgzRhYxJ9RaFedAxPk+g4lqNAEZQszBR+VKy71noRR6GH/UTDvgna74X1vL
p7u7sjRs1NGcGcnpaCt3rTYExGlx9avnz3WwX/G/P8NwVy/u+Jvnz5/D+YTB
fJoqYqI+KtZF5cXkMngQ0sJKZsQc83/GdCUnRUPypC4uUKRQBC6LXmowjBSt
d8MqkMUGFXieXXH+SFWV6tYk2ihHD7MnePqa8W4DAWi+aaGdlcACapGZxkQB
MUHdNblGOy25ElwzyVVsZ+Ojai7hbFRXJ3LKYo5T0idnyl5+fRUrjWpPee6e
gdsiK1QY7sKwdKBSf+QKJ61pDsYfLEcn5HB8ZMlgKnUEudF4lmW8JEzagqGe
3qMenmZd28KqcMg9AdeK7rNMyOSsSvm71lBy+1JlbBPruWHLWZzCc6+Uy7tn
9GMt22aZn8d8NGJ/g/JMwAUVcGihkh2Ql/4ieRv4gJubjOf8GhWGAg+j2kla
mAW6po5vV0dvSFflSfJ6eVJCA+Bgi+CCwpKMs7FFGt0Tzm94DovfGHDf1UhP
/tUKcRbhUMWewPwsVE8CjIj6caMhmQKKkj9mUJYBJsGcM8fejBnuMeZ4YK4q
nrM2zTKkkLCDf+NmkDQXk/LYes3NPbuIsA/QX6St3aSOzSKK7MVh3Rcyz8wV
J2xv6pPxBLHs4FLZGHPK9qmODW90RCs0PQAhsZCBCJmNFe+N9WOjDy5umo8e
PrjEcTVWouK1G5GmMuxDXW4xjjjlhU9jAR7tcnPgTiRSFNwxFkrXzNC6X8HQ
bpI3HV44xhWynDPY6GNQYGJTkeJj6elJ+bGaDi5sojX3ueyEfTt7yAdJ5b1Z
3KYw/JJ57Y8EPI+GOQ/jWwfe27mC9k+4j7OKumUwEeoaBXMrYVLL/yyHdsm0
0/0mFdDW3oXv9aKSMz3mmW6mYpgfS85C+IC2xJmEjmLhei0p7RNUFsSIinbr
IS+DWmswUpG1RjrBC2xP47qUJNqwJzFbJv/gk66taURQjl4LLE9z1Wf3MU5T
dhAy61Qll4ey8jymYBoaNe2FsV0TcRR7uyS8RyW3uPVFgqUWkyq/citu9yXq
mNnVpuE1P9143F6FdHXXtsjMDooz8nnprmsUaqR/CAuNFRjtaE1q5U8Fxbb0
5YPspIb5JrdlYQRjEmMmmN+bc2biHj4W6c1FixNtCjXMITHD09H6D0BiKq8C
FDfEtkDqqdH4hqah6LEP8Vm1z/XtrE4aoUMADs1qtWd/WDi6NJu2xanxbzBB
NGGC6p8M4ZIeGfewbsomtU0FV9NpbgCxy3i8Q5QYTFi4vEd3Uo/Mlwk8FGsz
u+NDkRCM4XjV0dr4TG/GLK2RGAgGDbILTyoif6hgIXEYOpEmkfb725jDg3QB
ZbjgYipdVJdlmObOlq9hGBM+dqpW77UKoqw1w+NS1WHha51iurWwZjswTWet
nhybLEEZ4SjCW6MPr6O7WeMOmfs5hPhHs9eynEM1SiIsT5gmUGwnGVbsCU7M
CilPAZ40jnlwhWZq4uYVPRN8SVUMh34ES2TQyIB5lTx8rfXY4X6ZwkdFwTvo
wxAMsbYt15WWvtcjMwCHq+k5CI9fS4EJZlRTsAz17R2yvRPewEqZOlASqZL5
IehfPQ8oi47NAKK8akf8cI5QB9tSLTOVMJhGRg2bM3j8GrPy/Q0m8LMCrCb5
vNpqcrKz78pRiZ91l8GICT3mKActx5fbQ0x9iZH0XlVLQD3ohY2tcWLhyhha
5F801JBCL5TSfvlG9ZpUyqFXXyzZH8lDXmgC2k+Y/OuHald4ew2m2hy8g1aa
mkxFC3koN+1tkFX01buq2pnXqcyQ0ik+dJLfUlbrcaOlRJLdJeQF1c/MAqLx
xeoFqGcpP9gXRHd4NPy6OkMi3MySEaL7L3MWbR1In22c0AevIhOlSUUUHH0V
u+mZcqa4wdglTrmZPY3b5KUbTA3hWw9lP7WCh3Qy6l7XJJxwJBBdjCNsehJd
RzzFWTHad3wxGKVE0ruL2BbrZwmsruK8dzYzV9GsGwSLMjyGg7+kBmdxz7yc
SoKmZS4l+mfhGp8r0aHH5nUp0vpK9ez2gxeaqcZx9TC53bk1l+1smddvO9hF
rcmHqvxdu+vqWJ3EDZ0IiEJZ+axmezG1EWmO50biDMj+G8sgyawm7/uScWkz
w5kfOuFiFGcGDzdk06ypPk0WTwneV0fqJPziMyvb5bI6q9bAOo1HX3xxlaLu
7GA2xFJabHleFld4JlawTZLhytj3VVTc080dRmCEDCVida4M7l2gM/yPbFFG
FsEUXW0Eq3VGplSWzUUJ7EpWHqsCwxWslWy5WW/yknPMJbVs1qpZWwG5PAVW
c1o1QXma067+gu1Wzsh/PZPkPkqo5Qj+jw+Yj9fdmhkra8WSIbP7cRFAm86j
Z/PkKcTDgbhgUri1WE71QL2XspVCZ3ufO+y8X0bH7rvfpKMKqc7trI9EYepj
PicIECACZGtPk4g3b7H3lnGPUTnMvjuqKswE/ViXdBOxIlZxpu0OPGhpQ1RL
j2nQgBRDEQLPTjWxU0Ka8q1Y/caU9qHShIOtcASkz+FLhnO2/TracO3KZEgk
rmyDDyEVvrKZdMNM20Sagh3xyM93mAjCUn/7zcYgzQ3j8mVy/KLc7Q/4iz61
MBijIu/V9DQ2kxUAm4VR8qLPQnB7eqoPBz4GUEd14wOI+mlEqu3yDExr1zPn
07DePXICalvxAL4euzHH26ouzXWh1rd3sBVWPHVlXqEu8ZXLEFgUBx5JCwsl
d8tVpu3qBui0jCBnRvDYcJZL4NWt3B1IJGeG6LqyB1WCjEt+Z6j2lGOTUuBn
vGUvcRKD4wWumnYZYZW9jZad6hjz0GUGkacFXB28Dl/YBwBL8e77bDZ8cUx9
J3bhGo3L5H3ORqfObrpoOKXmsndpY6W6tQbgpr5oRW5mB5NAKC4hk1/ZSvWR
mLK+NRYjmuyqSejeULexSNcp8WDocaXx12z+0SoVWsAydEffi6RcxPqY48pV
BjV5sumxph8/mvvNIEUQ9B+WwQegLUyuyBPR+ky9bpnPKyW4j0AgWb2UHJ+E
nYWv52ZCerkaP2MrwiD/3gA8XqDTNJa8FskiekHVAdonr3msAsSqvZoWGheW
Ila6tNrgIzFHLrUsSZdHNQVfAlj0U6Dn29uuQpL/gdPPv2hNgFJbREzHyfM0
p+JxeNm8mzHagR3Wl6zVIoRJfGWSvWDF4kqk6q4w61t6H4XBMQFQFEExPyor
4RKjB6qNZhqtlc0eWgbdCL/IVAoHJ2ZbRyucLgOhbqChPKCdp8DHUA+5b14h
LCUtiqm63VYD0//YgOm60pKIVqMkVRnQDfIeHKrAWZAn1djzOo/ZzTDKxN1F
5RIGoOUdMWK1DYdVbzT6x0Z7uS4u3rVIrQIw02VdF5KpfKoOZZrhlIAXOVjz
02TEcZnWrotqjxYaF+VDc/mohhjyVE8C3zL7DLVO3e7IdsRbjcRWyzg3dKWr
NaFK4ZymDGbO4XKDHx7ht1QGr+EAhQjnhTxiY6neLMVZNdNL7ox3yUL279Mq
UbxqXu9LPgl4a6abFGvlazU73wr3MGguPWs2rrp6p+EASy6IX9E1JcrXdJXi
aNxwPnA4ruL7NHrX7Tk2nF1rJQImlKc+HZmZC1A5+xcoW9DauqLKY8NEbRxi
lY8st8pMhOsqIaJRX3bUlMBQ4IYLemmZQXVqm5v3mVdtdb6n/RA2wsqH5F+y
3UFqIbiONQ8gDNUKzMeu9qlGHwsre8EVE/XRMa1l4mJYlYGLJ0KEzpby+tt5
lqPGN9h/dFLn9uHu8SRCpazSS/T2QMSloFHzzrthhtETZ9MSbV4dbTxQygRO
uGi6nQx8e70/nmbqkZIMjkW0niswhGROtdDMe63uvFjAs4+Y5DzpXJWpkBLG
Zmt+zM3ueN5r8PofpgNQwfLMsL89ShbGUbKzJlRlt6n5wL1mkEIhsijRtmZE
N6F8tHPsexRimlcWTmIxNQWyUljENE2YOHp47Gas2prT9lHnPDznm/IawPx9
1vLM+mAJd+josEMSszajXlh6hnaq1sSMcqUgk7A6XgpYVQh8ZOrLtALQqgzH
nTkpXhGxw9jTPYKwt2VinmNvGOEz793DpIIilk4z6KB2aphp3m1xDq2GpVi8
VNvMKnWZIWIZ2DFeOHLSKqQM2M6T4qJV1cw2smOXyi7q65uNiHG5izk0ePRK
bF2UUX50O2lPtTOXccHCCV5/O56x/t5y3dgRIGcPIhHa2YDL2R8UX+BaYayn
NqFqKkja6CGG4F8Ww3yTITXGLX+XTuccu85dyx7O8nV594R99BpKPlbvpO6j
BzsBK2+7EqJPcwDPxylj8my7ubcM5oRYiEVK0sU7jZaSZ0AT1E9RHhJCWcsl
o/eGfLXWsjuYSlfkLdGtE3leJULTFrIBbmrksFnP5snp6M7TNbvXrrqeKlVa
A9JgZoxHKgF+HlQBQOv1Q8tDG7FHEziZHi9D1lCKsd0K7otHL2KmFXpUmTNa
y0plkhJCZh5YNnXsXZ/h1qzcTayDHbsrrWJnslSg13oqqdKszlACdztLVbNi
bhSM4cY6YU/awGWGrqzeajztRG3xUox5dqMmXSUM5Uy71GnRyYigQCEhVYKX
sRZ3rpu6NzA2EXTB/nLSiUBf13rNbz9Ma/rpI1XeQmBSQtY4fNSKQs+D1dW1
/si0zZZH2MJcsy7l9ubctcZ2dEVHRTW1toBH72gDgay++Pt6dn1Ix67xSFnj
rmy+wVVdfWi67uNbq4NcvDq/vEz5Y6nmvToKTK6qIdnXBhTSzsQgtfWSV2jT
3lqAUn4i/WoDN6utoHp5QnZnNgntBIg7tBu3qG1u/NKiS4fO4pTyNrpgIlLp
xVThHh/p4Zm33vwJf9rXFVz5XUW89YkuPZp31ldJ2QXLxatPVovKsyeFBZgG
L0m/iokAI3FhAzVtrD+TWqihAk2zumsTZlt+gz2zq5ikUOxXEg76lRBGm3ee
8qhNEZPw7S5YkoLi8YJWBSX+PO3UqDuiv16JNrORM+RNvbBCnAxSyEcdMy1X
00t0hnAxKeO5sWC+dsnbjjGI45vhDpBRHeeYfFRlbWZTn76T4l958KMEZiUz
JndRvafsiXOCwmX1XVJxbu+47aDvKQdTB8l+R2EVPaHeUZlG/mGbyxnPdiHH
3/ReNJVWMyWWAxhMPTkZs8XMdDWr0aeiAgXLMcZcg9a9F1Fe7X2yCSj8CvHe
blQ3p384qzanOMHEU+rcrqr7pBLLuBDfpXXaGyWS+9esn8KoIv6utMY9kwQK
hJhwL+UoUivLvBVxlNOuG3k3Df8923x4BeCmdrfXidXRnq99S9GKs/OzjzWj
tFRSDEfI/O5YVjMpPRrwn+TeQRdY4jiVFMyf6NWe2bStZ+zbjEBrdKb9lrIi
xDFHsVrnQRNWfey1racod7gJsTL7Taex00ev5KZ4Bm1borXx7jBgZ9/GMKh1
HGv5rtre7mbcrQMSlX0S1Rd8+6t5N7+ZZTqCG04eGnlfJTnCCsdVdZPgPB8s
zyki2ZxwiRGHNnsIdquzrtiKicOqrYAXLJAHsLQ5S3ql9UPb7poHYIZbVkGM
bvJyvR5hU3jqSl9wHkADOmjGfTm6Sew0m0wMVKqevU6pn8lhvsWkkbd8nzuR
XE0jcL0VZCV5RFvyUkuGpfICsf86huqzsucWf22MaXpHngTbshBjpF+r/k4n
NpxzbAU8dQ+am6Ue+qxJfWw8m8UpM1+n9orZO9X6cJUP5l68FU/rPbx1hD6Q
7YleFq9VQU/0oU8uzzoTE3lIbxhqe9P2MfnA+jGWt6LwgYZOY1syxXtai7FP
cr/4y2P5TdZ7Db3wAGFuYtswetcQ4tPyIOM/2wVtd6WsVa+CTlQG2lRDurwQ
BC1h6p1eiETCIvBdqeGRIhMPf+7g2OFtv9Aubpk31hOluphrUmXObtXGqAa+
xHC8pU15a5kqXQUrTPXPMgbSY5YNXaGm743nYrR4C92mUQ+XKmJDBgnyh9f5
GPdtvXaZr9dkoP9DVc5xLr0bWkJz8mqsrdxaFx9kzxex45P1Uo2V/qMhlbvb
taRmdCrGchx6jdTdy82jGjaOB1imVhxX45vblujbFfEn2mRCrcbrqnJ2tVZf
FvvRbdBlECofXNO43wxoyXMmrjZw7ZpB2Pufo65rUQXlK+NSc+pCjqU3fC41
M4pivWITjDCkJyZSyuuxm1WraySD/FdzBmo4UO9mlCNYJ9a5svAI2a1sa8f9
yFVB1Q3QWQK6VsJGyT6WG9d99LzgmszAToug/skMEPSnPXz2w6PpPv5PRbrG
Ok95qytOEZa+goSJjLfMd6qWEVJU95GO9BkNRCGUeW9ElNBKMaBIFV+B8NoA
kqq6S4F4BAiSlpvZFAnEtEqyoTEFx7WVVuVFgUgM72m6mYJkvWsCLczSLLEH
kSh3+k/tv4WXKIcVuMpDJCIzxIYd0d0BKkT6ATAsVh0PdQAH8+HnZqmroFpe
jIaFedZ/LOl1iinguS2oWhs6Pp7T4xDlT4WGeiAe4n3Y1KlVTZtY5NwIO6xQ
5AyjP7rNoG6QVyrwFTc5lXMy/hOcAsy4JoYPOJ1K8bQkH89Gqn4crExCadfN
UqDgXwq35c7rkvXx8kaw/sirguVHiTANU4dRmLoe7JBwYo3WmDL0tWpssjnL
il3tvXlHBMX3qU2LsxUFKIL+31U7usV7OSE6zYaS5QcREwqplYDwzr0iyJXX
yqnX97moikqCeSlrzf4W5tPIB4NohCSxuokeIp4v0AixHJJ7U7SQpwcgtE4t
NV1Cb9yhasH8WM8emabcXU3WHbXqKm19IZIAzXowoI2FyUfEVnVLK4+7xv94
sGLs1PBSn5kbOfEJW509YflIhurNY+DliClbuFvbi/exfa5CEJiGzLNwNhaM
O8+hI+kmVhivkiykF5HrkMMjn2fAp+/UaqS487S7SaS79F5sjnZDnFwbplu+
n0ia8iT1bOO8NcDb3rBz7GrYM5iM7Bk6Ur5He6HV1I8SgknO1Ol26vCx7juF
J4GeZF0qeX9SEyTtzepCw0JC2gNO63h6700YH00lnPuYL9OxLk80GqbzmiYY
e6Gq78Dfs27dhXc3ZY6GIZxED9W+H6r2mqp7Ev6FvcDzJyfdnlKPp2l/p9TJ
ug9pXkjAVxHldKnLeWB3T1468+o1ai5GORy+GrmrWGC1Yny8spxQhAqrBtf4
XtUEpFjk3jeUkWGmmuVMqFVoTX8n7aQ0E89tC3Nugi8Hb+BXakfYXm2ywhTI
4vzsu7MDijq8vDQxxkiFG8bFGdUrhsdd1mQDDRyY/2XP2Hu1Hmcaw/tCqS/9
11/+8kv40u2JR4+syV25GJWTeeuJ12XekN6aNb/47NeerfdtnNqpV6NnXsG4
uejSTdh/80cglcOlPE86ACQue01Mlv31kP/x6XHiLNHab4toU4+XvtMs/zc7
iyvP/vW119ZZjQ4GT3x5XQ8v4ZKFKfH7y6+XXzIdQ8MCTzTCTr1jYUlMGmHn
fa5lne6wPfz6RVWNGg7yOz/9lJojWyzEvzbToFw+b1c7hHNIX+rP17RnZ754
PtJW3C5vY4Rce1NjhegIZlVh8poxaoB5Cbjw/d7rTo5qFCn+MaP6hS4rclXu
zFkiB5vJvo+OzUhsMtT3SrrWy0hvhmmY9qLJTDk0DWqNuCs8BSPiQtuUrrxV
CFQC3x9ulxHQ2Vqj1CzoE0dh/aEKUEaq/kIBpbG81E5Or0tDDeHb8rZemZby
Sf+p/Vom93VN1+QA9tU26U/yxgp+nf5OlWVeFyHlKns7fC+0biFI2IIbuMA6
c6LTaLO6/I58mSwAJIjjPmPRnf7j4kxfh3dbg9UxS8jP0iiNGLB9DxCpjIOM
kDff4Z6CNZnBguiyP+Bbye/8/V9+pbnM5jXfVBzq/PXl10/yqCM5UX8zj3p6
nP8v8ahJwZAPYj5PpXs9kbWWZYEhE+AXn8VfTdqw/I38KHv1b2FGKfA7x4jM
65FiVxafsGIQrvcWVP3/fzb0/042NFHiz2weprg9ysShJhIx8k7xItTxKhbQ
f4jPFaL6wjR+Nj/es0BPEN549lUyJdxkeMaSFLsTbEamaKoayJXPq4GfZJrf
p9O3Af1BswJe52R9FJ/smxr+67OLV+fnsqB3VfPpS0OQke+9TFYGD65mU2vs
H1T60xD+PBrvz0LS8V3511t/ufizPLmVfeMviQyA24pOYLtjtCmsdjAfgANK
SO7P71NJOLZsAWgVozNi5IN/2NtcOVSoo7PrvRw6ykJ84KDuAf1zccGQYfM3
zop5f39W3xANLkL3vC8eEwKVfhjdjLqS/OtDxgfFH8PPvHEs9N9N+0dGDj7y
syJPif9/5CK8ybPA/u+4CaMB33cVNOFCT/d8vumYN0uLbvL5pmOTXPl+7vQn
6GxM4Rii3eb0gX2x9Lk3H1yi+u/ujPVBfbE+cOlPAohljPc0zhqt+WjzrLRr
WcesD5xgDLZn9PFkS63HmWqBDKLPfy+vGM8PjqCg9tX/sQZaH7bQCfBHPzyf
6Jpw2BHegTp8jtvwxIdPj3zZdUZyvolBTaTfHmCs+cJHIfwDh3TNou4ti8bP
w+oE7aDGGj/S+LBwogVcToFM6YvffP6ZaK3/oB0aJiEINvMTWRMhDZbRYiVM
X4kC2dX7bWwN/AnsnwtymEXx7fllIZ8GLHNRXP2HlT28LGsxojrAo0VC77ba
HQCBAZFNQCSiACebQPU1Tvq3+81j8dnzz36tsZcIiVPHBbzcKoggyaNvv9ek
I1niEV8Q/CEY7ipOK2YPXQF8vklb0YcDMnFW833bD3LyF//yu7zwKjavhzWz
YBIL3fFeQ/2UcadbIRAUsNWcdpQXpqKvpZBYclWdl+SwWhpWw7MWz+P8YMQo
qlpjhb6NzGJ3eIRnyuzK1Tu05BI+ooWs1R1Jz+W+AfQ99vVBNM6DnrMAb5op
Jzh97iuxiqIkh3shRVgv7OLt/YXil60ZGEPEWlX2ISu+nSFjjGZpej0/+ezk
l1+m2Z+zJEWItcNj6MaeiDdsAoF88F72ChDwr4aWCBkPgFvKjCvpfrX2O1yt
5fPPYx4D7EweghbZKddB79wOUQLsDRuLousA0yQRXpC/ptrECnJYw0es0bRg
VX3sJme97SeTUQJwyFZt9VNqj9nco8WAfwB6mdEjDRViKWxHByejaltPQDYJ
YXwzYVOy808Uk1koJPlmU96O4K6YMGuwsEw6OaiWkdMmH1o0PibgHt7HXzw/
eXHlwySL3d5IZTGEyVh9BpRRsPIF8qMmiFuSvGVVZwB6FaCISgXFjZwrbfVT
4XLYQzdPuuaGoqpdiJWwtdqzEf51dVfe1yh4l4g/9jxqNc/0pv4RqvDpbHsj
72wUYqd6gl6yPujO8kv49pcsrhcb/bS3WiaF1xIcVqzmrkyhqXjqMt1l8cO4
QsaiiJvM+gpW4SPVtY5IjyaegYG88roVWa/x460EvVw7412JFmVhrFWiZHmk
pyQ51pF1qVLk7+f9XscQPzRYVK91RmvxtngZJ9mb+BoyfmdqvZVp90YVSC2e
ajdMXj7Qfkwy4coIGe/2g90RL7bJZLkDjFJJCOpQ3bZdnvS0iLXcRCHT0nvX
+xoFoxzmh4W9NESifi6WWprpN+YmUsq2GHEI68xrKB4m4qNSzrUwICOruC92
AkypT7W5VGJOy8kvDGkSay1UWy63MyTAXGWGCHwaImc4iR+6sjIzc+VWyCjs
BS28rsK3H1dh8QWNOgkksprW+vTyqOORj80ihuyYIRq/P6lLMimunHoiA4C1
B7REW1EphPY9E2Yz5LkZR5OYc7GwJad9vNPl5YENWDCD01ugJDvBWoohFJRw
PSB0zPdsrjmssZDsio2Ky9v4W/yOxVqZy08wpRem1f7iH1gV/uVhdwOjPQM/
aCcCQgu1bACXFNu9TJsZhPDPUP9coXvTWJ5pvIyaNz5QQ+ide+zgTRrUjZwl
rlkE2itRlYVJJ+UA9leCZFicJopeiJzdvtu1vSYSxA9qGwGez1An/7uo0Stm
f+semUzC7Tag6RjYoLBTJO2+054uG+vkbhCMrNZ0OelJwlKWUe/EfmGHODXI
TIVlC8HHnKPO5qR4ZmtgqJtprVW8vwOgzJoFKMe3odvdApbyn3plXawvVUEv
8vrQ65ESZg0K5DdDq2U91OOlZC+KYoi6pLIo7VYx7WNnB4N6052VMmscJK8P
BD6gZanNubIuH3vTL9+nV37XZlh0AgVvvFbVNsNaWzkOlboxFamK6DIjSZUN
wTVWWeavksoc/QqpDjegIf0edhxQOUiaIvjPIZtjpfb3jUg4ywK3B7V0wlrb
15X1eqEavwqfVbRng0qZrAkQtrIeRtYFc7R12Ia5PE0/VvEdZ8dcTi1AXUdk
bFTdhJJGKdv3VULNE5oJC9arNIkRRA1Nds+UdtXucMG0oMgUDmTtK1JOPW51
BSOLOU86GXXW8lOpoSdxQcjbK7tMQA8pddEAal7TPzK6vPUXB6nQ6l714sgM
jX3vm0nfO6+jRgMSakjqpESoXWrwnVcJEd2ta7k1WfF/L6dq5GTauaUlHOD0
IB96RMoec8ibbyotbB42a6SW3XqJO7FO1OoAMPB882IT9L0ZpVOkcbLiQSuV
pOHSsZKFAvnAPUuRPkp3owPwCrAy7G1X7u6Uck6Kr5Hb6MKqNk+lsrf45QWu
2cexg0teT94bhsMeJofQJpas9rDuyptYJ/y6suwFsG/bgeXzX+fw4ZH9iesq
K92gbnPh10aR5rpiawMQt9EWqjfRNiPr146KXPBLoKuEboWbr1vKG90yTw7S
Nju4CApcWbhbJGf5lGXq7rrRnpSX8axY6xhLShZXznfzGrVeAlfuUR+TIZw7
xvNisWzVwG9bI5MInHYgp98OXxqLoT8AsdzANcKE/r1JwFfetcKY9XUJUn3T
eZ4cKdwOSm8vkCpwSIf4DtgY1iFsAZFc6iGjw/fMz8brxm0zRK9c/HVX3zjE
kcVKomvSChTUNzdyEN/CoKS7iqLove6aX5584b4YHUn9DYsQIWg8pAQz33tv
Ohw52+nEkYm5vrfawjq0l+5PCoIbBlUskXDgrbMa/NReDTIbG7L8Pe0ITlWd
y4wxG/2w6aBQwfL5F27zrUcpLtF5xgI0TJKod668lEOw2jA7tiCd68OgGuV7
Os43dirB/aJzcQx0tjWPg/osa+8/mVp/cuesPW9InVFL7TQ17o8KdrGxKgwk
Ytyv1K3wn1S50K3z1rPKQhvb2LwS27gv5tgHoyle040/cVMzduF4sUjRGfOp
rETetVvHXkB96fpFiL9d5L/W0rpZ91j4IOKjS32q+GNbqz3DW9cEf7meNMrQ
p31VeVPKr1vWQUmq/uEN8Kyyw1r5Ovr148CsqcDIFP0PvNH9qAKXo7pjN0dN
wfb0NmPGTK3WXJFKC+HJ2DuEou+Y45H+5HX43zSeGjMOizAXAwmuljIox//Z
c40Za5M06BETX8PC5NPYxXBb31u5Hg/rTMuTkslrggomedMpuFn0mtj+TklP
6Ob5yfPnz1/QP5giZsL2xXzU7oITYzl2n0fkT69XOt2Q/HayPR9SVykrpusl
v1LP4TC+U9qzzqN2M07CWYLWM4yxPpgk6bENi93EujvIbQDTYUNdvk7FWe1g
49zWFPaAh1GNymX0BOei2mtqT2/VWkdWb/TsNhbdUSqLHULGdcYuo8/aEBoH
ZWo9F2Lbmrk6KuwT6NE7Tn4uN7KAn7pTzfzKaskFbdmiBDPh1NkaJl7x4MVK
U/+RfhLWcNvrweuH5Aqv5Z2sg+2i67wp4GnapN7wrNqNp4gNvF8e+UGnmC1m
r/24Yx5ZqUX49mqjYVyuZlLNLaOGoNSAc2QiXyzfIxNlRi2CLp7zTFVKrcXK
0bem7RyEl+1LHN1CLz0+MaRPqKKGEj4EMr+e1EPrDyBYXm4UKR7etaQcJpGv
oDEgKDOfvViM4kDeqWNcxqcvnlmp+2fR5dGtg+ZHwfZ5f9l7j3Z5xwe3GKtp
vyz5LSf2mSc8jH0xNdT9X067zdJPqvTBBz4f9+8x38ZCc2gBYrNA1eTb5IOY
WpSudOkhm241jNx8K1Gyo/PNWnSNqwDmoQyvTXEQy0g1/p6of6jlRq18oVys
nsHDS69o35VMCRZTEWRRPeDQZYs8VqoZy1sje1zSeBSx9cU6xiJHp8Nz+MI1
7WhSmU0Y86/X+cJj7icK04q90sPHY9ZsPA+DyTP3n/eB1VSB3lx6ty61B0P0
6wMDFR1fl4fBXDawsm+kJlNs1R6yFlYMGR90bbKGVmZiIgFS2+yUw4luwpfB
kD8RSPMhfaZGGVqHjatcu4/qn7W0RnUFCE3aKPOXhKarcJ3YkMoD8AiLmJI/
9cYwwRkW76r0HN1ZglESubyroqiMz6PE1hoSs2Rubnr9cEeil4gW+KYVzsl8
oNSE9zy1tH0ovZivZ7Eijc4yNcGSOjJLyx72PFHOLkTPhNiVFGvussikjXr7
8rKPXqvvsTKjXlN6fbs+7rX8BMbySAI98EhKdamV0t5H/oY+qC3vauc6xo0b
fHlykrZIJvojn5zvBr9ZdF3I8ht15i6XS9rXANio3W3Z9WKWhZ9O3XP8757R
hfLsfwxWAxTNK/OvU5dLxfZd4cn8ozkj9kBabrYiq/WweVjs/Zr0FHUNeRXR
4RhmzRqqMs+NWrgWsp4okVRQTAe1koKnsSjuw5Pd0PR0c3t3JmB10O2RV+mL
WXs62ReoQPr6R68WzDaoSCH2AZ4QBUN7AO3LdyhY6Bj7CtenFsHTJ0ZfONIH
MWYuBKcYj4icaK22NeshHGl0kXYYFsA1WiYNhGZFY7y/817yetNpMnqylVjo
Ratp5v8ymrsKd/O0mxC2oIfjo0gBDq+036WWpMR3aVgpbybXtIEGVF7y7cmq
tXETnmrhpzYXfEzRveQ1mNTm1c3OjeFwtkLlk021vq20+hblj2zTbd2/K7v1
898wiTI9ZkiuuRtPNpYa3FoBEGwYZRfL7CdEQfIedhYAaB/IdoLep1G9grLX
IhyyUcSqFmhJiiBOf3fdyjRVU3H4MqFX7JkVzoWsiovVXYc+4io1cg/28vln
T2kr32R9z9YBvotYGL/XiOODF1o4osAmPXSdN6DQvmDjhBRrIhXFKoc9lnxs
2dk0v8aPjG3HvLR5rClgMU2KfPbwGuleUHKP97Oacwtq8vWN+uG1lwO5d6p3
Gy+T7dUkpG3qzyN70JchNnGOatdbnhwORmaXRdLtRLvRPpee0hJ2bd1o9Yvz
1OaGZk+Kk3JaWbkOVozNcE3aXM0bchO3M/VOWhdRYipGwYHPU78yIinQWo5p
8KjiU+x3CwpFxTGE8EO5gbfnm/LhXd30KUw3IamptvNNFo8MURyqKsc5ZFEX
73lnuq5G4YkzZHyIAJfgJkYsCm6R7YklkkEjvIad9/ulBEOBR8R/9fMHgDtv
51CvqNVEK1ijtBYb6UNOzmyxSK9gz2WzVnkEf0WVoN9fL6MCyerTQQOaoCnY
BUyhGhcmiE0VrKKuHNp9lbToh7vHQ/SqKO50eNyIjtm5HyWBkozU7ZYneL+1
Hq9mSys4N+qtRY5GiDYwMDsvxQGjUsjlt221Kb6B6g9cT5fdkM+P87SFcUl4
WGgaBUPXYT8B6+L9sVBR5RmQUyDAQeMaAE8Y/QGpKAsboxG0WKDabuvWSsnk
xbQvj+H+Do0VilPXcVWrXLW72izrR+vhEAy8xNT+Y+RSqrx0neO2ZbV9D03h
QpERuByLMeVR6NOJWote68D07jFYbHVflYiUI88C1LPUNkAC1Eq2VQaq2nmc
N4Rvqqari4u6e/euvC/LrhzxwOFu3IORm3jYF8NBIalWiRfh6dX7MC1JpEU5
vSQRWb65GHLx5YAy6LvT8jpFKq/zTWUYuoF1h3Fj+Uu12aPBq7ajSNd7YzSm
Gewby9sS9u3o31jwjAV1lIxHkbDMzsLdGzNT78AUZZZZu39HxZuQVbwpZive
XGpyS9e1EGB5lkptdbXVRv0YIZROP1h6Fx2lBczIi3vVfUKP0IBwF63M5VoM
uchaxpVpLieEQp6jhZTWQn/FHwDKWsm9fdcm/YmSrU9MEy4S85Y8tN079Z9l
ihNs+6q5RSiJ+DMUBYnVmxpRYRvdlvsYQzb7Kx4WKoVsqYFcywxXiMaUd4Y0
QY20oVrdNcJsNoXJ/G+syDkEBoSw92bEQA1UVPVRnl18tby4fP3i+fPikwsQ
gyr/l3G4180trtSntr4wni0tepZj2SftgxoFy6pZt55ojzOiPNC/8MBdqW5u
KI8vs/j/0raKTjfqY19EHUvjhOrjof7+fwECJTnBj/IAAA==

-->

</rfc>
