MIME-Version: 1.0
References: <1a059195afd.4565299a1665355.5803749020539612109@phionyx.ai>
 <CAOfgHgozu3Zkfa_8xLL-_819UXa9+AHWyzmgJqECrJrdHAMqrg@mail.gmail.com>
 <1a059647c95.52b5c00d1669474.5350363334433611579@phionyx.ai>
 <CAOfgHgqo59hP2=ETw4_tZ+7V+_NofFA0CzDx+VPmkasNaQuPmA@mail.gmail.com>
 <1a05b083a92.194b8edc1680092.2192186531592395387@phionyx.ai>
 <CAOfgHgpoPMzgjph+8iiu1GCbCbCSQrU0CLXCSwPfNRdRoeeseg@mail.gmail.com>
 <1a068aa9c84.628acde8302609.9037848624334984897@phionyx.ai>
 <CAOfgHgp=SPxXRjgZpDWtBL1d-CoV4+UMyiEDJbMUjqkZd+PGHw@mail.gmail.com>
 <1a06920a8e5.48543f44307536.277778572727460648@phionyx.ai>
 <1a0693c482f.8787537f308350.3610854305484865878@phionyx.ai>
 <1788476568800716144.1788476568@conarium.dev>
 <1a06a611813.c6c0a25312932.5215504566405879891@phionyx.ai>
 <1788531190678629118.1788531190@conarium.dev>
In-Reply-To: <1788531190678629118.1788531190@conarium.dev>
From: Walter Hawkins <wdhawkins46@gmail.com>
Date: Sat, 5 Sep 2026 00:12:54 -0500
Message-ID: 
 <CALc05oFS9S3NFZ6AMo67as1o4o43XCSJxARSNhwR1ohKC-Vz+Q@mail.gmail.com>
To: Emek Can Dogru <e.dogru@conarium.dev>
Content-Type: multipart/alternative; boundary="000000000000ac160d065ab57081"
Message-ID-Hash: 5BEQSKBIO5TJGGRABAAUFV63J54AD6OR
CC: founder@phionyx.ai, team@emiliaprotocol.ai, scitt@ietf.org
Precedence: list
Subject: =?utf-8?q?=5BSCITT=5D_Re=3A_New_I-D=3A_Evidence_Requirements_for_Agent_Contr?=
 =?utf-8?q?ol_Delivery_and_Outcome_Reconciliation_=28draft-abak-agent-contro?=
 =?utf-8?q?l-delivery-evidence-00=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/scitt/CiAlVgCWAuLQJjyEWExLl-ZrysU>

--000000000000ac160d065ab57081
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Emek,

Congratulations on publishing draft-dogru-cedulon-decision-profile-00.

Naming `effect-against-refusal` as a first-class reconciliation failure
mode is an important contribution. Existing payment and spend profiles
almost universally assume non-execution under denial; formalizing rogue
execution against an authoritative refusal fills a genuine gap in the audit
model.

Regarding your IANA registration question: your reasoning is sound and
consistent with SCITT/COSE architectural practice.

If the Effect Extract is delivered as an application-level detached JSON
payload rather than an encapsulated COSE structure whose MIME type is
parsed and validated inside an authenticated protected header parameter
(e.g., `content type` / label 3), registering a standalone media type adds
registry noise without cryptographic or protocol enforcement. Limiting the
formal media type registration strictly to the COSE_Sign1 Decision Record
keeps the IANA parameter footprint clean and avoids encouraging fragile
MIME-sniffing downstream.

We will run the conformance suite against commit da7bf9b and review the
interaction with receipt-invariant checks.

Best regards,
Walter

On Fri, Sep 4, 2026 at 9:14=E2=80=AFAM Emek Can Dogru <e.dogru@conarium.dev=
> wrote:

