Non-Collapse Requirements for Evidence-Bearing Agent Systems
draft-watts-agent-noncollapse-requirements-01
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Author | Deonté Watts | ||
| Last updated | 2026-10-31 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources |
Additional academic profile
Author GitHub account: DeontewattsV1 Author ORCID Author research profile Research archive profile Research bibliography profile Research discovery profile Research standards and metadata profile |
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-watts-agent-noncollapse-requirements-01
Network Working Group D. O. Watts
Internet-Draft GoodShyt Group Inc.
Intended status: Informational 30 October 2026
Expires: 3 May 2027
Non-Collapse Requirements for Evidence-Bearing Agent Systems
draft-watts-agent-noncollapse-requirements-01
Abstract
This document defines architectural non-collapse requirements for
agent systems that consume evidence, provenance, model outputs, or
other machine-readable claims before consequential actions. It
requires implementations to keep integrity, provenance, evidence
qualification, authorization, and execution as distinct states; to
represent unresolved required evidence explicitly; and to preserve
issued evaluation records append-only. The document defines no new
transport protocol and no IANA registrations.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 3 May 2027.
Copyright Notice
Copyright (c) 2026 IETF Trust and the persons identified as the
document authors. All rights reserved.
Watts Expires 3 May 2027 [Page 1]
Internet-Draft Agent Non-Collapse Requirements October 2026
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. Normative Non-Collapse Requirements . . . . . . . . . . . . . 2
4. Three-Valued Evidence State . . . . . . . . . . . . . . . . . 3
5. Append-Only Lifecycle . . . . . . . . . . . . . . . . . . . . 3
6. Typed Promotion Boundaries . . . . . . . . . . . . . . . . . 3
7. Relationship to Evidence Qualification Receipts . . . . . . . 3
8. Security Considerations . . . . . . . . . . . . . . . . . . . 3
9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 4
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
11. Normative References . . . . . . . . . . . . . . . . . . . . 4
Appendix A. Changes since -00 . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
Agent systems increasingly combine identity, delegation, evidence,
memory, policy, and execution. A recurring failure mode is semantic
collapse: a property established in one layer is treated as though it
were established in another. Examples include treating a signed
object as true, a supported premise as authorized action, or an
authorization as proof of successful execution.
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Normative Non-Collapse Requirements
An implementation conforming to this architecture MUST distinguish at
least the following states: artifact integrity, provenance, evidence
qualification, authorization decision, and execution outcome.
Watts Expires 3 May 2027 [Page 2]
Internet-Draft Agent Non-Collapse Requirements October 2026
Integrity MUST NOT be interpreted as proposition validity.
Provenance MUST NOT be interpreted as truth. Evidence qualification
MUST NOT be interpreted as authorization. Authorization MUST NOT be
interpreted as execution.
Where a policy requires qualified evidence, missing, stale,
unresolved, or type-incompatible required evidence MUST NOT be
silently treated as satisfied.
4. Three-Valued Evidence State
Evidence evaluation SHOULD preserve PASS, FAIL, and INDETERMINATE as
distinct states. FAIL indicates a required condition is contradicted
or violated. INDETERMINATE indicates that no required condition has
established FAIL but one or more required inputs or bridges are
missing or unresolved. A policy requiring PASS MUST NOT accept
INDETERMINATE.
5. Append-Only Lifecycle
Issued evaluation records SHOULD be immutable. New evidence SHOULD
create a successor record that can identify its predecessor. A
successor MUST NOT be interpreted as erasing the historical state
under which an earlier decision was made.
6. Typed Promotion Boundaries
Crossing from observation to evidence, evidence to warranted premise,
premise to authorization, and authorization to execution requires
explicit interfaces or witnesses. Implementations SHOULD make these
promotion rules inspectable and testable.
7. Relationship to Evidence Qualification Receipts
An Evidence Qualification Receipt can implement the evidence-
qualification layer described here. A PASS receipt remains an
authorization input only; local policy retains authority over action.
8. Security Considerations
Semantic collapse can enable authority laundering, replay of stale
evidence, profile substitution, confused-deputy execution, and false
completion records. Implementations should bind evidence states to
exact propositions, profiles, contexts, and actions when consequence
warrants it.
Watts Expires 3 May 2027 [Page 3]
Internet-Draft Agent Non-Collapse Requirements October 2026
9. Privacy Considerations
Evidence graphs can expose sensitive information. Systems should
minimize plaintext evidence in authorization paths and prefer scoped
digests or privacy-preserving references when sufficient.
10. IANA Considerations
This document has no IANA actions.
11. Normative References
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
Appendix A. Changes since -00
This section is to be removed before publishing as an RFC.
Editorial and tooling-conformance changes only; no technical content
was changed.
* Added BCP 14 Requirements Language section (document uses
uppercase requirement keywords without the boilerplate; idnits
error)
* Added RFC 2119 reference entry
* Added RFC 8174 reference entry
* Normalized author metadata (full name with ASCII form, initials,
organization GoodShyt Group Inc., San Francisco CA postal, email,
ORCID URI)
* Updated document date and revision number.
Author's Address
Deonté O'dell Watts
GoodShyt Group Inc.
San Francisco, CA
United States of America
Watts Expires 3 May 2027 [Page 4]
Internet-Draft Agent Non-Collapse Requirements October 2026
Email: deonte@goodshyt.fun
URI: https://orcid.org/0009-0005-8586-3650
Watts Expires 3 May 2027 [Page 5]