Answers are grounded in this paper and cite their sources.
Specification draft demonstrates cryptographic reconciliation between authorized agent decisions and recorded channel effects, highlighting mechanisms to detect unauthorized actions against...
Internet-Draft draft-dogru-cedulon-decision-profile-01, Cedulon Decision Profile: Reconciling an Agent's Decisions Against Its Effects, as posted to the IETF Datatracker on 4 September 2026 (submission 168602), with its XML source and the Markdown it was rendered from. The profile defines a second population on the Cedulon reconciler: a Decision Record is signed by the party that decided whether an agent may act, an Effect Extract is an authenticated list of the effects that occurred on a channel, an allow must be matched by exactly one effect whose content hash the record named, and a refusal by none. The finding this profile exists for, an effect that occurred under a reference a refusal names, is effect-against-refusal. Files: the plain text as posted (byte-identical to the IETF archive copy, SHA-256 555d2fe2294670d49140af1f54c39ca61865488dc6e07f7971b9a7386a227116), the XML source (byte-identical to the archive copy, SHA-256 88500296d537343a05f8700aeaf7f3b1a99735a52c6f7f11dcc2c63de96eeab4), and the Markdown source, all taken from commit 06c3119 of dogrucanemek-alt/cedulon, the commit that recorded the posted revision. The companion implementation carrying this revision's claim set, with the class of the effect under the signature and the effect-class-mismatch finding, was published to npm as @cedulon/*@0.13.0 on 4 September 2026 (22:51Z) from tag v0.13.0, commit 3637b62. This is an individual submission and a work in progress; the text calls its requirement language provisional. External readings of the profile, including one frozen leaked-refusal fixture read by this implementation and by a second, independently written reader, are recorded with their digests and their limits in docs/EXTERNAL_REVIEW.md of the repository (Round 10, commit e26f50f). The Internet-Draft text is subject to the IETF Trust Legal Provisions (BCP 78); the repository it is taken from is licensed under Apache-2.0.
No takes yet. Share an insight, caveat, or question.
Emek Can Doğru (2026) studied this question.
Synapse has enriched 8 closely related papers on similar clinical questions. Consider them for comparative context: