<?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.43 (Ruby 3.4.10) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-morrison-identity-attributed-commits-05" category="info" version="3">
  <!-- xml2rfc v2v3 conversion 3.32.0 -->
  <front>
    <title abbrev="Identity-Attributed Commits">Identity-Attributed Git Commits via Tier-Structured Trailers</title>
    <seriesInfo name="Internet-Draft" value="draft-morrison-identity-attributed-commits-05"/>
    <author fullname="Blake Morrison">
      <organization>Alter Meridian Pty Ltd</organization>
      <address>
        <email>blake@truealter.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="18"/>
    <abstract>
      

<t>This document defines a git commit trailer grammar for
identity-attributed contributions using the <tt>~handle</tt> identity
primitive defined in the MCP DNS discovery draft.  The grammar binds sovereign actors,
automated bots, and AI instruments to specific commits via three
tier-structured trailers (<tt>Acted-By</tt>, <tt>Executed-By</tt>, <tt>Drafted-With</tt>)
and three optional cryptographic trailers (<tt>Identity-Signature</tt>,
<tt>Identity-Key-Id</tt>, <tt>Identity-Anchor</tt>).  The signature is computed
with Ed25519 over the commit's patch identifier, the value
<tt>git patch-id</tt> derives from the change the commit makes, under a
fixed domain-separation prefix.  The signed value therefore depends
on the change alone, and the resulting tree and the commit hash do
not enter it.  A commit that
carries the same change keeps a verifying signature across rebase
onto an unrelated base, cherry-pick, and message amendment.  A
merge commit carries no signature, and a squash is a new change
signed by whoever squashed it.  Conformant parsers reject cross-tier category
errors (e.g., an Instrument-tier handle in an <tt>Acted-By</tt> slot) as
malformed.  The mechanism is provider-neutral.  It depends only on
DNS and the <tt>~handle</tt> resolution algorithm of that draft and needs
no central authority or verification service run by a platform.</t>
    </abstract>
  </front>
  <middle>
    

<section anchor="introduction">
      <name>Introduction</name>
      <section anchor="problem-statement">
        <name>Problem Statement</name>
        <t>Source-control workflows now produce commits whose authorship is
shared between human contributors, automated bots, and AI
instruments operating under varying degrees of delegation.  Each of
the existing mechanisms for attaching identity to a commit covers
only part of this mix:</t>
        <ul spacing="normal">
          <li>
            <t><strong>Git Signed-off-by <xref target="DCO"/>.</strong>  A legal attestation of contribution
rights under the Developer Certificate of Origin.  It carries no
cryptographic proof of identity or tier, and nothing in it
resolves to a verifiable key.  A <tt>Signed-off-by:</tt> line is
whatever the committer types.</t>
          </li>
          <li>
            <t><strong>Git commit signing (<tt>git commit -S</tt>).</strong>  Cryptographically
binding, but each hosting platform keeps its own key directory,
as GitHub does for uploaded GPG keys and GitLab for SSH keys.  No key
path resolves through DNS, and no canonical mapping leads from an
identity to its key.</t>
          </li>
          <li>
            <t><strong>Sigstore / gitsign <xref target="GITSIGN"/>.</strong>  A keyless signing path using
short-lived certificates issued from OIDC identity tokens and
recorded in the Rekor transparency log.  The cryptography is
sound, but the identity layer is bound to the operator of the
OIDC provider.  Migrating between providers re-roots identity.
No tier structure exists for non-sovereign signers.</t>
          </li>
          <li>
            <t><strong>The <tt>Co-Authored-By:</tt> trailer <xref target="GH-COAUTHOR"/>.</strong>  A plain-text
trailer that names a co-author by name and email address, and that
AI tools commonly use to name a model.  Its value has
no resolution path to an identity record or to a key, and nothing
in it distinguishes a person from a tool.</t>
          </li>
        </ul>
        <t>None of the above binds identity to a commit through DNS,
independently of any provider, with a separate tier for each of the
people, bots and AI tools that now commonly contribute to one
codebase.</t>
        <t>Attribution rests on the chain of signed attestations a commit
carries, and a copy of the same content does not carry that chain
(<xref target="MORRISON-IFT"/>, Section 6.5).</t>
      </section>
      <section anchor="design-goals">
        <name>Design Goals</name>
        <t>This document defines a trailer grammar with the following goals:</t>
        <ol spacing="normal" type="1"><li>
            <t><strong>Provider-neutral.</strong>  No dependency on any specific identity
provider, certificate authority, or transparency log operator.</t>
          </li>
          <li>
            <t><strong>DNS-resolvable.</strong>  Public key material is reached through the
<tt>_alter</tt> DNS TXT <xref target="RFC1035"/> record of <xref target="MCPDNS"/>, under a zone
associated with the handle as <xref target="ALTER-URI"/> Section 3.4 describes.</t>
          </li>
          <li>
            <t><strong>Tier-structured.</strong>  Three distinct trailer slots correspond to
three distinct identity tiers: Sovereign (humans and
organisations with cryptographic agency), Bot (autonomous
agents under scoped delegation), and Instrument (AI models and
tool classes that lack keys).  Each slot accepts only handles
from its corresponding tier.</t>
          </li>
          <li>
            <t><strong>Cryptographically verifiable at the sovereign layer.</strong>
Sovereign attribution is bound by an Ed25519 signature whose
public key is reachable from DNS without prior trust
establishment.</t>
          </li>
          <li>
            <t><strong>Category-safe against misattribution.</strong>  Conformant parsers
reject cross-tier handle placement (e.g., an Instrument handle
in an <tt>Acted-By</tt> slot) as a grammar violation at parse time,
before any policy applies.</t>
          </li>
        </ol>
      </section>
      <section anchor="scope">
        <name>Scope</name>
        <t>This document specifies:</t>
        <ul spacing="normal">
          <li>
            <t>The trailer grammar in ABNF <xref target="RFC5234"/>.</t>
          </li>
          <li>
            <t>Multiplicity, placement, and ordering rules.</t>
          </li>
          <li>
            <t>The Ed25519 signature algorithm over the commit's patch identifier.</t>
          </li>
          <li>
            <t>Verifier behaviour for accepting, rejecting, and surfacing
attribution states.</t>
          </li>
          <li>
            <t>Security considerations specific to the trailer mechanism.</t>
          </li>
        </ul>
        <t>This document does NOT specify:</t>
        <ul spacing="normal">
          <li>
            <t>The <tt>~handle</tt> identity primitive itself.  This is defined by
<xref target="MCPDNS"/> and incorporated here by reference.</t>
          </li>
          <li>
            <t>Background to the tier taxonomy beyond what Section 3 of this
document states.</t>
          </li>
          <li>
            <t>A vouch, the statement by a person that they stand behind a
contribution.  A vouch is a stance toward a contribution and is
not an identity tier.  Section 3 gives it no tier, and no trailer
here carries it.</t>
          </li>
          <li>
            <t>Sovereign key custody, derivation, and recovery.  These are out
of scope for this document; implementations are expected to
apply standard hardware-backed-key custody practice as
summarised in Section 9.7.</t>
          </li>
          <li>
            <t>The IdentityLog transparency-log mechanism backing the optional
<tt>Identity-Anchor</tt> trailer.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="terminology">
      <name>Terminology</name>
      <section anchor="requirements-language">
        <name>Requirements Language</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
        

</section>
      <section anchor="definitions">
        <name>Definitions</name>
        <dl>
          <dt>Handle</dt>
          <dd>
            <t>A <tt>~</tt>-prefixed identifier per <xref target="MCPDNS"/>.  Handles are the unit
of identity addressing in this document.  A handle carries no zone
of its own.  Resolution queries the <tt>_alter</tt> underscore-prefixed
TXT record of the zone named by an <tt>org-scope</tt>, or of a zone
associated with the handle out of band, per <xref target="ALTER-URI"/>
Section 3.4, and never a zone derived from the handle's
spelling.  A handle that
matches the <tt>handle-ref</tt> rule of <xref target="ALTER-URI"/> names the same subject
as the <tt>alter:</tt> URI formed by prefixing it with <tt>alter:</tt>; the
trailer value <tt>~alice</tt> corresponds to <tt>alter:~alice</tt>.  The trailer
grammar of Section 4.1 carries the handle without the scheme name.</t>
          </dd>
          <dt>Sovereign-tier handle</dt>
          <dd>
            <t>A handle representing a human individual or formal organisation
with direct cryptographic agency.  Holds its own private key.
Can sign.  Examples: <tt>~alice</tt>, <tt>~example.com</tt>, <tt>~example-co.net</tt>.</t>
          </dd>
          <dt>Bot-tier handle</dt>
          <dd>
            <t>A handle representing an autonomous agent acting under scoped
delegation from a sovereign.  Holds a scoped key whose authority
is bounded by the sovereign's published delegation policy.  Can
counter-sign within the delegation envelope.  Examples:
<tt>~example-deps.bot</tt>, <tt>~example-merge.bot</tt>.</t>
          </dd>
          <dt>Instrument-tier handle</dt>
          <dd>
            <t>A handle representing an AI model, API endpoint, or tool class.
Does NOT hold cryptographic keys.  Cannot sign.  Exists as a
descriptive label only, suitable for attaching
provenance metadata to a contribution without making any
identity claim that requires cryptographic backing.  Examples:
<tt>~cc-example-model-1</tt>, <tt>~cc-example-model-2</tt>, <tt>~cc-example-model-3</tt>.</t>
          </dd>
          <dt>Patch Identifier</dt>
          <dd>
            <t>The value printed in the first field of <tt>git patch-id --verbatim</tt>
              <xref target="GIT-PATCH-ID"/> when given, on standard input, the output of
<tt>git diff-tree -p --root &lt;commit&gt;</tt>.  It is a function of the
change the commit makes, that is, the per-file diffs including
their context lines.  The commit's parents, message, author,
committer, timestamps and the rest of the tree do not affect it.
It is
hexadecimal digits: 40 in a SHA-1 repository and 64 in a SHA-256
repository, in the tests this document's author ran with git
2.56.0.  <xref target="GIT-PATCH-ID"/> describes it as a sum of SHA-1 hashes of
the per-file diffs; in a SHA-256 repository git computes it with
that repository's hash.  A commit with more than one parent, and a commit
whose diff is empty, produces no output and has no Patch
Identifier.</t>
          </dd>
          <dt>Tier-Slot Grammar</dt>
          <dd>
            <t>The constraint that a given trailer name accepts handles only
from its corresponding tier.  Cross-tier placement is a
grammatical error, rejected before any policy is consulted.</t>
          </dd>
          <dt>Rung</dt>
          <dd>
            <t>A level of conformance in this document.  Rung 1 is the trailer
grammar and signature of Sections 4 to 7.  Rung 2 is the
mode-attributed commit of Section 8.  Rung 3 is attribution
anchored in a transparency log through the <tt>Identity-Anchor:</tt>
trailer (Section 4.4).</t>
          </dd>
          <dt>Conformant Verifier</dt>
          <dd>
            <t>A consumer of commit trailers that implements the parsing,
rejection, and signature-verification rules defined in
Section 7.</t>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="identity-tier-taxonomy">
      <name>Identity Tier Taxonomy</name>
      <t>The trailer grammar in Section 4 partitions handles into three
tiers.  This section defines the taxonomy normatively for the
purposes of this specification.  Downstream attribution grammars
that reuse the taxonomy reference this document.</t>
      <table>
        <thead>
          <tr>
            <th align="left">Tier</th>
            <th align="left">Cryptographic Agency</th>
            <th align="left">Trailer Slot</th>
            <th align="left">Examples</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">Sovereign</td>
            <td align="left">Holds own key, signs</td>
            <td align="left">
              <tt>Acted-By:</tt></td>
            <td align="left">
              <tt>~alice</tt>, <tt>~example.com</tt>, <tt>~example-co.net</tt></td>
          </tr>
          <tr>
            <td align="left">Bot</td>
            <td align="left">Scoped delegated key</td>
            <td align="left">
              <tt>Executed-By:</tt></td>
            <td align="left">
              <tt>~example-deps.bot</tt>, <tt>~example-merge.bot</tt></td>
          </tr>
          <tr>
            <td align="left">Instrument</td>
            <td align="left">No key, no signature</td>
            <td align="left">
              <tt>Drafted-With:</tt></td>
            <td align="left">
              <tt>~cc-example-model-1</tt>, <tt>~cc-example-model-2</tt>, <tt>~cc-example-model-3</tt></td>
          </tr>
        </tbody>
      </table>
      <t>A handle's tier is read from its lexical form, as in <xref target="ALTER-URI"/>
Section 3.3: a trailing <tt>.bot</tt> marks the Bot tier, a leading <tt>cc-</tt>
marks the Instrument tier, and a handle carrying neither marker is
Sovereign-tier.  DNS does not settle a tier, and the envelope of
<xref target="MCPDNS"/> carries no tier field.  Implementations <bcp14>MUST NOT</bcp14> assign a
handle a tier other than the one its lexical form gives.</t>
      <t>Instrument-tier handles cannot make attestational claims.  A
<tt>Drafted-With:</tt> trailer records provenance
for information only and binds no verifiable identity.</t>
    </section>
    <section anchor="trailer-grammar-normative">
      <name>Trailer Grammar (Normative)</name>
      <section anchor="abnf">
        <name>ABNF</name>
        <t>The following ABNF <xref target="RFC5234"/> defines the syntax of each trailer.
Implementations <bcp14>MUST</bcp14> accept exactly this grammar.</t>
        <artwork><![CDATA[
acted-by-trailer     = "Acted-By:" SP sovereign-handle LF
executed-by-trailer  = "Executed-By:" SP bot-handle LF
drafted-with-trailer = "Drafted-With:" SP instrument-handle LF
identity-signature   = "Identity-Signature:" SP "ed25519:"
                       base64url-signature LF
identity-key-id      = "Identity-Key-Id:" SP alter-did-url LF
                       ; alter-did-url is imported from Section 3.2
                       ; of [DID-ALTER], and here it MUST carry its
                       ; "#" key-fragment
identity-anchor      = "Identity-Anchor:" SP "identitylog://"
                       timestamp "Z/sth/" seq "#" commit-id LF

sovereign-handle    = "~" handle-name
                      ; MUST NOT end in ".bot" and MUST NOT
                      ; begin with "cc-"
bot-handle          = "~" handle-name
                      ; MUST end in ".bot"
instrument-handle   = "~" handle-name
                      ; MUST begin with "cc-" and MUST NOT end in
                      ; ".bot"; tier determined by the "cc-" prefix
                      ; per [ALTER-URI]

handle-name         = ALPHA 0*62( ALPHA / DIGIT / "-" / "." )
                      ; letter first and no "_", as [ALTER-URI]
                      ; requires; the 63-character limit is this
                      ; document's own
bot-suffix          = %x2E.62.6F.74
                      ; ".bot", matched case-sensitively
base64url-signature = 86( base64url-char ) "=="
                      ; 64-byte Ed25519 signature, base64url-encoded
base64url-char      = ALPHA / DIGIT / "-" / "_"
timestamp           = 4DIGIT "-" 2DIGIT "-" 2DIGIT
                      "T" 2DIGIT ":" 2DIGIT ":" 2DIGIT
seq                 = 1*DIGIT
commit-id           = 40HEXDIG / 64HEXDIG
                      ; SHA-1 or SHA-256 commit identifier
]]></artwork>
        <t>The terminals <tt>ALPHA</tt>, <tt>DIGIT</tt>, <tt>HEXDIG</tt>, <tt>SP</tt>, and <tt>LF</tt> are
imported from <xref target="RFC5234"/>.  The trailer rules end in <tt>LF</tt> because the
lines of a git commit message are terminated by LF (%x0A) alone.
A carriage return at the end of a line is not part of the
trailer value, and a verifier <bcp14>MUST</bcp14> treat a trailer whose value ends
in one as malformed.</t>
        <t>The rule <tt>alter-did-url</tt> and the rules it uses are those of Section
3.2 of <xref target="DID-ALTER"/>, and within them <tt>handle-name</tt> is the production
of <xref target="ALTER-URI"/>.  The handle an <tt>Identity-Key-Id:</tt> value names <bcp14>MUST</bcp14>
be a Sovereign-tier handle whose name also matches <tt>handle-name</tt>
above.  The key fragment names the
verification method of the signing key, as <xref target="DID-ALTER"/> defines it.
A signer <bcp14>SHOULD</bcp14> include the zone after "@".  A verifier resolves a
DID that carries no zone only where it holds an association between
the handle and a zone established out of band, and otherwise the key
is unresolved (Section 5.2 of <xref target="DID-ALTER"/>).  An example value, in
the display form of <xref target="DID-ALTER"/>, is
<tt>did:alter:~alice@alice.example#key-1767225600</tt>.</t>
        <t>The three handle rules above match the same strings apart from the
<tt>.bot</tt> and <tt>cc-</tt> constraints, because a handle name may contain a dot (for
example <tt>~example.com</tt>).  The constraints are stated in comments in
the ABNF and are normative.  A handle ending in <tt>bot-suffix</tt> is a
Bot-tier handle and is valid only in an <tt>Executed-By:</tt> slot, and a
handle not ending in it is never valid there.</t>
        <t>The <tt>.bot</tt> suffix makes the tier syntactically distinguishable for
Bot trailers, and the <tt>cc-</tt> prefix does the same for Instrument
trailers, as in <xref target="ALTER-URI"/>.  A Sovereign-tier handle is one that
carries neither marker.  Cross-slot
placement is rejected by the verifier (Section 7).</t>
      </section>
      <section anchor="placement">
        <name>Placement</name>
        <t>Trailers <bcp14>MUST</bcp14> appear in the commit message footer block per the
git trailer convention <xref target="GIT-TRAILERS"/>.  The footer block is
separated from the commit message body by exactly one blank line.
Each trailer occupies one line of the footer block in the form
<tt>Key: Value</tt>.</t>
        <t>A commit message that places trailers anywhere other than the
footer block (e.g., interleaved with body paragraphs) is malformed
under this specification.  Conformant verifiers <bcp14>MUST</bcp14> refuse to
parse trailers from outside the footer block.</t>
      </section>
      <section anchor="ordering">
        <name>Ordering</name>
        <t>Trailers <bcp14>SHOULD</bcp14> appear in the following canonical order:</t>
        <ol spacing="normal" type="1"><li>
            <t><tt>Acted-By:</tt></t>
          </li>
          <li>
            <t><tt>Executed-By:</tt></t>
          </li>
          <li>
            <t><tt>Drafted-With:</tt></t>
          </li>
          <li>
            <t><tt>Identity-Signature:</tt></t>
          </li>
          <li>
            <t><tt>Identity-Key-Id:</tt></t>
          </li>
          <li>
            <t><tt>Identity-Anchor:</tt></t>
          </li>
        </ol>
        <t>Verifiers <bcp14>MUST</bcp14> accept trailers in any order, but emitters <bcp14>SHOULD</bcp14>
follow the canonical order to support diff-based review.</t>
      </section>
      <section anchor="multiplicity-rules">
        <name>Multiplicity Rules</name>
        <t>The following multiplicity constraints apply to a single commit:</t>
        <ul spacing="normal">
          <li>
            <t><strong><tt>Acted-By:</tt></strong>  At most one trailer per commit, and a commit
with more than one <tt>Acted-By:</tt> trailer is malformed.  A squash is a
new change attributed to whoever performed it, and the <tt>Acted-By:</tt>
trailers of the commits it replaces are not carried into it.</t>
          </li>
          <li>
            <t><strong><tt>Executed-By:</tt></strong>  At most one trailer per commit.  A commit
is executed by at most one bot in a single delegation context.</t>
          </li>
          <li>
            <t><strong><tt>Drafted-With:</tt></strong>  Zero or more trailers per commit.
Multi-instrument drafting (e.g., a commit drafted partly with
<tt>~cc-example-model-1</tt> and partly with <tt>~cc-example-model-2</tt>) is
permitted and expected.  Multiple <tt>Drafted-With:</tt> trailers on a single commit
form an unordered set; order of appearance is not semantically
significant and verifiers <bcp14>MUST NOT</bcp14> attribute differential
authority to earlier-appearing entries.</t>
          </li>
          <li>
            <t><strong><tt>Identity-Signature:</tt> and <tt>Identity-Key-Id:</tt></strong>  These two
trailers <bcp14>MUST</bcp14> appear together or not at all.  An
<tt>Identity-Signature:</tt> without an <tt>Identity-Key-Id:</tt> is malformed,
and vice versa.  When present, they bind to the <tt>Acted-By:</tt>
trailer of the same commit, except as Section 8.4 provides for
member signatures on a mode commit.  A commit with more than one parent
<bcp14>MUST NOT</bcp14> carry them (Section 5.2).</t>
          </li>
          <li>
            <t><strong><tt>Identity-Anchor:</tt></strong>  <bcp14>OPTIONAL</bcp14> in this version of the
specification.  Implementations targeting Rung-3-compliant
attribution (transparency-log-anchored) <bcp14>MUST</bcp14> emit it; all
other implementations <bcp14>MAY</bcp14> omit it.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="signature-algorithm-normative">
      <name>Signature Algorithm (Normative)</name>
      <section anchor="algorithm">
        <name>Algorithm</name>
        <t>The signature algorithm is Ed25519 <xref target="RFC8032"/>.  It uses SHA-512
internally and produces a 64-byte signature over an input message
of any length.  Implementations <bcp14>MUST</bcp14> use Ed25519 and <bcp14>MUST NOT</bcp14> use
Ed25519ph or Ed25519ctx variants.</t>
      </section>
      <section anchor="signed-payload">
        <name>Signed Payload</name>
        <t>The signed payload is the concatenation of a fixed prefix, an
object-format octet, and the commit's Patch Identifier (Section 2.2)
in binary form.</t>
        <t>The prefix is the 38 octets of the ASCII string
<tt>identity-attributed-commit/patch-id/v1</tt> followed by one NUL octet,
39 octets in all:</t>
        <artwork><![CDATA[
69 64 65 6e 74 69 74 79 2d 61 74 74 72 69 62 75
74 65 64 2d 63 6f 6d 6d 69 74 2f 70 61 74 63 68
2d 69 64 2f 76 31 00
]]></artwork>
        <t>The prefix is followed by one octet naming the object format of the
repository the commit belongs to: 0x01 for SHA-1 and 0x02 for
SHA-256.  The Patch Identifier follows, as the hexadecimal digits git
prints decoded to octets.  A verifier <bcp14>MUST</bcp14> reject any identifier that
is not 40 or 64 digits long.  The payload is the prefix, the format
octet and the identifier, 60 octets for a 40-digit identifier.  The
prefix separates this signature from any other use of the same key
over other data, and the trailing NUL ends it so that no longer
string can share it as a prefix.  The format octet keeps an
identifier computed in one object format from being presented as one
computed in the other.</t>
        <t>The Patch Identifier is obtained with:</t>
        <artwork><![CDATA[
git diff-tree -p --root <commit> | git patch-id --verbatim
]]></artwork>
        <t>taking the first field of the output.  <tt>git diff-tree</tt> is a plumbing
command and does not read the <tt>diff.*</tt> configuration that changes
the output of <tt>git diff</tt>.  A signer working before the commit exists
obtains the same input with <tt>git diff-index -p --cached HEAD</tt>, or
against the empty tree for a root commit.  It does not use <tt>git diff
--cached</tt>, since that command reads the configuration.</t>
        <t>A commit with more than one parent has no Patch Identifier, because
<tt>git diff-tree -p</tt> prints nothing for it.  A merge commit therefore
carries no <tt>Identity-Signature:</tt> and no <tt>Identity-Key-Id:</tt>, and
neither does a commit whose diff is empty.  The <tt>--verbatim</tt> option
is not present in every git release (Section 9.6).</t>
      </section>
      <section anchor="rationale-for-signing-the-change">
        <name>Rationale for Signing the Change</name>
        <t>A signature is useful if it survives the operations that carry a
change from one place in history to another.  A commit hash does not,
and it cannot contain a trailer that signs it.  Rebase, cherry-pick,
amend, and filter-branch all change the commit hash.</t>
        <t>The tree hash does not either.  A tree names the whole state of the
repository after the commit and changes whenever the parent
changes.  A commit rebased onto a different parent has a different
tree, and a squash has a tree that no contributor signed.</t>
        <t>The Patch Identifier depends on what the commit changes and on the
context lines around it, and on nothing else in the commit.  A
commit moved onto a different parent keeps the same identifier when
its diff is the same, and loses it when the base has altered the
lines the diff touches or the lines beside them.  The signature then
attests the change the sovereign made, whatever state the repository
was in before or after it.  The costs of that choice
are set out in Section 9.6.</t>
        <t>Where stronger anchoring is required, the optional
<tt>Identity-Anchor:</tt> trailer binds the signature to a specific
commit-id within a transparency log entry, recovering commit-level
identity at the cost of an external dependency.</t>
      </section>
      <section anchor="signature-format">
        <name>Signature Format</name>
        <t>The signature is encoded for placement in the trailer as:</t>
        <artwork><![CDATA[
ed25519:<base64url-signature>
]]></artwork>
        <t>The base64url encoding follows <xref target="RFC4648"/> Section 5 (URL- and
filename-safe alphabet) without line breaks.  A 64-byte Ed25519
signature encodes to 86 base64url characters plus two <tt>=</tt> padding
characters, for a total of 88 characters in the trailer value
following the <tt>ed25519:</tt> prefix.</t>
      </section>
      <section anchor="key-derivation-and-rotation">
        <name>Key Derivation and Rotation</name>
        <t>Sovereign keys are derived out-of-band; their public components
are published under the sovereign's <tt>_alter</tt> DNS record per
<xref target="MCPDNS"/>.  Key derivation, custody, and recovery procedures are
out of scope for this document.  This document treats the
sovereign key as a pre-existing Ed25519 keypair whose public
component is reachable via the DNS-resolved path of Section 6.1.</t>
        <t>The <tt>Identity-Key-Id:</tt> trailer names the key that signed a given
commit.  The history of a sovereign's keys is governed by Section 6
of <xref target="DID-ALTER"/>.</t>
      </section>
    </section>
    <section anchor="dns-resolution-normative-reference">
      <name>DNS Resolution (Normative Reference)</name>
      <section anchor="sovereign-key-resolution">
        <name>Sovereign Key Resolution</name>
        <t>The sovereign handle's public key is resolved via the <xref target="MCPDNS"/>
          <tt>_alter.&lt;zone&gt;</tt> DNS record mechanism.  Verifiers <bcp14>MUST</bcp14> resolve the
DID in the <tt>Identity-Key-Id:</tt> trailer as Section 5.2 of <xref target="DID-ALTER"/>
specifies.  That section runs the resolution algorithm of <xref target="MCPDNS"/>
against the zone the DID names.  Where the DID names no zone, that section
admits only a zone associated with the handle out of band, per
<xref target="ALTER-URI"/> Section 3.4.  The public key is the one of the
verification method that the trailer's key fragment names.</t>
        <t>Verifiers <bcp14>MUST</bcp14> require DNSSEC <xref target="RFC4034"/> validation on the
<tt>_alter.&lt;zone&gt;</tt> lookup, as <xref target="MCPDNS"/> does.  <xref target="MCPDNS"/> defines no
other retrieval path for the envelope.  A key that cannot be
retrieved and validated this way is unresolved, and Step 3 of
Section 7 applies.</t>
      </section>
      <section anchor="instrument-metadata-resolution">
        <name>Instrument Metadata Resolution</name>
        <t>This document defines no record for an Instrument-tier handle,
and <xref target="MCPDNS"/> gives one no envelope.  A verifier <bcp14>MUST NOT</bcp14> treat
anything published about an Instrument-tier handle, such as its
provider, version or capability profile, as an attestational
claim.  Instrument handles cannot sign commits; a <tt>Drafted-With:</tt>
trailer says which instrument was involved and makes no claim that
it authorised the commit.</t>
      </section>
    </section>
    <section anchor="verifier-behaviour-normative">
      <name>Verifier Behaviour (Normative)</name>
      <t>A conformant verifier <bcp14>MUST</bcp14> perform the following steps in order:</t>
      <ol spacing="normal" type="1"><li>
          <t><strong>Parse all trailers from the footer block.</strong>  Trailers
appearing outside the footer block <bcp14>MUST</bcp14> be ignored.</t>
        </li>
        <li>
          <t><strong>Reject cross-slot category errors.</strong>  For each trailer,
determine the handle's tier from its lexical form (Section 3).
No DNS lookup is made for this step.  If any handle appears in a slot
other than its tier's slot, for example an Instrument-tier
handle in an <tt>Acted-By:</tt> slot, or a Sovereign-tier handle in
a <tt>Drafted-With:</tt> slot, the commit is malformed and the
verifier <bcp14>MUST</bcp14> reject it as a category error.  The error
message <bcp14>SHOULD</bcp14> identify the offending trailer by name.</t>
        </li>
        <li>
          <t><strong>Verify signatures, if present.</strong>  If <tt>Identity-Signature:</tt>
and <tt>Identity-Key-Id:</tt> are present, the verifier <bcp14>MUST</bcp14>:  </t>
          <ul spacing="normal">
            <li>
              <t>Extract the DID and its key fragment from the
<tt>Identity-Key-Id:</tt> trailer.  The DID names the <tt>Acted-By:</tt>
handle, except as Section 8.4 provides for a member signature
on a mode commit.  If it names any other handle, mark the
commit <tt>unverified</tt>.</t>
            </li>
            <li>
              <t>Resolve the corresponding public key from the <tt>_alter</tt> record
of the zone the DID names, per Section 6.1.</t>
            </li>
            <li>
              <t>If the commit has more than one parent, or has no Patch
Identifier, mark it <tt>unverified</tt>.</t>
            </li>
            <li>
              <t>Otherwise compute the commit's Patch Identifier per Section
5.2, form the signed payload, and verify the Ed25519
signature against it using the resolved public key.</t>
            </li>
          </ul>
          <t>
If signature verification fails, the verifier <bcp14>MUST</bcp14> mark the
commit as <tt>unverified</tt> and <bcp14>MUST NOT</bcp14> report it as having a valid
sovereign attribution.</t>
        </li>
        <li>
          <t><strong>Verify the transparency anchor, if present.</strong>  If
<tt>Identity-Anchor:</tt> is present, the verifier <bcp14>SHOULD</bcp14> verify the
anchor against the referenced log according to the log's own
verification protocol.  Failure to verify the anchor <bcp14>MUST</bcp14> be
surfaced to the user but <bcp14>MUST NOT</bcp14> silently downgrade the
commit's verified status.</t>
        </li>
      </ol>
      <t>A conformant verifier <bcp14>SHOULD</bcp14> also:</t>
      <ol spacing="normal" type="1"><li>
          <t><strong>Cache handle-to-key resolutions.</strong>  DNS lookups for the same
handle within a single verification pass should be performed
at most once.  Cache TTL <bcp14>SHOULD</bcp14> respect the DNS record TTL.</t>
        </li>
        <li>
          <t><strong>Distinguish attribution states in user-facing output.</strong>