> Ali, Iman, all,
>
> Following this thread, I wrote the decision side out as a profile on the
> Cedulon reconciler and posted it today:
>
>   draft-dogru-cedulon-decision-profile-00
>   https://datatracker.ietf.org/doc/draft-dogru-cedulon-decision-profile/
>
> The population is the one this thread has been circling. A Decision
> Record is a COSE_Sign1 signed by the party that decided whether an agent
> may act (allow, deny or defer, with the request hash, the policy hash
> and, for an allow, the reference and the content hash of the effect it
> allowed). An Effect Extract is an authenticated list of what actually
> occurred on a channel. An allow must be matched by exactly one effect
> carrying the content hash it named; a refusal must be matched by none.
> The finding the profile exists for has its own name,
> effect-against-refusal: an effect under a reference a refusal names.
> The spend vocabulary had no word for that case.
>
> What is measured and what is not, in the document's own terms: the
> profile runs on the same reconciler that runs spend, and the spend
> behaviour is held byte for byte by a fifteen-case golden file; eighteen
> conformance cases and four offline fixtures for a direct-message reply
> log; the live log's field names were not read, and no independent
> implementation has run it. Before posting, the draft was read by an
> outside model barred from editing, and the code behind it by two; what
> those readings found is in the companion's review log, the code defects
> each with the test that was red before the fix.
>
> Pinned commit: dogrucanemek-alt/cedulon@da7bf9b. `npm ci && npm run
> test:pre-release`; the cases are tests/decision-profile.test.ts, the
> fixtures interop/mizan-ig/. Same terms as before: run it, try to break
> it, say what you found.
>
> One registration question for anyone who has been through it. The
> profile registers one media type, for the Decision Record, and none for
> the Effect Extract, which is a JSON body with a detached signature; the
> reasoning is that the core registers names only for objects whose
> content type is checked inside a protected header. If that reasoning is
> wrong I would rather hear it before the six-type request is answered.
>
> Emek
>
> On Fri, Sep 4, 2026 at 6:05 AM Ali Toygar Abak <founder@phionyx.ai> wrote=
:
> > Hi Emek,
> >
> > Thank you. That closes the focused review on my side as well.
> >
> > I also have the pinned reproduction file and exact invocation now. I=E2=
=80=99ll
> run the 0.8.0 and 0.12.0 cases independently from clean directories and
> record the result separately, without changing or repinning the historica=
l
> 1 September probe.
> >
> > I=E2=80=99ll keep the distinction explicit between your reported measur=
ements
> and my independent reproduction until that run is complete.
> >
> >
> >
> > Best,
> >
> > Ali Toygar Abak
> >
> >
> >
> > Phionyx
> >
> > https://phionyx.ai
>
> --
> SCITT mailing list -- scitt@ietf.org
> To unsubscribe send an email to scitt-leave@ietf.org
>

--000000000000ac160d065ab57081
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><font face=3D"tahoma, sans-serif">Emek,<br><br>Congratulat=
ions on publishing draft-dogru-cedulon-decision-profile-00. <br><br>Naming =
`effect-against-refusal` as a first-class reconciliation failure mode is an=
 important contribution. Existing payment and spend profiles almost univers=
ally assume non-execution under denial; formalizing rogue execution against=
 an authoritative refusal fills a genuine gap in the audit model.<br><br>Re=