Verifiers <bcp14>SHOULD</bcp14> present three distinct states to users:  </t>
          <ul spacing="normal">
            <li>
              <t><tt>verified</tt>: <tt>Acted-By:</tt> present with a valid
<tt>Identity-Signature:</tt> resolving to the published key.</t>
            </li>
            <li>
              <t><tt>claimed</tt>: <tt>Acted-By:</tt> present without a signature, or
with a signature whose key cannot be resolved.</t>
            </li>
            <li>
              <t><tt>anonymous</tt>: no <tt>Acted-By:</tt> present.</t>
            </li>
          </ul>
          <t>
Conflating these states is a security defect.</t>
        </li>
      </ol>
      <t>Because every tier is read from the handle's lexical form, Step 2
detects every cross-slot placement without DNS, including during a
DNS outage.  Only Step 3 depends on DNS.</t>
    </section>
    <section anchor="rung-2-extension-mode-attributed-commits">
      <name>Rung 2 Extension: Mode-Attributed Commits</name>
      <section anchor="motivation">
        <name>Motivation</name>
        <t>The trailer grammar of Section 4 attributes each commit to individual
identities, at most one Sovereign actor, at most one Bot and zero or
more Instruments.  A class of contributions falls outside this model.
A mode is a bounded, DNS-addressable composition of Sovereigns
operating under declared threshold consent, and work it produces
jointly has no single <tt>~handle</tt> as its author.  Examples include
pair-programming commits where two Sovereigns contributed
indistinguishably, working-group decisions ratified by a quorum,
AI-majority outputs produced by a mode whose signing authority sits
with the mode as a whole and with no single member, and
cross-organisation commits ratified jointly by two or more modes.</t>
        <t>Rung 1 of this specification has no surface for such attributions.
A committer must either name one member arbitrarily as <tt>Acted-By:</tt>
and misattribute the commit, or omit <tt>Acted-By:</tt> entirely and leave
the commit in the <tt>claimed</tt> state.  Rung 2 adds a trailer class for
these commits, <tt>Acted-By-Mode:</tt>, whose value is a mode handle and
whose semantics are threshold-attestational rather than
individual-attestational.</t>
      </section>
      <section anchor="trailer-acted-by-mode">
        <name>Trailer: <tt>Acted-By-Mode</tt></name>
        <t>The following ABNF extends Section 4.1:</t>
        <artwork><![CDATA[
acted-by-mode-trailer = "Acted-By-Mode:" SP mode-handle LF
mode-handle           = "~" handle-name "@" org-scope
                        ; handle-name MUST NOT end in ".bot" and
                        ; MUST NOT begin with "cc-"
org-scope             = domain-label *( "." domain-label )
domain-label          = ALPHA / ( ALPHA *( ALPHA / DIGIT / "-" )
                                  ( ALPHA / DIGIT ) )
]]></artwork>
        <t>A mode handle names the mode by its handle and the hosting zone of
the mode by its <tt>org-scope</tt>, the form <tt>~&lt;handle&gt;@&lt;zone&gt;</tt> that
<xref target="ALTER-URI"/> gives a handle qualified by an organisational scope.
The trailer value <tt>~release@example.org</tt> corresponds to
<tt>alter:~release@example.org</tt>.  The zone is taken from <tt>org-scope</tt>
alone and never from the spelling of the handle.  The <tt>@</tt>
separates a mode handle from the handle rules of Section 4.1, none
of which admits it, and whether the named handle is a mode is
settled by the record of Section 8.3.</t>
        <t>The semantics of <tt>Acted-By-Mode:</tt> are threshold-attestational.  The
trailer asserts that the commit was authored under the compositional
consent standing of the named mode as a whole, and asserts nothing
about the signing authority of any single member.  A commit <bcp14>MAY</bcp14> carry both an individual
<tt>Acted-By:</tt> trailer (naming the Sovereign who physically performed
the commit operation) and an <tt>Acted-By-Mode:</tt> trailer (naming the
mode under whose standing the work was performed); the combination
attests "member M committed on behalf of mode O under compositional
consent".  A commit <bcp14>MUST</bcp14> be permitted to carry <tt>Acted-By-Mode:</tt> as
its sole <tt>Acted-By-*</tt> trailer class when the work is purely
mode-coupled and no single Sovereign claims primary authorship.</t>
      </section>
      <section anchor="tier-resolution">
        <name>Tier Resolution</name>
        <t>Under Rung 2 a tier is still read from the handle's lexical form
(Section 3), and a mode adds no fourth tier to that reading.  A
handle is a mode when its record, in the <tt>_alter.&lt;zone&gt;</tt> TXT record
of the zone its <tt>org-scope</tt> names, declares it one.</t>
        <t>A mode handle <bcp14>MUST</bcp14> resolve to an <tt>_alter</tt> record whose capability
declaration includes <tt>cap=mode</tt> (or an equivalent capability token
established in a later revision of <xref target="MCPDNS"/>).  The mode record
carries, at minimum:</t>
        <ul spacing="normal">
          <li>
            <t><tt>type=mode</tt>: declares the handle a mode.</t>
          </li>
          <li>
            <t><tt>threshold=&lt;num&gt;/&lt;den&gt;</tt>: declares the signing threshold required
for the mode to attest to a commit (for example, <tt>threshold=2/3</tt>
requires two of three member signatures).</t>
          </li>
          <li>
            <t><tt>members=&lt;uri&gt;</tt>: a reference to the mode's member attestation
keylist, itself a DNS-published or HTTPS-resolved JSON document
listing member Sovereign handles and their currently-valid
signing-key identifiers.</t>
          </li>
        </ul>
        <t>Verifiers <bcp14>MUST</bcp14> retrieve and DNSSEC-validate the mode record as
Section 6.1 requires for Sovereign key resolution.  A mode record
that cannot be retrieved and validated that way is unresolved.</t>
      </section>
      <section anchor="verification">
        <name>Verification</name>
        <t>Section 7 is extended for Rung 2 as follows.  For each
<tt>Acted-By-Mode:</tt> trailer on a commit, a conformant Rung 2 verifier
<bcp14>MUST</bcp14>:</t>
        <ol spacing="normal" type="1"><li>
            <t>Resolve the mode handle per Section 8.3 above.</t>
          </li>
          <li>
            <t>Fetch the threshold-attestation metadata (<tt>threshold</tt>, <tt>members</tt>).</t>
          </li>
          <li>
            <t>Enumerate the member signatures present on the commit, that is,
the set of <tt>Identity-Signature:</tt> trailers whose corresponding
<tt>Identity-Key-Id:</tt> binds to a Sovereign handle listed in the
mode's member keylist.</t>
          </li>
          <li>
            <t>Verify that the count of valid member signatures satisfies the
declared threshold.</t>
          </li>
        </ol>
        <t>Under the Rung 2 hard-gate profile, a commit bearing
<tt>Acted-By-Mode:</tt> whose member signature set does not satisfy the
declared threshold <bcp14>MUST</bcp14> be marked <tt>unverified</tt>.  Under the Rung 2
warn-only profile (the rollout default), verification is limited to
parse-only and slot-category correctness; threshold satisfaction is
surfaced as informational but does not downgrade the commit's
verified status.</t>
      </section>
      <section anchor="slot-exclusivity">
        <name>Slot Exclusivity</name>
        <t><tt>Acted-By-Mode:</tt> accepts mode handles ONLY.  Verifiers <bcp14>MUST</bcp14> reject
a value without an <tt>org-scope</tt>, and any Bot-tier or Instrument-tier
handle, appearing in this slot as cross-slot category errors per the
rules of Section 7, Step 2.  A handle whose record does not declare
it a mode fails Step 1 of Section 8.4.
The existing <tt>Acted-By:</tt> slot continues to accept Sovereign handles
ONLY, regardless of whether an <tt>Acted-By-Mode:</tt> is also present.</t>
      </section>
      <section anchor="interaction-with-co-authored-by">
        <name>Interaction with Co-Authored-By</name>
        <t>The <tt>Co-Authored-By:</tt> trailer <xref target="GH-COAUTHOR"/> remains unchanged by this
extension.  A commit-UI surface that does not parse the identity
trailer grammar natively shows the authoring mode only when it is
written as text.  Commits bearing <tt>Acted-By-Mode:</tt> <bcp14>SHOULD</bcp14> therefore
include a <tt>Co-Authored-By:</tt> line rendering the mode handle in
human-readable form.</t>
      </section>
      <section anchor="rung-2-rollout">
        <name>Rung 2 Rollout</name>
        <t>Rung 2 <bcp14>MUST</bcp14> be deployed in two sub-phases.  In the parse-only
sub-phase, conformant hooks and verifiers accept and recognise the
<tt>Acted-By-Mode:</tt> trailer, enforce slot-exclusivity per Section 8.5,
and surface member signature counts informationally.  They do NOT
enforce the threshold.  The parse-only sub-phase is permitted before
the <tt>_alter</tt> resolver has shipped in the deployment.</t>
        <t>In the signature-verification sub-phase, verifiers also
enforce that the member signature set satisfies the mode's declared
threshold.  The signature-verification sub-phase <bcp14>MUST NOT</bcp14> be enabled
before the <tt>_alter</tt> resolver is in production and the mode record
schema of Section 8.3 is stable.</t>
        <t>The warn-only profile is a permitted transitional state.  Once the <tt>_alter</tt> resolver is in
production and the mode record schema of Section 8.3 is stable, a
conformant deployment <bcp14>MUST</bcp14> promote from the warn-only profile to the
hard-gate profile.  A deployment <bcp14>MUST NOT</bcp14> remain on the warn-only
profile, nor stall indefinitely in the parse-only sub-phase, once
these preconditions are satisfied; continuing to accept
<tt>Acted-By-Mode:</tt> threshold claims without enforcement after that
point is non-conformant with this section.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <section anchor="sovereign-key-compromise">
        <name>Sovereign Key Compromise</name>
        <t>If a sovereign's signing key is compromised, the sovereign revokes
the envelope that carries it, as <xref target="MCPDNS"/> specifies, and publishes a
new envelope with a new key.  Revocation invalidates every signature
made under the revoked key at once, whenever it was made (Section
5.4 of <xref target="DID-ALTER"/>).  A verifier that observes the revocation <bcp14>MUST</bcp14>
mark every commit signed under that key <tt>unverified</tt>.  Section 6 of
<xref target="DID-ALTER"/> sets out which earlier keys a verifier can still use.</t>
      </section>
      <section anchor="instrument-handle-spoofing">
        <name>Instrument Handle Spoofing</name>
        <t>Because Instrument handles cannot sign, the <tt>Drafted-With:</tt>
trailer is an unverified provenance claim.  A malicious committer
can always paste <tt>Drafted-With: ~cc-example-model-1</tt> into a commit they
hand-wrote.  Implementations <bcp14>MUST</bcp14> treat Instrument attribution as
informational only, and <bcp14>MUST NOT</bcp14> extend trust decisions on the
basis of an Instrument trailer alone.  The sovereign signature
on <tt>Acted-By:</tt> does not repair this.  It binds a real
cryptographic identity to the commit, and a false <tt>Drafted-With:</tt>
claim then has a named signer answerable for it.  The signature
does not make that claim true, and it attests nothing about which
tools were in fact used.  A
deployment requiring assurance about instrument involvement <bcp14>MUST</bcp14>
obtain that assurance from a source outside this trailer grammar.</t>
      </section>
      <section anchor="limits-of-sovereign-attestation">
        <name>Limits of Sovereign Attestation</name>
        <t>A valid <tt>Identity-Signature:</tt> attests that, at signing time, the
holder of the private key published under the <tt>Identity-Key-Id:</tt>
of the <tt>Acted-By:</tt> handle asserted the signed payload of Section 5.2
over that change.  It does not attest any of the following, and a verifier <bcp14>MUST NOT</bcp14> report or
imply any of them on the strength of a valid signature alone:</t>
        <ul spacing="normal">
          <li>
            <t>that the sovereign authored the content, or reviewed content
authored by anything else;</t>
          </li>
          <li>
            <t>that the change was made against any particular base, or that the
tree it produces is the tree the sovereign saw;</t>
          </li>
          <li>
            <t>that any handle named in <tt>Executed-By:</tt> or <tt>Drafted-With:</tt> did
or did not participate, in any degree;</t>
          </li>
          <li>
            <t>that a delegated actor was, at the moment it acted, operating
within an authority the sovereign had granted, in scope, in
force, and unrevoked;</t>
          </li>
          <li>
            <t>that the sovereign observed the act as it occurred, or is in a
position to enumerate the acts performed under its identity.</t>
          </li>
        </ul>
        <t>The signature asserts something about content at one point in
time.  Delegated authority has a scope, bounds and lifetime of its
own, and no property of an Ed25519 signature over a patch
identifier carries it.  A deployment that needs to know whether a
non-sovereign actor was authorised to act for a sovereign <bcp14>MUST</bcp14>
establish that from an authority record obtained out of band;
specifying such a record is out of scope for this document.  A
valid signature in particular <bcp14>MUST NOT</bcp14> be treated as evidence
that an authority existed, that its bounds were respected, or
that it had not been revoked before the commit was made.  A
Bot-tier counter-signature attests only that a scoped key
was used, and leaves open whether the use fell within the
delegation envelope the sovereign intended.</t>
        <t>A commit carrying <tt>Acted-By:</tt>
and no delegate or instrument trailer is not evidence that no
delegate or instrument was involved.  The Negative-Attribution
Risk subsection below states the deliberate-omission case; a
further case is that a record of delegated activity may be
legitimately withheld from a particular reader without being
absent from the record itself.  Verifiers <bcp14>MUST NOT</bcp14> infer absence
of delegation from absence of a named delegate.</t>
        <t>A signature establishes that one commit is attributable and says
nothing about whether the full record of activity conducted under that
identity is visible to the person or organisation the identity
belongs to; completeness of that record, where a deployment
offers it, is a property of the deployment, outside this
grammar.  Implementations <bcp14>MUST NOT</bcp14> present signature validity to
a sovereign as evidence that everything done under their identity
is visible to them.</t>
        <t>Attribution under this document identifies who is answerable for a
commit.  It does not establish with certainty what took place when
the commit was made (<xref target="MORRISON-IFT"/>).  Implementations <bcp14>SHOULD</bcp14>
phrase user-facing output accordingly, and <bcp14>MUST NOT</bcp14> label a
signed commit in terms that assert supervision, review, or
authorisation.</t>
      </section>
      <section anchor="dns-poisoning">
        <name>DNS Poisoning</name>
        <t>A successful DNS poisoning attack against the <tt>_alter.&lt;zone&gt;</tt>
record could redirect verifiers to a substitute public key under
the attacker's control.  This risk is mitigated by:</t>
        <ul spacing="normal">
          <li>
            <t>DNSSEC validation, required by Section 6.1.  A key from an
unsigned zone, or one that fails validation, is unresolved.</t>
          </li>
          <li>
            <t>Independent transparency-log anchoring through the optional
<tt>Identity-Anchor:</tt> trailer.  The log is a second source of truth
that DNS poisoning does not reach.</t>
          </li>
        </ul>
      </section>
      <section anchor="patch-identifier-collision">
        <name>Patch Identifier Collision</name>
        <t><xref target="GIT-PATCH-ID"/> describes the Patch Identifier as a sum of SHA-1
hashes of the per-file diffs.  SHA-1 is cryptographically weakened
for collision resistance (SHAttered, 2017), and a sum of hashes is
not a hash function with the properties of SHA-1 itself.  This
document has not analysed how hard it is to construct a second
change with the same Patch Identifier, and a verifier <bcp14>SHOULD NOT</bcp14>
assume more than the strength of SHA-1.  An attacker who could do so
could present a different change under a valid signature.  The
signature itself is Ed25519 and is not weakened by this.  Verifiers
<bcp14>SHOULD</bcp14> record the commit hash alongside the Patch Identifier in any
local audit log.  A later finding about the identifier can then be
checked against the history.</t>
      </section>
      <section anchor="costs-of-the-patch-identifier-basis">
        <name>Costs of the Patch-Identifier Basis</name>
        <t>Signing the change has the following accepted costs.</t>
        <ul spacing="normal">
          <li>
            <t><strong>A moved commit still verifies.</strong>  A commit moved onto a base the
signer never saw verifies if its diff and the context around it
are unchanged, because the Patch Identifier does not depend on the
parent.  The change may behave differently on that base.  This is
the bound already stated in Section 9.3, that the signature says
nothing about the state the repository is in.</t>
          </li>
          <li>
            <t><strong>The commit message is not signed.</strong>  Because the Patch Identifier
ignores the message, the message and the trailers in it can be
altered without invalidating the signature.  That includes the
<tt>Drafted-With:</tt> and <tt>Executed-By:</tt> trailers.</t>
          </li>
          <li>
            <t><strong>A rebase can break a signature.</strong>  A commit rebased onto a base
that alters the lines its diff touches, or the lines beside them,
has a different Patch Identifier and no longer verifies.  This
fails closed.  The same applies to a cherry-pick whose conflict
resolution changes the diff.</t>
          </li>
          <li>
            <t><strong>Git version.</strong>  The <tt>--verbatim</tt> option is needed so that
whitespace is not stripped before hashing, and it is not present in
every git release.  A verifier using a git without it cannot
compute the value defined here, and a verifier <bcp14>MUST NOT</bcp14> substitute
the default or <tt>--stable</tt> mode, whose results differ for changes
that alter whitespace.</t>
          </li>
          <li>
            <t><strong>Object formats.</strong>  The identifier was 40 hexadecimal digits in a
SHA-1 repository and 64 in a SHA-256 repository in the author's
tests with one git release.  Other releases have not been checked, and the
format octet of Section 5.2 exists so that identifiers from the two
formats are never taken for one another.</t>
          </li>
          <li>
            <t><strong>No signature on merges or empty commits.</strong>  A merge commit and a
commit with an empty diff have no Patch Identifier.  Their
attribution rests on the parents and on whoever created them,
outside this mechanism.</t>
          </li>
        </ul>
      </section>
      <section anchor="key-custody-at-the-commit-signing-boundary">
        <name>Key Custody at the Commit-Signing Boundary</name>
        <t>The pre-commit hook (or analogous integration point) that invokes
the signing operation is a trust-sensitive boundary.  The hook
runs in the unprivileged developer process and may have access
to the sovereign's private key.  Implementations <bcp14>SHOULD</bcp14> route
signing through a privileged helper (for example, a unix domain
socket exposed by a dedicated signing daemon, or a hardware
authenticator using WebAuthn PRF) rather than reading the
private key directly from unprivileged process memory.  Direct
key handling in the developer process is acceptable for
prototyping but <bcp14>MUST NOT</bcp14> be relied upon in production
deployments where commit attribution carries weight.</t>
      </section>
      <section anchor="negative-attribution-risk">
        <name>Negative-Attribution Risk</name>
        <t>A committer may deliberately omit the <tt>Drafted-With:</tt> trailer to
conceal AI-instrument involvement in a contribution.  This is
detectable only by out-of-band evidence and is not addressable at
the protocol layer.  Where AI-disclosure obligations exist (for
example, in regulated software development contexts), they <bcp14>SHOULD</bcp14>
be enforced at the policy layer.</t>
      </section>
      <section anchor="mode-threshold-non-enforcement-under-the-rollout-default">
        <name>Mode-Threshold Non-Enforcement Under the Rollout Default</name>
        <t>The Rung 2 extension's security value for <tt>Acted-By-Mode:</tt> rests
entirely on the member-signature threshold check defined in the
Verification subsection above.  The rollout path defined in the Rung
2 Rollout subsection does not enforce that check universally.  The
parse-only sub-phase, itself a <bcp14>MUST</bcp14>-mandated first phase for any
deployment whose resolver has not shipped, surfaces member signature
counts informationally without enforcing the threshold, and the
warn-only profile carries the same non-enforcement forward as the
stated rollout default.  In either state, a committer holding fewer
than the declared threshold of member keys (including zero, where
local key custody permits it) can attach <tt>Acted-By-Mode:</tt> claiming
full quorum or governance ratification, and the commit's verified
status is not downgraded.  Implementations <bcp14>MUST</bcp14> treat commits
carrying <tt>Acted-By-Mode:</tt> under a non-hard-gate profile as
unverified for any purpose that depends on the threshold claim.  See
the Rung 2 Rollout subsection above for the <bcp14>MUST</bcp14>-level obligation to
promote a deployment out of the warn-only profile once its
preconditions are satisfied.</t>
      </section>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="git-trailer-name-registration">
        <name>Git Trailer Name Registration</name>
        <t>At the time of writing, IANA does not maintain a registry of git
commit trailer names.  If such a registry is established, this
document requests registration of the following trailer names
with reference to this specification:</t>
        <ul spacing="normal">
          <li>
            <t><tt>Acted-By</tt></t>
          </li>
          <li>
            <t><tt>Executed-By</tt></t>
          </li>
          <li>
            <t><tt>Drafted-With</tt></t>
          </li>
          <li>
            <t><tt>Identity-Signature</tt></t>
          </li>
          <li>
            <t><tt>Identity-Key-Id</tt></t>
          </li>
          <li>
            <t><tt>Identity-Anchor</tt></t>
          </li>
        </ul>
        <t>Until a formal registry exists, this document recommends that
implementers coordinate with the author and
treat the trailer names defined here as reserved for the
identity-attributed commit grammar.</t>
      </section>
      <section anchor="uri-scheme-dependencies">
        <name>URI Scheme Dependencies</name>
        <t>This document writes the <tt>Identity-Key-Id:</tt> trailer as a <tt>did:alter</tt>
DID <xref target="DID-ALTER"/>.  The <tt>alter:</tt> URI scheme is the
subject of IANA considerations in <xref target="ALTER-URI"/>; this document does
not separately register it.</t>
        <t>The <tt>identitylog://</tt> URI scheme used by the optional
<tt>Identity-Anchor:</tt> trailer is reserved by this document until a
registration exists.  Implementations encountering <tt>identitylog://</tt> URIs
without a registered scheme <bcp14>MUST</bcp14> treat the anchor as an opaque
reference and <bcp14>SHOULD NOT</bcp14> attempt resolution.</t>
      </section>
      <section anchor="no-other-iana-actions">
        <name>No Other IANA Actions</name>
        <t>This document requests no other IANA actions.</t>
      </section>
    </section>
    <section anchor="relationship-to-existing-standards">
      <name>Relationship to Existing Standards</name>
      <t>The trailer grammar defined here is intended to coexist with
prior commit-attribution mechanisms.</t>
      <table>
        <thead>
          <tr>
            <th align="left">Mechanism</th>
            <th align="left">Purpose</th>
            <th align="left">Coexistence with this spec</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">Git <tt>Signed-off-by</tt> <xref target="DCO"/></td>
            <td align="left">Legal attestation of contribution rights</td>
            <td align="left">Orthogonal.  A commit <bcp14>MAY</bcp14> carry both a <tt>Signed-off-by:</tt> and an <tt>Acted-By:</tt> trailer.</td>
          </tr>
          <tr>
            <td align="left">Git commit signing (<tt>git commit -S</tt>)</td>
            <td align="left">Cryptographic identity via GPG/SSH key directories</td>
            <td align="left">Orthogonal.  A commit <bcp14>MAY</bcp14> be both GPG-signed and <tt>Acted-By</tt>-signed.  Verifiers handle each path independently.</td>
          </tr>
          <tr>
            <td align="left">Sigstore / gitsign <xref target="GITSIGN"/></td>
            <td align="left">Keyless cryptographic identity via OIDC</td>
            <td align="left">Architecturally adjacent.  Different identity provider model (OIDC + Rekor vs DNS-resolved DID + IdentityLog).  May coexist.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>Co-Authored-By:</tt> <xref target="GH-COAUTHOR"/></td>
            <td align="left">Plain-text co-author line</td>
            <td align="left">Orthogonal.  <tt>Drafted-With:</tt> names an Instrument-tier handle where <tt>Co-Authored-By:</tt> names a person or a tool as text.  A commit <bcp14>MAY</bcp14> carry both.</td>
          </tr>
          <tr>
            <td align="left">Linux kernel <tt>Assisted-by</tt> <xref target="LINUX-AI-ASSIST"/></td>
            <td align="left">Disclosure-only attribution of AI assistance in kernel contributions; legal liability remains with a human via DCO (<tt>Signed-off-by</tt>)</td>
            <td align="left">Architecturally adjacent and complementary.  <tt>Assisted-by:</tt> discloses AI involvement in prose-readable form; <tt>Drafted-With:</tt> names the same involvement with an Instrument <tt>~handle</tt>.  Both <bcp14>MAY</bcp14> appear on the same commit.</td>
          </tr>
        </tbody>
      </table>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The author thanks colleagues at Alter Meridian Pty Ltd for the
framing of identity tiers, and external reviewers who tested the
tier-slot grammar and the cross-tier rejection rules.</t>
    </section>
    <section numbered="false" anchor="document-history">
      <name>Document History</name>
      <t>draft-morrison-identity-attributed-commits-05 (November 2026):</t>
      <ul spacing="normal">
        <li>
          <t>Section 1.3 states that a vouch is a stance toward a contribution
and not an identity tier, and that no trailer here carries it.  No
requirement changes and no reference is added.</t>
        </li>
        <li>
          <t>Prose tightened throughout, with no requirement changed.</t>
        </li>
        <li>
          <t>The <tt>Identity-Key-Id:</tt> value is the <tt>alter-did-url</tt> of <xref target="DID-ALTER"/>
Section 3.2, with its key fragment, and the draft's own
<tt>did-alter-uri</tt> and <tt>key-id</tt> rules are removed.  The value may
carry the zone, and a signer <bcp14>SHOULD</bcp14> include it.  <xref target="DID-ALTER"/> moves
to the normative references.</t>
        </li>
        <li>
          <t>Section 8.1 says that the grammar of Section 4 attributes a commit
to at most one Sovereign actor, as Section 4.4 requires, where it
said one or more.  The <tt>type=mode</tt> field of Section 8.3 declares
the handle a mode and names no tier, as that section states.</t>
        </li>
        <li>
          <t>Sections 5.5 and 9.1 no longer let a DNS record publish historical
keys by key identifier.  Key history follows Section 6 of
<xref target="DID-ALTER"/>, and revoking an envelope invalidates every commit
signed under its key.  Sections 6.1 and 7 resolve the key through
the DID.</t>
        </li>
        <li>
          <t>The 63-character limit on <tt>handle-name</tt> is stated as this
document's own.</t>
        </li>
      </ul>
      <t>draft-morrison-identity-attributed-commits-04 (October 2026):</t>
      <ul spacing="normal">
        <li>
          <t>Prose rewritten, with no requirement changed.  <xref target="MCPDNS"/> is pinned to revision 08 and <xref target="ALTER-URI"/> to
revision 04, the revisions last posted.</t>
        </li>
        <li>
          <t>Defines Rung in Section 2.2 and writes the three tier names as
Sovereign-tier, Bot-tier and Instrument-tier handle.  Moves
<xref target="ALTER-URI"/> to the normative references, adds <xref target="DID-ALTER"/>, and
replaces a pointer to an implementation the text never names.</t>
        </li>
      </ul>
      <t>draft-morrison-identity-attributed-commits-03 (October 2026):</t>
      <ul spacing="normal">
        <li>
          <t>The signature is now computed over a Patch Identifier under a
fixed domain-separation prefix and an object-format octet, and no
longer over the tree hash.
The Abstract, Section 1.3, Section 2.2, Section 5, Section 7 and
Section 9 follow.  The earlier statement that the tree hash is
stable across rebase, cherry-pick and squash was wrong, because a
tree names the whole resulting state, and it is removed.</t>
        </li>
        <li>
          <t>A merge commit and a commit with an empty diff carry no
<tt>Identity-Signature:</tt>.</t>
        </li>
        <li>
          <t>Removes squash aggregation of <tt>Acted-By:</tt> trailers from Section 4.4
and the aggregation-race subsection of Section 9.  A squash is a
new change signed by whoever squashed it.</t>
        </li>
        <li>
          <t>Adds the costs of the Patch-Identifier basis to Section 9.</t>
        </li>
        <li>
          <t>ABNF: trailer lines end in LF as git commit messages do, and
<tt>handle-label</tt> is renamed <tt>handle-name</tt>.  The <tt>.bot</tt> constraint on
the three handle rules is stated, and the timestamp rules no longer
refer to undefined terminals.</t>
        </li>
        <li>
          <t>Corrects the cross-reference for key custody in Section 1.3 to
Section 9.7 and the placeholder in Section 8.7 to Section 8.3.</t>
        </li>
        <li>
          <t>Adds the missing reference for the Linux kernel <tt>Assisted-by</tt>
convention, removes a pointer to an Appendix that does not exist,
and replaces a reference to a page that no longer resolves.</t>
        </li>
        <li>
          <t>Removes references that the text did not cite, and statements
about the document's own contribution.</t>
        </li>
        <li>
          <t>States how a handle corresponds to an <tt>alter:</tt> URI <xref target="ALTER-URI"/>,
and removes self-description and padding from the prose.  No
requirement changes.</t>
        </li>
        <li>
          <t>Section 10.2 points at <xref target="ALTER-URI"/>, not <xref target="MCPDNS"/>, for the IANA
considerations of the <tt>alter:</tt> URI scheme.</t>
        </li>
        <li>
          <t>ABNF: <tt>handle-name</tt> begins with a letter and no longer admits "_",
as the handle grammar of <xref target="ALTER-URI"/> requires.</t>
        </li>
        <li>
          <t>An Instrument-tier handle is identified by its <tt>cc-</tt> prefix, per
<xref target="ALTER-URI"/>.  DNS resolution cannot settle it, because <xref target="MCPDNS"/>
gives an Instrument-tier handle no envelope.  The
<tt>instrument-handle</tt> rule now requires the prefix, and the Instrument
examples carry it.</t>
        </li>
        <li>
          <t>Instrument Metadata Resolution no longer resolves Instrument
handles through <tt>_alter</tt>, since <xref target="MCPDNS"/> gives an Instrument-tier
handle no envelope.  The <bcp14>MUST NOT</bcp14> on attestational use is kept.</t>
        </li>
        <li>
          <t>Every tier is read from the handle's lexical form, as in
<xref target="ALTER-URI"/>, and no longer from DNS.  Step 2 of Section 7 makes no
DNS lookup, and the paragraph on its DNS-unavailable fallback is
removed.</t>
        </li>
        <li>
          <t>A handle carries no zone of its own.  The zone is the one an
<tt>org-scope</tt> names or one associated with the handle out of band,
as in <xref target="ALTER-URI"/>, and never one read from the handle's spelling.</t>
        </li>
        <li>
          <t>Removes the HTTPS <tt>.well-known</tt> fallback from Sections 6.1, 8.3
and 9.  <xref target="MCPDNS"/> defines none and requires DNSSEC.</t>
        </li>
        <li>
          <t>The mode handle of Section 8.2 is written <tt>~&lt;handle&gt;@&lt;zone&gt;</tt>, and