garding your IANA registration question: your reasoning is sound and consis=
tent with SCITT/COSE architectural practice. <br><br>If the Effect Extract =
is delivered as an application-level detached JSON payload rather than an e=
ncapsulated COSE structure whose MIME type is parsed and validated inside a=
n authenticated protected header parameter (e.g., `content type` / label 3)=
, registering a standalone media type adds registry noise without cryptogra=
phic or protocol enforcement. Limiting the formal media type registration s=
trictly to the COSE_Sign1 Decision Record keeps the IANA parameter footprin=
t clean and avoids encouraging fragile MIME-sniffing downstream.<br><br>We =
will run the conformance suite against commit da7bf9b and review the intera=
ction with receipt-invariant checks.<br><br>Best regards,<br>Walter</font><=
/div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" =
class=3D"gmail_attr">On Fri, Sep 4, 2026 at 9:14=E2=80=AFAM Emek Can Dogru =
&lt;<a href=3D"mailto:e.dogru@conarium.dev">e.dogru@conarium.dev</a>&gt; wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Ali, Iman, =
all,<br>
<br>
Following this thread, I wrote the decision side out as a profile on the<br=
>
Cedulon reconciler and posted it today:<br>
<br>
=C2=A0 draft-dogru-cedulon-decision-profile-00<br>
=C2=A0 <a href=3D"https://datatracker.ietf.org/doc/draft-dogru-cedulon-deci=
sion-profile/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.iet=
f.org/doc/draft-dogru-cedulon-decision-profile/</a><br>
<br>
The population is the one this thread has been circling. A Decision<br>
Record is a COSE_Sign1 signed by the party that decided whether an agent<br=
>
may act (allow, deny or defer, with the request hash, the policy hash<br>
and, for an allow, the reference and the content hash of the effect it<br>
allowed). An Effect Extract is an authenticated list of what actually<br>
occurred on a channel. An allow must be matched by exactly one effect<br>
carrying the content hash it named; a refusal must be matched by none.<br>
The finding the profile exists for has its own name,<br>
effect-against-refusal: an effect under a reference a refusal names.<br>
The spend vocabulary had no word for that case.<br>
<br>
What is measured and what is not, in the document&#39;s own terms: the<br>
profile runs on the same reconciler that runs spend, and the spend<br>
behaviour is held byte for byte by a fifteen-case golden file; eighteen<br>
conformance cases and four offline fixtures for a direct-message reply<br>
log; the live log&#39;s field names were not read, and no independent<br>
implementation has run it. Before posting, the draft was read by an<br>
outside model barred from editing, and the code behind it by two; what<br>
those readings found is in the companion&#39;s review log, the code defects=
<br>
each with the test that was red before the fix.<br>
<br>
Pinned commit: dogrucanemek-alt/cedulon@da7bf9b. `npm ci &amp;&amp; npm run=
<br>
test:pre-release`; the cases are tests/decision-profile.test.ts, the<br>
fixtures interop/mizan-ig/. Same terms as before: run it, try to break<br>
it, say what you found.<br>
<br>
One registration question for anyone who has been through it. The<br>
profile registers one media type, for the Decision Record, and none for<br>
the Effect Extract, which is a JSON body with a detached signature; the<br>
reasoning is that the core registers names only for objects whose<br>
content type is checked inside a protected header. If that reasoning is<br>
wrong I would rather hear it before the six-type request is answered.<br>
<br>
Emek<br>
<br>
On Fri, Sep 4, 2026 at 6:05 AM Ali Toygar Abak &lt;<a href=3D"mailto:founde=
r@phionyx.ai" target=3D"_blank">founder@phionyx.ai</a>&gt; wrote:<br>
&gt; Hi Emek,<br>
&gt;<br>
&gt; Thank you. That closes the focused review on my side as well.<br>
&gt;<br>
&gt; I also have the pinned reproduction file and exact invocation now. I=
=E2=80=99ll run the 0.8.0 and 0.12.0 cases independently from clean directo=
ries and record the result separately, without changing or repinning the hi=
storical 1 September probe.<br>
&gt;<br>
&gt; I=E2=80=99ll keep the distinction explicit between your reported measu=
rements and my independent reproduction until that run is complete.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Best,<br>
&gt;<br>
&gt; Ali Toygar Abak<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Phionyx<br>
&gt;<br>
&gt; <a href=3D"https://phionyx.ai" rel=3D"noreferrer" target=3D"_blank">ht=
tps://phionyx.ai</a><br>
<br>
-- <br>
SCITT mailing list -- <a href=3D"mailto:scitt@ietf.org" target=3D"_blank">s=
citt@ietf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:scitt-leave@ietf.org" tar=
get=3D"_blank">scitt-leave@ietf.org</a><br>
</blockquote></div>

--000000000000ac160d065ab57081--