the zone comes from its <tt>org-scope</tt>.  Revision 02 read the zone from
the handle's first label, against <xref target="ALTER-URI"/>.</t>
        </li>
      </ul>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC1035" target="https://www.rfc-editor.org/info/rfc1035" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1035.xml">
          <front>
            <title>Domain names - implementation and specification</title>
            <author fullname="P. Mockapetris" initials="P." surname="Mockapetris"/>
            <date month="November" year="1987"/>
            <abstract>
              <t>This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="13"/>
          <seriesInfo name="RFC" value="1035"/>
          <seriesInfo name="DOI" value="10.17487/RFC1035"/>
        </reference>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <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="RFC4034" target="https://www.rfc-editor.org/info/rfc4034" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4034.xml">
          <front>
            <title>Resource Records for the DNS Security Extensions</title>
            <author fullname="R. Arends" initials="R." surname="Arends"/>
            <author fullname="R. Austein" initials="R." surname="Austein"/>
            <author fullname="M. Larson" initials="M." surname="Larson"/>
            <author fullname="D. Massey" initials="D." surname="Massey"/>
            <author fullname="S. Rose" initials="S." surname="Rose"/>
            <date month="March" year="2005"/>
            <abstract>
              <t>This document is part of a family of documents that describe the DNS Security Extensions (DNSSEC). The DNS Security Extensions are a collection of resource records and protocol modifications that provide source authentication for the DNS. This document defines the public key (DNSKEY), delegation signer (DS), resource record digital signature (RRSIG), and authenticated denial of existence (NSEC) resource records. The purpose and format of each resource record is described in detail, and an example of each resource record is given.</t>
              <t>This document obsoletes RFC 2535 and incorporates changes from all updates to RFC 2535. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4034"/>
          <seriesInfo name="DOI" value="10.17487/RFC4034"/>
        </reference>
        <reference anchor="RFC4648" target="https://www.rfc-editor.org/info/rfc4648" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4648.xml">
          <front>
            <title>The Base16, Base32, and Base64 Data Encodings</title>
            <author fullname="S. Josefsson" initials="S." surname="Josefsson"/>
            <date month="October" year="2006"/>
            <abstract>
              <t>This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, use of different encoding alphabets, and canonical encodings. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4648"/>
          <seriesInfo name="DOI" value="10.17487/RFC4648"/>
        </reference>
        <reference anchor="RFC5234" target="https://www.rfc-editor.org/info/rfc5234" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml">
          <front>
            <title>Augmented BNF for Syntax Specifications: ABNF</title>
            <author fullname="D. Crocker" initials="D." role="editor" surname="Crocker"/>
            <author fullname="P. Overell" initials="P." surname="Overell"/>
            <date month="January" year="2008"/>
            <abstract>
              <t>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="68"/>
          <seriesInfo name="RFC" value="5234"/>
          <seriesInfo name="DOI" value="10.17487/RFC5234"/>
        </reference>
        <reference anchor="RFC8032" target="https://www.rfc-editor.org/info/rfc8032" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8032.xml">
          <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="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
          <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="MCPDNS" target="https://datatracker.ietf.org/doc/html/draft-morrison-mcp-dns-discovery-10">
          <front>
            <title>Discovery of Model Context Protocol Servers via DNS TXT Records</title>
            <author fullname="Blake Morrison">
              <organization>Alter Meridian Pty Ltd</organization>
            </author>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-morrison-mcp-dns-discovery-10"/>
        </reference>
        <reference anchor="ALTER-URI" target="https://datatracker.ietf.org/doc/html/draft-morrison-alter-uri-scheme-06">
          <front>
            <title>The 'alter' URI Scheme for Dispatchable ~handle References</title>
            <author fullname="Blake Morrison">
              <organization>Alter Meridian Pty Ltd</organization>
            </author>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-morrison-alter-uri-scheme-06"/>
        </reference>
        <reference anchor="DID-ALTER" target="https://datatracker.ietf.org/doc/html/draft-morrison-did-alter-method-01">
          <front>
            <title>The did:alter Decentralized Identifier Method</title>
            <author fullname="Blake Morrison">
              <organization>Alter Meridian Pty Ltd</organization>
            </author>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-morrison-did-alter-method-01"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="GITSIGN" target="https://docs.sigstore.dev/cosign/signing/gitsign/">
          <front>
            <title>gitsign: Keyless Git Signing</title>
            <author>
              <organization/>
            </author>
            <date year="2023"/>
          </front>
        </reference>
        <reference anchor="DCO" target="https://developercertificate.org/">
          <front>
            <title>Developer Certificate of Origin v1.1</title>
            <author>
              <organization/>
            </author>
            <date year="2004"/>
          </front>
        </reference>
        <reference anchor="GIT-TRAILERS" target="https://git-scm.com/docs/git-interpret-trailers">
          <front>
            <title>git-interpret-trailers(1)</title>
            <author>
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="GH-COAUTHOR" target="https://docs.github.com/en/pull-requests/how-tos/commit-changes/creating-a-commit-with-multiple-authors">
          <front>
            <title>Creating a commit with multiple authors</title>
            <author>
              <organization>GitHub</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="LINUX-AI-ASSIST" target="https://docs.kernel.org/process/coding-assistants.html">
          <front>
            <title>AI Coding Assistants</title>
            <author>
              <organization>The Linux Kernel documentation</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="MORRISON-IFT" target="https://doi.org/10.6084/m9.figshare.31951383">
          <front>
            <title>Identity Field Theory: Toward a Physics of Being Known</title>
            <author fullname="Blake Morrison">
              <organization>Alter Meridian Pty Ltd</organization>
            </author>
            <date year="2026"/>
          </front>
        </reference>
        <reference anchor="GIT-PATCH-ID" target="https://git-scm.com/docs/git-patch-id">
          <front>
            <title>git-patch-id(1)</title>
            <author>
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
      </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA81963IbR5Lu/36KOpzYGFGLhkhKomTK9g6ti82zuh2Snss6
HIMm0CR7BHRjuhukOGP7Wc6znCc7mV9m1qUByHLsbsQq5gICfanKysrrl1l5
nmd91c/LI7dzMitr+nyXH/d9W12s+nLmvq1697xZLKq+czdV4c6rss3P+nY1
7Vct/X7eFtW8bLudrLi4aMubLY/RR+xks2ZaFwt626wtLvt80bRt1TV1XtlN
hb8pn8pN+d7jbFr05VXT3h25qr5ssmrZHjkaRNcf7O19sXeQZcWqv27ao8y5
nP7r3OVqPpcXfTMvPpTujb4IPzbtVVFX/yj6qqmP3PG8L1v3pmyrWVXU7n1/
5173M1xYLmh2R+6CH/EHel9Z8LVjGliW1U27oCfclPzS01fP9/cePtaPB/v7
X+jHR3sPH9nHw0dP9ePjA//t072HB/Zx/wm+ffP8/Yu3Z0cYga3Ni6qbNjdl
e+eaS5rMrJwTTeu+/Ni7923TN9Nm7s7Klq6QdaIHuPM/n7vTctq0MyI8PywQ
6VdJ9BuI1BftVdkfueu+X3ZHDx7Mir7o22L6gShVlf3lmJ70gNb9wXW/mD8Y
rPtiusxndZfPbH75/h6eSk+hkR3sHRziz47eXHa8+Db8E5p9W5d9/oKfuMZQ
Wx58/Pr85Wn+/elJSt7z69L9Hov7e0c/urPpdbko3WXTOqL8suin18XFvHS/
XBf1jP7/tLws27Kelv9zKYvZ5Ku2yjtMJt87/C8h7Obnvjh5kYO263SdVbMj
3ORelFPa5W0xr/5BMkHkxGWF2RP5Zv9jSUkz0GkvMNB8b/+/hJSbnpvx/ZFk
+fbk/Ozk27cpWa9ILFZXNON/L+/mZddBTJ/RN1V9tbN5vs20G9M9Xd+05XhW
3jyYNvyIB53c9UAf+SCd2ENe2ufvBrKovCnnzZJI/bxseQVZOrNcetdWV1Xt
bvbH+1tGYXdOw42gfPLWvUcy7/z89Pjk9cvTs7XJ5xUTdtkSZXtVQPf2dze/
ky/vpgsW2qDCg8338yu/y5+/O/7+/Lt3Ay5+3pa0HvWVK5zoJHdb9ddusZr3
1ZKkgbDsRlFAkzvi1fludbF9XWhE16sLjLCsHyyJ5fO2/Puq7PruwXVzm/dN
90BenJMcqq9K+lOHlBeqJnMeUm5DynVI9M7XJ2+//3N+fJIfn52dnJ2nMzs+
ITUy46kdd13V9UXdb58Gb+bXVb36SGxHXD13NPjVgjYxtt/26X3A1VjnZduQ
zOTZzDB4/9Ix7zvWfe9OT0/O3r3NT14NhmpmhXtVlfMZDwb2wHlzW7QzWpn3
13ddNe2YD78peUb/Xje39X+nTBls//W5V5jz/t74cO/poweLL8aXtAGvC9qA
D/e/eLz/8OlDZfT3x+fPv8tPXqwzOlQPWUe/jb3trizL89wVFx2Luj7Lzq+r
zq+am5WXVV12RDu6xzhb94O7aovFomhZBWYbjDO6vJbPRKXOrTqmeE8MMlEV
OXF2V7ZsK3oyyTN944yMOFxLhg4MFa+jRUCOHVjNRnBR1bPOdXxBSRLK0UyI
s0ds8jUkJ+lxF03fjRy91hE/VzXNFhPsXN+4bllOWdLo/MQ66q/bsiS7lyRv
F2xZEwXu3uR4ygboN3eTkZu8/FhOV+FPiHL660+03ya7Gb8Vj3PNkmlRzN20
vVv2DQ1/eU3vjZ7qLWMW1QW/dDLKwrckzPOTGb8jmND1lBh3sqsk6ew+R+tI
E1ryuDIIo5ezg8eP979wTCYQV+b7+86BGXQ1WNuO8PNNMV+V2YRX3rhlQuvT
0jJ17rJtFvIQiJvoeW5BO4aIvarpWldkl9VHotyMFqKq865cFi32jSPZSj9F
w6ar8Ep+Fv1GWojetixpabOmjt9VzJu6lNXkb9uyY5nG3MVEtq91NNdFd01v
J2O8dyXLdFcx+xx7br4uenIeWlbMuK+jfW9v+lCWS+Z+olh1ecevCPQtpm1D
erUtL4qupBESJ9HuX9VtOReWo69H9KCyJctyWU0/yIgXJNwKngTx34x5kAeT
LUraszYkG03dhNfJzYXr/r7iCVU8qrq81YFmSr+LO3d73ZS8wHIh7yR+A3kC
sBlqXsu2Y2Zry7+VU3oZzyJnRnfmQmU05IbZsRxfjfnFZKXYjpEr1calTUo/
hq3gunnT77qiyxbFnN9XznR9FyUPtOoWPHIS8TfEbG1elyu29eiak97W2jX1
nFyYOuNtb2sZRAYtdjOHSCE2oMESYy9YoPMyimzATXVZEtsQAdWcVPnOyoEM
diwnmxb8GCLGTTUlNlrVTL/CLWn9ePBjkY2LakZvzrLfsa3WNjOSBazLst/9
jv0qMvkX7oz0W8nUybKzZkWmSw7ZRw7XbdN+uJw3t7yYtzxxur30gobWqvO2
wXW1JOJkkP60kmV/W5a1u17RogVRymLNbRZrWSzW2IISg0S24U3Rgn1n5RXt
EahAchDLK5CA6P+yIAHQXGZM7PIjaVy+2C9aBzeHRDtdxT+Y3Gbp6Q0eyGfe
qrR8xGO9rAot96L6eESkdPfvmw1K3NJcXuZE7R/IdPxxfP8+b0gezpzfQlaN
LA09IVYipN3IfLym6cmkeLC/YmkKa4UNRY9IZS8tCV1M//Fzopn2kIHgo6aX
Gde0j/j9zH4s/zBz4SO4fR/KO0iVSTK/o4mbkzrjdXW02jS0VPayOOrvlmU3
DgRScqrVTTohUr35GQl6ptbzeBLFfH5Hz2ctSHeMHFHLlbygxF5YSONolWfM
emT48JhJsbYla8u7ET2h6NQQJYFZyqKvlvOmmHGY5/23fEMHstBVr4sLXHB2
9h2+p9m/bfgTPYfUxXVEquu2WV1dsx43otKK1E3NIydtsVzyGOdlMVO1UvBK
xzzGA2YCC5HO1EdxD5y6JO4H9YGMlT6o02NExIBggdCTO9ptfT4nNUY2SmAa
okvXreg7jOHdyYvn8Rg+lDWmDh7ggEmwUU7LD8wzbVF3xPfk8t+5eXOlgi/i
tjthg64h7pVF4rv9O+bFHSunjjb1isVeg59lI9PzsZtKuh8jMxFKb3lTXelW
N5lhP7KMz4m/iXr2lnGGZYIQ93aN7HhZb1qWPBhSUCutcSfPZ/K8yY8hsCDy
icHNHPwhco5sHYjxSOlzDIreaxdCVLN13UF4qCPCspe/BIcgquaK2YyYqDNN
X/BDyHzrm2YO22YBWbMiEUrEknvdggNf2PWdWhNkANB9xHOR6gA/iML29Jdl
xfbnvU0slIgAZkkWAmyKMrVXFWlXngEtEHkGyrkYHJHrLVkoumRkXBM91Ubd
KDnjDUJSXBQhXTdHKK+o7/yKjsStJDNA7KhSVpIXrhQJDiZZlg15eCOoBzN6
hWpCe1JFnnxewIKKNOyMPC/YNDQNi88yzVp2Nl2wxCrIZzU8Iqnd+YmZWWW2
y7RZ3hlRxMri+CS7GQ2EswjqOxkk3pDd++c/Y3/v559H7qyEAnaH48e7Y6jh
FyWEwLdNMe+2ezBDtwWU5KFcNnPS0LyBrvgJpKv2x8Tt74dWCrM07R1bnilb
KVgd70B4f4a8sLBkkYwJZsjIbZAZfrfTvA54DMQRuchRVjIYwfvVxZxexbKb
bYC2Ihla8U6n9S9nnpdEVrjJXxE9mvho7w8ah/7R8/ul+0HCyT96m939g/mA
veKua6YVTA1PLrX9SFf84EOlP/pVeTh+RBTqpsQ20GoPeRrnqRuFeZzDI5LN
NA1OJVuQvLlbmvaygRzkgfTp1WEb0ZO7I3fmJdY9GEwmqtVT75QxMYdU/5Mp
TsTfHblviP3usWVVN4tm1WH2V7ClhCjkfy7Zj/FW066wdTCN3T3aZpA//vW8
6dx0TmQsde/Ni+kH6Mtds7p4xuRMTMtlr8avUBhDgFSpEorA0aFpE3EfMXHX
TIHYLClEyQSJDi1DC8APD1Qron3uNRAbw7X3GoPjA6sVLB5Y0TgQL8WgmeGY
3g3pOXLvwe2rjkW4Y0lBd3bXcH+y7DGmoc5H3hWXNO6rgs1Zsh27aGxi+qy5
MvzMdW9G+ZRU0LSU5dngzuhV/IStzgxHP1Rm3FTNXEzTQt9OS7Eo2XYi7QuX
FeK6IboQ9ZbLeYVdQELqjPlnKJ1UcpQdDGTWr0MpRaM6/ubtK+xbzgn9OKYL
30gMr5pCkPgZCkOybdIyk7SrOb9cnru+jJH79KsBAX7KH8FVdOVFeV0QIVai
d4RzYXfKGuAjD6RbtZfFVFRnzGCsJ2RgJDRW8MlIEXQsLHWfeoGqRpARxTsk
4zUxzxrk7btzvfXO03M92ORCsIk2Vjm/hKVWsfnno08XLMJNLGIyJHaadtm0
kIUcn+Dt0VqOBwbSN7S1r9rYeAMf9sVHlil3RLc7FmjsBgRxaV4SvS9whRKI
nnnsbprV9FoCMp25meqniuEBsUI/3/HvvG1LMldI3bKrEzlP8E7wMAke8MVT
1vkaHI2vlRmL2dQnRhIEj4uGf4VoUMVGReI22ZrRM0Atc8GqHvMKooelx5QE
QzMjVkZ0CUwgz2EdxVE/MabZV6ZHkUShp7LtwVsKTNjHzPDMVQsyf3zYucNd
5UfiDF48KBTemkownj753DOiQ5lfcL5nlkeDInYpaLJT1nhsva94W1admP9G
hy/GT8bGcRaZe91cJQo+ZwUf4iD8JouIWlyQnr8W2DNCshRx52W7qOqGnnQH
oXJa/n1FDpz4/K8LskpJZ/HegEPK0QeyOXfefH92vjOS/+dNwp9PX/6f709O
X77gz2ffHb9+7T9kesXZd+++f/0ifAp3Pn/35s3Lty/kZt50yVfZzpvjv+zI
+u28e39+8u7t8esdcZbiLcuLQvvkgsNImmphQ7LLzHwAhb95/v7//d/9R+6f
//xfmjb/+Wf9g5Ph9MftdancAuUpf/J+yGiRSxGhpBaJA5dVT/bdiEU6+YDk
ADNnEl3v/8CU+fHIfXkxXe4/+lq/4AknXxrNki9Bs/Vv1m4WIm74asNrPDWT
7weUTsd7/Jfkb6N79OWX/4ZQRL7/9N++ztRuJmlXYYtk2XeiCI84hvHLJJfo
LK9ByMFylMWEIu1IuUN2F3Pxqq50Y3pxoR6cRlCS9Yc8Uh0dBTzV8uSHSJSC
rjsNjtvfV6UP1HrbFgYaCQPavzZsegRbu8HG5Rv42fATzbaZkHmYQ4pMYI+z
t2Uj+ITpyyYNXXpRsB8PogRDOHOxKazSEFEfebIG0GchgC4P/T2Ey7Kc0yJd
xbRRv3fBGtkmLj+RZ3A5gZaHER8Z4+JcezerW12wYpYADx4AwpHvzkAGidMy
RYR4WCzNX9qFz9SfMEUsnvXkl4JsEFKtwThFYEzv0l81EBL0gZk2NGgj1aPx
votj8Dp3sx8xE8Fb8NTGHGZV/RHbemBevbUtaTYdsyGSshJG5QAZOWUrcpka
WC8LfAouAkfpeN4SFdvoKjDjN/NZiKItobIkAkj3Py8kbMLm/ceCFRH5J0ap
EX0q5VtOx8V/59NmXJf9hCZHrsjnTat2wWERb4VTXyHqKz4Lmxbea7E4hfcI
/HwKc3GgOaLItDi05hYIqyROBRuMKxj0iYOkZvAYNIE1smJBn8NZZzJr/Cy6
o6wlmhsTj5WiJxI53934oukTyiF5gm+JeJtTFZ+ioXltI3f8/oSGMFs2FRvT
iASZ/8ZL+8KMzGsi2IA5NARKM2WTyTMA4mrsQmARWK8tYXnOi4tyDoU1ou1Z
9eI3xUH2TEIIZQ0zbVH2BQNSLG4U2Wq2SRbFB5nQXRw9pcFXC7ERWzEWusHI
1RBZI/l0mnsCM3nyfRB97euDzV8/5MV4Dz8iwHgygQiI+KCNU/chjHpZteTw
XSJ1T6IhyTu6PCdeuyAmWUzYMo8z4j9C5cMQJcUv/oVYdVW9XPViOhOBlpDa
PLUrRPEuL3PkC/MlPZ2jpO5L8X++nkjWAGby5aqeWi5CZODWhCeIXHXyQlIL
+SUJPLyoY/dhvprJstLPVSuxr4898gOdBYuD/9WySTeybOFIt+II20gzByP4
njTbxbKLk6G96TtMb9aIEX95yRKNzW+dHCzzj8WM/CUWg7OKg+lH7tEeDCZH
Vky+z3ul6SrOD+ANh4/CjwePDxEMtwtGtpA9AoWJsqcpaZSXDGIRsVcwFg7G
jw/He+O1JfUhJFZFcMHJ8IbGwLA4qYsslpBzQO1nySDjOWgqhZPinSk5PALb
wy6j0fIL4iyxoHkaWDo0A1bkskYhtomIp1PJyeNgBioXS7jokviDhaOsyLfR
W/gb7BJelsjfzgRGy7Ghb0Vf6t5hV5l1aS2pa0AziPO9apY4uIaTNJIEQZN9
OprEOSUfOwlBk0pkl+jsHhkbZIfN20eqchj4APSg5qx8OaOpnK6I74+Q4bth
qYesnsRwpuUmw5BvcPv8mH6j5YDogg9kBDuic49YQD6xRxzoI9h+IqGUglOw
rpEN8tTueohJ93HasYAvJrKqWA/bRkHXNQfuaBLZTfeCwfOIg9dRLMvCKyAU
qEdqTWgVo240jOg9XCERh6I47pJZIMx70J5MeZL0RmwoAttEZusTeJoeS8V8
6M41hiGu5YYYlZ8XUr/iU3juq2rEQwxQ01nApdObLEaPxbZoiQdPk08nLn6Z
LVct7VFJX4NnLFBkaewXZJDR7iiLRRJx0oF2mW50pIzil/lAzoAVs+wnIYD+
+ylNvLpjmIT2myLdHXatfGUq1X32v5+yn/L4X/pX/mu/feryrY+hWYaADA9b
LELNEY/ARJ3N0kdIyX+wrz7fvA2zRMQ9EPYsia+rGWrPjwBWeOtPn28SxoSN
A7/0DMlXjxKcjX9lDOLid/70X2ES0SCyY+/xSXxQQuezIJzn5UfIWZYMCFbQ
/oo9zOBfPjyyvBaL8YnMlxj9g+wlJrDG5JBex0U0qkkWrokoEsJ3ReyYAzdS
lxWjsvBwjHnggfHeY5ieJfK6su85/RA9FNASte9Zc/vwauT9SzaTTUA2wQZR
PIvJsGuOpEVmqSi5r8EIoZ9h8tXlGjklXLnVS+gYl8DDZ4suzmkWczGkO4C1
hrxh8lCiDV1kt2csuTxcm61IDlEhSot0ME05StaEJD2H+vShqv3dvbcmEHcR
vOGsgIjjkL9MMwWJXO3uiI4fWXAiUeyDihuJLOaDI+6dchIaMlFlKI3tl19+
yQrIgIs7A0dj13zldrxs2HFn74OHmOtKvX6VlbaV45vpzniL42Zi5ui2mZIc
GGa7j25LlgL3BRhUdLvHp8Yb/auoEsnjLeUhO6XkS452si1ymjPkh49W7Tx6
ZPwikizsuBhhBhBOeYsg+xnjT8/hu7e869ngSk5WLJZN21scKYiEg+3P4CCR
L8L4UTYlYvNkXWDZJftOe2b7M3Z+t8MyM79siysA3gLwF9bO+nzVChKq2tVk
NB09eLCVtt6vcTv/8aDrrx/skED5O16uUHaiLJErW2MwefkvO7qhc7aGt7zl
WRAoJRI8bocF6A7oYj9tvfei5DoGuAU7JFJ3sohd/b/fOJRkGNk6H//mBw4H
mUxNX7f1CTKMZyJbZ2WP1EOI/sgDJWS49RnD4GgWDT2i0vHr998du737hwf3
9PMD9+KEPEL6/x16C/3veMftbn3NvASSTiIImn/a+evOaABS2Hq/RUYQ5nSH
D7mGgrM+9Mw55wrFjai27YtnsZ9LRhN4oVtdEmXCRV+5f/l48HJ8eDA+fDV+
8uhXyD7SgC85KiRn8q6su0qM4WyT4PnKPT28F4kkHr/bdTtffbVtjz0jX55E
cL8hMzyKHkTmLZkus2zw6GTd1tbqrztZ2MExBR7JhXzZwfDjlnHunIdrjzZ8
zFgwDP995fbvy69BXCTj2Pvu5Z/pAhrs4SP5uJVMEnBgoKOGE9QfC3kRKERx
jLBHinlHRjKTBsUAPA7+IO/hT2fvJyJ9J69fTTh9kqXSPOT6k9C5Om0qJXDv
RTkt1JnJEEiSFEaEGPVw89YPr5dN/PqVu/cvH/eOdwVPPybDFJYYX92WxAi1
oUf4jXiuYllh4QWIL3l1cVrATMgbwwtA4LBT1kcoLAmTSCAQEP9Koiq0YwN2
XKiKDMck0YCTEO8CTWiiq86novjJwbHPSClu1H0hBL3wKRUWTBMLPCwD2jtN
sOi6mPlZu2GFBhmFMjXJxDAFsgs2VDfmLZQYErmZd41P9iSjyoAj1Fezc2Q6
OKR7ssTHl4pBD7hTKKzgGruYHN5Q5OjgsYI+nWYnJXJZhgQa21ut2/nDjiAK
bJU93LfI6MmK4Uvzej5BKzbHtaQdap9q40ErhjWLkWZgJzzAI4eIhZMsHNK/
bP/fVurbMxK56lCPgYHNQvDl8RpDMBjruHbqrhkfVzKMWdUt58WdOBBDRiKl
MPHlq5ry+gP+d6xP+x3bS/tPDp8ckPTY25soVwuizVIS4GIBimLxo+Rdz2Ae
+hEbzrKGmTp7kCLs0kVxwW7k5YJ35MBbi0LgngWiWDMGvHHtls069d13fUza
PxfbCyAUSCCWMIhAKZ3gfWCx6DIfvolzmaXEG1l6BRU5kRjjIOmlEBReikoz
+wrQSmMBDNJSiWPuoFT62JtEe0sKVh7Wa9of8CAhoyprBPIDcgc+07RXVF2E
+7VsTQYPWwNzwcuVBRHTSFxiv5rsDwbfM4vuHbr5oNtmcVF1EJVJ5VLqoPto
LpMnS6K5IWwrdpzfwH57PFFY7Xu7jUhlwUdxDz2uIk6CqKK5bBqWDxfzZvoB
9h9z61VUNkgMdcPCshHYvi/hNamaPIALYhTqHKXMB6+8YJgOTcf8VSbOxbyo
P0BhjbOXkcfrmul0taxKISEUmgrI9L2akyIuziYk04/cH1km8OY9Hr4eog40
7kKUtqjvRNClUYkseYsiEoF/mZfFjWENMCGeNeKM3S6vm9eKmRW/bIh/RvFk
W1ddM2JGAcpnClu0gYKoJEsZf7dGB2GEd4oojPhAlUPKCSEQEco7gEYUSHUU
OGR0c7qRGSg8iKswvHVDQST98Hi8QeNmh+NNwffsjykhNLbh518Jhhvj1NIZ
Sa/ZJDOZljBeOi9Uj66WbLtJQpHNZEat3VTlrdAuhmq6Uxbzw6DNIr4ikbbA
qCHhy8H9ufG9FlNF5ESxBTFkw7m/OhiMS2w3vmc9TbWe0IoDu/aEmPEgkaL6
Q4YH+gpEF+VWaMhWhUgjUHyJjQECMuIEF5ZCN6JVx1XIycm+EpViFsVMUgqK
JSRSJKz069SIMnuCbLCgFHBB0a2kHCTlowsQQRU0f2sjSFmXh/AfZduw3yBE
tjlGg+Badl77PHj6UsGIsi8FK5uw0fgXzG42oiRxuTEkDTJH122OUO9KCnjJ
PkEP5B3X3ShIcuyMccu1SHhYrnrImZxiZCMJdbDYIfTcruyf6XZhJwISQxJ/
FipmeeWr2GCnskirxZUfyDHEf43VsOk4cdNXAE+GIk/iDnrNnHOo8kamKZeC
Vr7WbqNoEYNqTbZIwQIDUPvbJmbZWB/2zVUJYY8yqp4ZieYEyzIBdsavM/DG
Zh8i3n2oz2N6MBSVKy0LevKfrlHuBTSLgB4RWDb88cZ9NqjAEelQfoRUJCsk
pEMfWQ0LKsM4h1ouLtgssvErCzBHrW+s7Slz5ntbSiv4IRcsNs9319bI5Dmv
hIEbfeqYyZFgNIZ6cRjllhYJzBOc8c0fcocMEsEFBhdnDu8NEby5pYJ3NWaH
WEDPEVrmQNH2Q/zxm+O/uEYuRGzfc4A79iD8tfi+/SL6YhNun2ZuwZsftE/U
jwJdgTPMAYvH+wcZzIsaNiwkg2ERCh8CinLpQCrWAp0xCyfTKrR5WV/119sy
M2xe2HCSOCP9kOkPy2veHPrHtP/IdckVmntIjYQUk70v7rjoNEwccg/fmWtO
0pfrqWpfJ1w4gauK1c2qJmuAeswl+UJ2X19GKshDbYYQpcCHB8SHHJagHVW0
4v6p16CmvY7l4VN5uFdgx2fPT07Uccsm2/uWPTB404MbktpiEYgO4s3y9vvX
Oujs4Rf2BsEyH0kS5vALBuQcPnaHpXtCH77g/33yhTuYucN9fKb/HPD3hwfu
yePsiVz8CBc8dIeX7nCG/+DGg0v3ZE9v5F+fZgf46VB+OnQP993eXgh2BSIM
R46xssvp8e1YCWcrIbs0guVENv1FOW/Y3e2bI7f3cW9faowRg+Olo68OII00
Gqc+w9oiypDEr0IoYQ3pBAASIGiMg0CUEwWQoHMa2lADGnPgfRBBouGDqSJ7
tMfMTeTSF/BEdHwD7jUmNReDniE0M+6MW3Ec7tniAx9Ir8nxgrg8B2/JdEXM
YVIMVtjcWlx9p1Jq1ZWJLuCICfa//Mxww7BffJaZ2RJ9GrhGvXFaUIrJlm0m
TM92skMjAw/fSrp9xFvSemzUWURWa1ziNCqYMhDmcYEOPqr7UDigxavhTrAe
z0W37RqXsCN9weEQdbx0X/0aPtD95LaAE2V39IWv7BiAGgMUcTzEIUoYhPzI
1eKC5Qa/CzZ7PQtpdQAFoNn5vvF9hH0uq6uV9lSxylluAJUluMfwtonY8RLk
4/4UUjp+2bQJqFFqwjOhTxTBEM0gdqWfABctfxRKTaUO9buXxy8Aqs+slA+R
ZIbDCS5RmBl09bbDSVQKzNzpX5DZcycMRhGcTiE3SpkQ9w5QvRDIETvrW62R
BIQXMYcPomVreNGJU7lh3SGQ5RfjJ2nk0lsjmyyKhG63O5MfzQjEFswsvAPy
hB5j61hD3WGTCDCr5UUmpnTL8AYp0VHpCo7WvCTfNSi/L8aHGgY6VQSELJm2
kAOxn0vvGQ0Z+65DRLPL1dxVlxARq/amutEQmHYlgQVm8WEySjJ1ISUUUWvN
Jg+Q5JcoCC7Vl60cWZja2kcYZoQ+S+ieAwhHCHQmfQcEyoTFOi3XW/RkaMsj
Yu+yQsrhgr2VaykhWoP+AidqqDjEc6MhOVk0DBm/hroMWrm5xlI36EMJsUev
4eHotgba2bcRUYtaf4uJI32JOHSKCIL3lGK2j77OeICDJkNyCUZuYj5qRKOW
2TbZGtr5SMVjNBubidRsYfIJGpq8fVRRWsiArrGdVs67Mg08ApFjEbnm5hMz
FkUTBFkYK5M0Y5VtW8kukvfPgTnEfivl1UxaIQ+zCMruLQEnGQN6TM+1luwj
yUrJrxelxdkWaw27eh6FgI5UmAV2CwXcC7JjRqGXjLAQMmGef7JbiSarUGdB
e+kbX0lMvzNrFfqiIZ8yQ3Cf9DG7o0lp4yEt8Z8QyyTtDjWveFhE2DvLns8U
aW+1jOu+m9+JAn7q09kjzqV+W5S31SzdBtQtu/N3I6sRhdkhdwFm7JEpzjOf
IOMLzvOIRxT1cggOiAznlZhlA9+LpaxkxCEMo8B6HUOVyRhRU8JgRF9uyNp/
HWxp/6s8XnQKLFh4dtwXOLRYeOzufX/6OodeYNA7SxWtmp8vr4uLst/1cQUE
uC9IP34Q4TBI+mdhajIv1G89PYwG5KEQHdsmHQdA3OQrUoHFDPUM4feR6vS+
6QugvJ8+je8ekEi6y4UwKKwaI5dlT2RVSBW6F74yGFvytNGWkllSSSyBQiux
IwLkDQdl6xmQHVVrLQvYSiRFQzocbB+ql0Jjqbi6KemioTWFpMqyqBiSxxhX
L/uS5riM2aG55QyhE077awpzSx2zwaR9xSxy6JLo7ZL6abOwc9+6yxxx+nVZ
VJZul9lnfvZp2wZpe1i60HQEfnd/HaPkD8f7ljpbj1fFNQidZWGD3mUrXaoV
Mi+7kUdXLQ83PqY7VpSxh/ydYo/8QLI0FYvACq9PVC0aYiqhHbNEVwLX8MKF
W3TD+189VHfY60LJYzQzTsiUVcZfcr7664RjQvcC5/44zM7geVhazp7rXvkE
iaNI3Xo6O/N9JUBhJr9e267Ult/WR89PJDbb/yHpxpJ7OMviSuyxHXxriX6t
hdKXZsUM8XzBviqI4POra7MtbWbMtU4Wplfgr9pUm/AQ1i/BSCl8NkBTjNfy
RqrleEHPXj4XsbzHKFsklQ3dK7n5AQ/Mm+bDaimoCwM9s404jnpMGASjbjJx
v9uSg9X0cNmCWgIRV0geh92lNu8FW5G4TeP5OjYYKESd2wJECpgIEU9nfblE
JwoPLX+S9i6JQOJvrBAx3TObWi6h5RY4H3phWxdJMdw9IaShBCq1m3S2aTyG
I4sQiHT7nRiHQYwXFxpU3/JKckvYpEcRbxY6Nfk4MvfCXBYX1Vz6hTSsZrF+
RZ3CwjPAwtl1HbaU8VhyYNU1p/WM+H+Y5fSdj4o7Nu4rbtARHiam3I1IGyaU
YBTYFPeVnRl7CJL66Mo4vAmZ6Pu2fOP7tiSx5uNQjdUPaKzZu0Fyt+vRRLCO
c7v3779HWpm9pDS1vJZSRi4ltNR2IT+zLQttYFZHlOTQu3XHOo17/qCNknUw
lRq1Du96Zc3RdFxo1uPxrJHksYKMjYUYwTN+uMuZOy4eYdkue1syNbNIiTOR
mC0kcm6YFky105QiQzOciwEC/FIeAo1EcC1o7KbwnHVu5rs3d2L1wBgYZFtQ
JID+rvGj3hi5a3EWyuKBfOvG+KjF+9KVUFmNz3yrQScMYyaumASCG3LbtC7R
3IU7K/tHNzEw9F2UhhpxrEHDGlhyovpm4IBzWxJ8sBvjRFo6O2JyuvW+e/kR
bbK91pOQw0CBeIwWEKTbdbgSJWjP9ZSdX+DPydBxKm6QoZNHbMjSnSA4o00Y
fUTY3sUgojADZYPJqlaazBgGA3qcBrtlUFMaqWUvBrwZLWpBB3e5xcSQ1hqp
3YmXnsQwAXjhmwtzm3ZYYOtcEuDDNLfM7F1vYEKNKP9K1igaq7yIrLKR89Iz
zWKNQmZbeN7cMdwZpfrUBgO81ZykYJp7EsugTy6jWxPL55L4rdvA1slCW6ip
S+iRpvI4xtDaJmdtguYasDL4Ed2mhnLWp+6PYbqJKy+xhA17OHPr7ZAkKb55
o6owCWSV7Y6ylNia9cWeM4QRiikzI6grWXP6UnH8XshNrWW5nKNDG+gVkVTD
FtE66ttUX4EkaIJW+pT8qmOBtuoDTTt24RmrMaNXXrWFKMCwIr/vbIozRHtW
3Xib0jZU1rxrjnxbvalXcHnfoLNVsP1FQwY91nk7s9PikqgTSwyESclSdOio
tJpzMXjA/ID+Hk0zLdEfg4dzfv7axsoiozSJGnwluoJmeYgemAF3uaGNHGs+
pmkureYsuyINDoMJr2+z2PegnaQ+ipaIH4X+Fy53E78JjhLNag/RVqye+7dh
PGTDRgwW7FTtGcMvgzn3yXfBpI3LNESXOt8TNu3QKJ3VzDHwYsPex0i2O24c
Q2/kxMP6S0WqMKRwLv2FeyBgjO5oymAN/Mjmp1Xk3jWKPJbUwnqBa2JupZWu
cEMOMjbNpqRT5QmRcReibUYNdJT2rTXcbAUzskDrePqdLAxiuXfsdqqLEwWl
6RqYx9oogDQ719jweR58dtaGk8kEztf0GuLZXAof9zQKOKVODFDLCjVRIyIL
U0qb3Ah6FjXn5P7c6Y/fNJIT+IdgzDIowGAdaiKA+9YMe6jTDicbvYtsbTbv
0DSZhAqMBKys9voZIRqkbbwQJULwqKsMd+GH2WXDnvOzkkYgwXG6W3rm0AB8
0wzOPbIqMUBK9jfuu4P+p3r2AURN6OAo/pq6OlG/GqtRyDjUldPjsBohINxp
zQGHLsN4o87HM+66nMC770aWGs25peOSJ1N1oB/PEcIYTRj/vmqI5qPs+CRf
FH/TEwYggzqbmF4J2srOtFqMgFfrmMF8JASXwoyWPJFVq0RUEUtPkoOyR+I+
Vn7ifrBGW0Z93wZcIr+p0xYdbn9zXwW/HqLKoCLEfw7SuBv7VCu7bYtVZ9kv
KT1gplXjtGgvKto2bTVH4DI2eOHfho6vsc0l/dlgh0aSirdOWyqwCQjqLHZc
NIpmolVEV2gOQmwdN4aW/cLgEhF0SsNReGPOooFTsnH1ErYLVixULmS6zgpt
tMIk3QZ5WllOa2QeYBYEQ3qRxGHUbT4ajGiysQ6ckxws66Iea0eD4m00RYmK
qdN5omQXl4Q66vjPuKJuUJbK5UHON9fbVubrniX3bC/H/cQD/E1rBbn+9ckd
X9lJNNKB6/49lJYm3+1myZ/RrVbvaFWq9zeXq24rVI3/De/cpbuQDjpOeCk4
hvj2AuXZcYkM9Kke8yA1VnKIR3x50uawV/wNydUv5Tlf/8EClQgmxeFWCcb5
KqK/E18G2VcnrfOIkfGKcaIXrVGg4gv+YBVGdOewbWBmbQM3Xau+MmbIYd7i
Q6mt7KLJZShkjFoueovDGiuatynzMazEHyZZwEyle3lgs2ihVtq5kBuI1ABJ
SvROw92WvSbdo/vbmk+GMp7CNG4mDTN8VU5oXBm8/YeaeAlShWE9A9n0KUmj
MLGQQiBjt+9CQNxQJYXp2CQhFil+jnuKJpdmaxFlZYYDBaa4An2fHaggQVrz
jlN9qIjTRNnF6AZG1Ap6hGTEtUt6O2abChnuRXDEYFrR6NwSp8IBHhs8l4gc
HrSyK7Oo12m+4SWQlEo9VQZGKeA/2PZhQvtX7j4zKjPeVPImigXYUc35xmtY
YCK4D/ccZ9fgXe/0bRvXaSchnoZTA/a/b5Sa6+zUARjRsRkSfrw/GWhNj4wQ
o47zZayXRV9MyYCaa+wwWDBhFaS1CvpyM9A2nIekWo+diDjd8D3maUrcOxkk
BOfzz3E1siiWa5AX4diZ9GS5bFYtm2KVlPho1yg00AHcZG0DY/qwt7BvfSu8
YSYo9KTN4rjXQEhb/EsNaEBPUKE9UA5p6hCnmQxCbMp6IZmRyTPFrlOzmd5N
F3zFT564e5Kq4WQXyW7e4VEmBMfgZHERLmICfN5Zi6onQ+FbNseKSDFqnXg4
FITb+9fVYrVARdOED0KSURyFqUeyV2g9xqUm4L76sl4tvn7wJTlRXw9vM6kS
3A9DqkidSlCrTDvsteRYlntR9H0Uv/PgwcMJOq1pP00Y1JcaVFgrktjFiOXr
7qsvyUflkRZxz7HGD4U41czkILnpXXygETkoI21Z73B8cx4CCTTS787P30eJ
+/999u6tz8nRE+b+UC88/myQ4vYdJLk15aptEZLKLbahpET0KOCmNmZJJf2I
p0mqNLckZKC3MifJlii8G+gJnGECcAgRKwFZRuyU5j/d9vxn0a/nP0XA/DEK
ZmVRDhSFYWxEK9zHJI4h3tnNtuxStlUpIPruq/DiuJ0+z8J3mWYa9sdJXD3e
8XFEnAwCqRgfczbsVWlV4xuVf2ggey8wMveiUL6cEJc+HLuXNXcd9Gu1Vu9j
4agmRuCFzqds92LnlQI53hgO8+lBlU1x2iAN+fqEieLFmjiXZSRhvvZwb+SW
km2kG2fMMWgfgfb2zqrGQKUufH26bNl2l9qUWtKGw5DG2NQRP1AXlE8TyLmJ
XZQ6DvUNhZSFDNlFqDEcA0gZuqphPBLb3hBdMb2OGvBZmtZwbjjM7LZo61yO
65NhunswPZm3V0jjF6t5vztKg720KdATR05SQDFx7ruacZwu96k/LO20r8sO
nXVsmDKLYqqPy3yIHKlu3yuNlDXHyf3kk/C4j41n67FxhvdwvPDlR1JvHRmF
pPbW6W0tUqPt1bl3b1//ZRM6B+3TC/Vm4pq92LMS6/DO+U4GSa2/ZGwtwxaS
3lbDJscAdZ/IZvtq+jUn5IkFT+NmC8JQKmoDFYVtABmQuSM5JPfvpw7HI/Hl
PKhsmF5GBK2qV3ocohRWrymWjInKMM0r2hY4lQ+ekjhFm6xpNqu4C0oIQwOC
QjaG8gyc/PQcOoWkfd7hdDSWBYoaVrVAbNXtIl4sLQwc2cv59yc+9iXHjBox
tZT+OrTuy4YB4dp6mPKJE2KXqJfDupjp70+tkFYV2W3LNnmNyiUuMHYWgDbZ
sU4xzW70vtzAmrYUG0gCSGjLWq01byRWMVWdoVl+zgavNbpYaCmAyLdTkRAa
NTzwcmdWLufNnQrjWw4YXuTLa3LlOwBkJPfhBUbmfx7FSvG6aT50g8pfZS2D
UpItoj2PtindkSv5gbRgkEhlkAQDFfpY0Ee2vGviFypiIJbmWmTBGTv0iLN3
JdrXV355AennC//I+16C0s4GCXLof0lgsye0DBVNQmVtT6tU3dLlN6JwREza
W9GQVRduVDyJ/jPFaoonG0711wYRx+pofZi3ZllUeLQ++wrpvdCGyUe8YgMQ
B0MUg1CJ+IM4NE9Ew7qyq/TwRnOBOSddWSRLA8Xv6uknx5Z9emzuV8Y24tqX
wPphZRV+RV5s00dBqPVJiOuQrVkcEF/D50kGf4GTG+v0gZm3VOoGRQXkSXNR
Fw6IKaX5Tr+FnUdI7mrQfMkzJ1suHLxkTDR7ZvpCU6Gyqzfs4ZAuksCAKVxl
Wjk9SEtkij7DcQ3STaDOI3JqOiU0mpbaa0tZPk/OHNuACiaxyytAsob22RCa
HLXTspPW5VotgwhQCPKLyW2Wcjzf/zZpjwXHIMKGevSu2BTm5XHLDW644R+i
eV/+To4fPqVXmZlWm+9jmdQACgJSLQT2ZIDScLmQTP0oVBlpQBD3WNwkezx+
tKmDVkAiYH7NBZ+tXXb+LTo2tEMD9ERzvOHE4yjiWPQY0cCK9Q4jWghHPcw6
FGBzaSKCsNr9QYsCwsBQmYpA0QonnKboVjnSyJ0tG9oN3PDG0tmfhnfKkm8D
dladNMTwlmp0rofBR48ZYldNKz7IxafRMh5sMb9lYOiyIDdn8Aq3sftHVadn
y5Z3sDrz27aBTNtYvC/t+aJZxkgLjgEmdrmcW5Igg8RRljMeo2SpIqIviq7q
tPgm7jhtkWg0IFQtkhw+LAzbpNDGqBwWxQ28x6V6VBxFjq1w6DNp1R6fvBv7
rhL+uyy4sGy4ggaxLWuthZPottbOkr64JfFhJ7f4coYwbj9Q9JOWPS+PbK1P
YtU7C/NajZvExcHGmZzae4uOeYzjmqIwFq14ski8S+gEN3dky4C15DERlFhh
xF4faG2vjCvc5w8I4oPsU5zAwLiV7fO6EnR/hAVwx1HwKjtW/3pL4asveCt6
xAR92I4P1hTtRrog9C2JzlvaWLizoTOU3hnzkD/FlnMSCpoetJqItPbj8UGm
p2T6AutBvbIGEAGmtIZimo/d3BEzwtM1LXcAhQ9tdy9MRfNxBtx2Q6pjhJJx
MxDaOQifeksuAuFZEkf4HWctI48uDapwCga+9K1zLLN3F6otn8XP1opErxAM
VoezP/jgh+mKbEMndbVN629E95myjNEe4XSPclji2BW3/q0Relo2X7XWApDe
M8QwzxC1pB/og+9WSuJ1SYwzspZfs/KK3h3eFJ09AMgNT3Nk1YOLRvYQTthi
Je/RLtpMSxDYUQei67SOaMa7psatdCliBiPBYMOoER7hyCSU8bPNK6oaVVaU
hUEhyYEpQrYz0FyMZu7O5XE63A0piewVDLAKvblk81TJOfHDrjOavOsaLqMJ
YsqO8C4EmKS2WI0GwHwoQCCpp4yIUqUAcEbi782ry5Jv08P/sua29qeJEtfQ
cC0xuOE0W2lcIz0Zkk4S4dzRgUksJc1lKZHFD3wouo9KZGxKdikCK8qLSplF
gxUQ4HW4FpLVp0jkLdp4I6KB5Xet+0RU9PRMq7dw7oLgbOzyqnO/WjJ4nA1l
BLtQYW/GThi0vgTeSoaRixmPXReNFfEfsWs5zNt3tmhQSwrgFObL9BLwu0Tk
y9obmOtNJkyQYNw+bhYfFKfcp0oCjofu1nBaHeqdV52VMwEH1PEGrZPkO9tx
lyVZfqHxb7bh7LnBluPuSZwBiJtJ+GMxhuCluvFCBFtx3dTRJgxGbuXCJtty
W1z+o+bFWwz4JkAUWcmeVt0H9siszo/b6Nx6XCuiBvPqAgIgZzcFiTpuLf6M
mP2Ss53YKxKbUAIHDEIiGCWMwr1kL8qMvicRwwfRa7O5a+50oiZExHUcTOJM
uHpyaN6SFRddXC/hudxOZR6EYZlpyQ7l/ck3TgG5WDvZUH4SbSkaw0Y/TjtV
hDSmzpjlVyh5MQNYjlHnGBGZ4dnQRgvcdblC8tlI5gnF3vAKDVeDYxNq07l5
GZnKF96Vt1OdGe0WA/qSIGNokvQMnue8JB7VyKomqyUNLbjHIhJ7GZfXtOJz
SgQkkqxpeGmUGH+ZGX2fOJjF0kNRGQLLIrG6s1hKRhJHRgxPUGg744Xw9hzZ
937ea9TiuGS0DVzUGtWXI3plgIyTeGOJ4V6EauTYoAsyHH72lIjEfTnvtJ1F
03zQPiXoHrFBqLl7//znm3enpydn797mJ6/Of/55dwPxtMno8rrl3bcOZQ/1
CWs+l+DTikzt1gj1WLYL28bQ29yllAwHOGUjNf+kOY/qM+uX8zupoX7fVMSE
8ICPWQeRvdZxTxf+bWm/yVmVH5LaigHgIdMNMUVtAFkocq5qCEZK1weSW7S+
DPiMyoawlqCrvAdlccDsNnMrjW9Z7DGAmYTQlTa2hzWsVbqhNnfkk/9JEfl4
3xfSqpImu2lVK0Wllpm3orZb1mRJ/NhBPjkn/9a6SvTr53+HxhnxmXGfOP97
rVyMn2LYez5O3vy0S3Yqw2mG6UrFDaSm19reeVjC9Jz8FXBIlm09jZFHu3bj
2vmMmT+f0URadDojB3HQz60anEQKCNZtydC+coaTk6Y2IrYyKj2x/h7d3aPr
ysgd7O0/8RAeHYG+u4KwBnaRtrA/xtNjrFXuVZpJkxGZ5mHmyrwEEfwzW0XF
/I5Nv2vSrdc4YVSOBmm0b+9q2vuFsaZG/oVoOrPeZWrgGoYzwTN2yblruy9u
G7qDGLR0rrctAhEnu23WEG9k8tkEc9wVR8cnInPNs1SsYGRFCvAk6jlZSId2
poytmuXRYuWd+UofiIJIUGJlCqgyK/tdb9EGXy2bNwzeKlakS3gHYNMK7Oiy
ElRdQBMm1n8t4RsyVabX5ZSt0FhcaecJ2RDPQ1ccHUgeDeQbDmFlWdz/Sil4
rT0GA/5aItsQyV1v/WaPtT2RRTsRhNR1lzqs0Fk87mOEXkPiQ2vgSQKz5CX7
26XZlvYvCi0upaeS76bEbn5bhqznKD4/ZEMHp5AzXpahVZPTAkvrJSREEHvw
mizvwGJoxS7iiCdhQht9h/mNcCOIAdg4vIsOFgithx6OIi84pKbYEnODeJls
jvVmSOIP6xqcB+azEmTrQizNrHgZvvkEUbhdNIrQNSVmx/NGf6QtE7XzjfQl
k5pA6xllxrAP1RtfpZuQHSoD6gn9h9EOlDSnMRF7t+c9aQcmg+B2QHG9WMp8
g8Zh/IcpFYxcZj7XA0O6pNnVaGu3K8YGDVqObVAk4kJJL8mwN1QeO9W+U+7H
5ZOOODRFmlUoei+0c/MQo/qSrIoemD3f9sS6kMHo5W6KQqpvq976QIy17fOm
bnpyqETJ0DDtgslxoOuK/K1lETW3JtsUyVv1fVnk+YigHk2R9OSjp6x15UtT
K1IJLIf8eBYyCFzmknplAazYMa/sDGyPRQYrTLenAoAQX8tzyVhOkN4ceXAJ
n/Hb6ZLCmLbmkzHHRHRRIr+L+3l2ns5xSzbilUd7m/q2anDrc86nTsSA6E8x
eH+PASKkAP3M9l1KcNR/29+odS5DQENVie+Oqn3PfUvTNHKsrTR9t9QIQBl8
X+krrgSRdvfS5E8qHdQGtSaIQsW38bmlwPi1V9JwTvpsagGTbu+kMyWYIPNF
35JJrPU+7Gid8domlX1XtYNG2a3GZyxLXOIEA9EadhjAVMNNJg/SGkTfHcn3
/HouPbQsBCswmNw08DesPYr2zncjzs2sYNdMcMxkXFxxSo2DOFeKekaIcleX
og65Wcs7eLy/mNnIaIUD2ERp0WutdxW9LENXJWWwVc0JChK+Vwg9SEyplc5f
XactXO6EvAUcq0w9/zi9HCU5tvqMjvR6LyZa7FAULhrAdTnnt6dQ5oIGiZNp
GAqQdQ3xMvd75aOVtVaRxBrDNzTXBQ+iKBfs7iDaybbvLaPIeDeVaN7PAVKR
TH8qLxhwVLv3p6924+I2g9Bjx8RZHPEK5+qCJQQ0si3o7aD5C1yb8W1IC3gI
XbmB2JVBh/yBPajg7++W6HkbV+EDOjzn7OxqifR5fPpXiIlYKalto2gHWKT5
lpbwWlFrm2J1jmN1WVouWdxFATo2mzR1u+3wBQ6ncAv0ksTi8Um+JclXCfI4
FP9GFphUWYMuCKpe3MXt8kJwJjLy4ypgUnfqRKEhAtnidxAN0hSMhjSrOtbT
kEzk0l8p50IUJsdOIR3SllerufBbc9nfShM/rCYmopZst6tnHGjMBDAiZE9m
JiP0AHoZjlZsz8r83ENK3jZ1/jLCkUSoWMW9vhC1J2JFEW4eFvj7LtS8i3Ll
nbUGYYE0zHx1qopFwVhFYe0I6cIaJTqPHXvkjwMYlQV344PgDK2LJmHp/Rh8
5uF68RNCkCvGgckgSDbgeAmPc8s2g358JQLvoZz7MMshTeh4LYAv6ft1F2eq
veEQ8G2wkwTjNjIkXrfeymYzFG8ADjIT2lM26Oh18JTtWO+dc9YnBhnRp9sC
hQp4gnooA4C0YBu12BmXBLg3b24eBRp6lreIZxUmrdbw21zJ5VHrnbsXOhtw
nb9Gc9UVRnMH1Y8CYmNrfBcGPoIB1+tcCewBB/UQq5bKdRbo0l4RwRWpF59q
bCt4koNGJJmArU0yeGj21mO7BV+iBkm2nj+xIVo0gldiDdTGQJQIRqPcxaVm
rLqEh6MODwkfeKTNWSlYyxTLura9fIEQuBsdZSNBBui7ovPi6Lql5/qNYL0G
p96g49xWkBwwaifHb4834dPYN7Fzwd8yw56WVxWfF6VAC+1rqDlUBhLD18Dj
IixKZZ2xW7kdsX8+DsEwQ3EbT2kW5fOQegOXxoQysJFkCHzAjEOtsAfbaHxr
sIj0PdL9YFAUNWxFIIVixjQT/iPye/F3rDDxxTrqJP1aUCLpdxJ7nXBtR1/N
GR/EMmce5i8m/WiQauBl5TMRZ52meWwrsKk/bRDGZ372MUHxRlDiLjskihto
7XfsvLEgYk8REABl0OgE7tCyRBcywel8f3rizhiPWpKK07bHlRxHFs+BucZ6
kX2y/WjhwsGXE3QtjbuxquMsJd0TvLyTl1cqTFfiAxJXgD+nCbsPDkN8NiA0
M3Mmh0dJ3fb8TtcGOAbrUJseN56MYtWFYuvPaVldRZTXIGcYzkq4JEvYXVhk
g0DkTstIcEMCbhij7AVp92OzKmc28kiegoW0wRVAhs2yoJ2XhV2E9p4+pIw8
Orl4cT2d2KmNOrxYiuOpipzzAXfrriavsAlXS1FGJ810yrlMktQ57+CXVjpy
xsXPJM+7zW1zEiavOp90l9C6GI048oxcg8YOUMtj69u7jzyQn9wb+3N7B4af
3HtVHJ/37yeSyAKFYMJG4GISUJ/5iP/sv5+yn/LP+PdZF/0nrv9v+Eczg3ab
yBFQ5IeQI3I3IZHy/N2P8Rq8Jo9qHhfHDhscuZbdr04vf9fSRrrS5gdbuwcM
Xqsh1UFDzZCG+20rhnlFEGec7jeJjujOzya7zF2b4arcYfrb998+ODv7LnKW
Gxiun5rfRSmTo3tza77NcWKvPPXbBGdh5/Sy+QiPogrJTLgDGydIxOM0Suke
sBWBfrecQDw7+fatX7ufOKKD6q8tsFye57uTF8/t8uN2ylHDKSlsObps9jfy
C5B2eOEjyP5u6+ErrazcPTzpX0kefSBxcdOlPc1ZV/2rM1n/urnivPwbHI6M
DT62ia0XT6V1ZBjo+zn3ikGmZdrkqtFRZLWRIdIlG/r31pFzS+NijT6sj0vv
i9Aj3IefHPNQRbaF+8eY6euqXn0k/mprot7kuOsA+ZIt+Prk7fd/zsmnPz47
Ozk7/5Hm8MJ791r7GUli2o/HJ4w7sIRtVduDk0Zkz9wce3leWXsBK8vTugaU
oYEvSAjQlklFw+4neETOS2m83kXkKJ4VIKKYAlGNRjuImhA3kcObFMA927JU
3neMH2Hh1Ajq7ruY0Ui+4X3Jq6AHRxrSNxzIyItC6vR4yrDEeTlDY1nVncph
7Eh+6JAiL4srrsEkg+AY4fY3tJ9nFb3/PRH1dR9MxctW+pMwwNLD4St/drU/
FkPxwVKjjTi5HnHCF0ttqmlu7yKibLWXk+D/5rvNz6WFuHthRsR3knHN/nlU
r9jVLWdf7QB8v/NzluGQ03zRkFtOXJxvPzmvy/cecxfrG3GXD/YODnfJN7jv
w+7744cB/QY02w1nqBQ5IXzZN+LcJ2ypp2xKuj+lkvnDchKOmTASDoxRpm+b
0BxiETLtnaW3gnXGo5kJtvC+e9/CiWXthVS6xnPJDBz55m/rT5V7zzdb675B
We9t8Zxs9nzVzifDIwNCac1D7lyLNw5bG4eIAFbKd0llRyCXx6/aShOSfOx9
NZvY2faAiiKxrb6BDG5R8KGv/hhQhdwooEPS3dYkWmtaQeO48ocfinyOhNH9
yfOB0N045o2n431ptu5Ty7/WvTE6NxmtQj7VpTFuuPbI97QwKB6e0RU40r60
LnzmLIUGKOHEuLhu0LqbaH4uaYsizGWHMCi76hQtsCEbIqZF5x6PH+PWL4go
IfU657MIk9NOpNBCAROM1ZGmJB07Q2lXED0MxQ71sHNsksKtZAHtjJSbBkfR
FREUd72KzS9EUi2mjBrqwzp0FOHnPokP19ATE7CxlIo0Dr+FDh/m/sAa6XLA
snkSNambaPGmoqZ7yUubiyQbYvzbBNkjslaId1I5JsKgLbUY/NMSIDpGgiuL
q7oWz8l35Nl7ClLEnd16EVJ2waORwiZutHBrXnAUt2HJD/K80EMdEDaLMBoH
4wPpchbCBtIHB6pAzRKmUdqEfhS6JPDdm60dtsp0b6dD37rPR9LCachcmKqd
JC4JQOnsxCI+8c5lAmzLSfrVDgP5TSv6cNOKnicQFgROb8M5l1q+sIaI0Hgo
p4ZxvK12JtSwB9KZcuinOixbz7yteb11dzd2epw/so6bAvMAjy86NLgfxYp0
FC92+ONx+PhEieyBO7rrre2/1mJi34Tai2QEggrqFG4Na0KRKMkBfYLEluPp
GCJwyweSBRxTYYVGw5P2BKkgp1dIhN7jL0wr8SJtypJ/Ikcuaguk3Vjchmee
4vmdjbq4umoNsR7374s74yAPGqkRNUoQ7gm35y0DTaLAdaQuvpBDPuWVbGYw
Xqq8NbSWCs+LO5+bl0s5d9QLJWb+RM1PoeKksJN2Ungx7v7m7asjbyIJGEi7
er5+xYIzcn8VNsWBJtusJnEBcJ7IIgmWP5HFpje5T+hEIZgc3HYw44IoSno3
evkdnW1bLTiasFjqJeE4WyeyBZ3BawtSyckhZLNiqs+lyU0XWcHBwGPDO87U
RIKTLVQI4UC5J35EkFVa9hjd85QuiWgtLSGjtUJhB/F4OgD+Zbt/BxAI6dva
UNLCrUMxebzkMAAJmrQDCvxlO5o+krFJHJ8rQa7CGZIqhVQtd8kmCaI8khEs
jq2Qb1rZ7vXShAVHwACmujhNf8PyEa+AIby+r2naiBSBnzhwHSmfMFXd1OX8
Mhd49NJ3gdCj8QK4B/7kJzyDxDzd3yOVCuLDpYtfDgqYrh/5xeUwrCxjHEG3
otf1EHy0RVPbBj10vf9NRmC/BsrT5qY7f90BKZIGfZEZHetrs4HltVtDG1UX
jMiZb107neZ2GKCcBpbYAmOnRmpA9WlVPtqposrFdIM/2cxZW9utQ0lPnjoX
0GUAWeTWkJzFBfR4aAV4HU73ts0cXsLgPutZLrpDpe2nD9jasGnSh1pLAoMA
WbcSOyx5cLjWxpOEtk09QGSawdlXKKir2PBeyixe/vae/yhvS9d0NOA4PIK7
9TttcpV0vvLnYWXxORaB+GwnIdbIw2eO4kjgqi5uSDVJcKeYzy+4jAUGSGoM
mHgIhzdri2U8iU39QVvi61Jheswww4aeVkjymWffyfZK82CjqLlxgzZOG2ls
7Y4T0cpXoEckKcxb+j3n2FI9CQSIrQ74TyPWMCrwvth8WJ22W/b8L3U33qGK
G0slzuwBk8s6Xa13ojZDwCICbCuUXTiZK6KttD1RN+bA+RPScRvfkHjLRBwB
qMC0GPligFimZP8fmA78BPLOAAA=

-->

</rfc>
