Internet-Draft Live Reference Resolution November 2026
Morrison Expires 22 May 2027 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-morrison-live-reference-resolution-03
Published:
Intended Status:
Informational
Expires:
Author:
B. Morrison
Alter Meridian Pty Ltd

Live Reference Resolution for Autonomous Agent Beliefs

Abstract

A recurring class of autonomous-agent failure arises when an agent acts on a belief read from a cached, derived, or proxy copy that has silently diverged from the authority the belief claims to represent. This document describes a reference-resolution discipline for the working beliefs an agent reasons and acts from. Each belief is held as a reference to a single named lowest authority and is resolved live at the point of use, with verification. When the authority is unobservable or the resolved value is stale, the belief takes an explicit uncertainty state and never falls back to a prior cached value. That state propagates to any belief derived from it, and an uncertain belief feeding a costly or irreversible act blocks the act or escalates it. Every resolution chain terminates in a single self-authorising root. The document is Informational. It records a discipline and a vocabulary and defines no wire protocol.

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 22 May 2027.

▲

Table of Contents

1. Introduction

An autonomous agent holds many working beliefs, such as the current value of a configuration item, which record is authoritative, whether a code path is still live, and the present state of a shared resource. In a wide class of agent errors, the agent reads such a belief from a copy that once matched an authority but has since diverged, and acts on the copy as though it were the authority. Common instances include a stale index read in place of the canonical registry, an ambient assumption carried across calls, a retained but superseded code path treated as current, and a narrative document trusted for a value that a live system owns. Point-in-time identity checks have the same shape. A confirmation made at one moment is relied on until the next, with nothing known about the interval in between (Section 3.1 of [MORRISON-IFT]).

Capability systems govern the authority to act, content-addressing and transparency logs govern the naming and integrity of data and artefacts, and message-signature schemes such as [RFC9421] bind a request to a key. None of these govern the working beliefs an agent reasons from, and none defines what an agent should do when the authority for a belief cannot be observed at the moment the belief is needed.

This document describes a discipline for that layer. It concerns the resolution of a belief against its authority, the handling of staleness, and the termination of resolution chains. It does not describe how any particular authority is implemented, how capabilities or credentials are provisioned, or how conflicting assertions from multiple agents are arbitrated.

2. Terminology

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.

Belief:

A value on which an agent will act.

Belief graph:

The beliefs an agent holds and the derivation relations between them.

Authority:

The single named source that owns the current value of a belief. An authority is the lowest source in a precedence order that can answer for the belief. For a live value, that source is a running system rather than a document describing it.

Reference:

A stable identifier for a belief together with the name of its authority, held in place of a stored value.

Resolution:

The act of dereferencing a reference against its named authority to obtain a current value, at the point of use.

Point of use:

The moment, contemporaneous with the act that consumes a belief, at which resolution occurs. Resolution performed earlier and cached is not resolution at the point of use.

Contemporaneous:

Within a round-trip bound declared by the relying deployment. A resolution is contemporaneous with an act when the interval from the start of the dereference to the act is no longer than that bound. The deployment declares the bound for each authority, and this document sets no value for it. The Echo option of [RFC9175] gives a published example of a freshness test against a threshold that the verifying party chooses. The server checks that the time between generating the Echo value and receiving the request is below a threshold T (Section 2.3 of [RFC9175]).

Uncertainty state:

An explicit value a belief takes when its authority is unobservable, its resolved value fails verification, or a freshness bound is exceeded.

Constitutive root:

A self-authorising source that answers for itself, such as a cryptographic key or a ratified decision record, in which a resolution chain terminates.

3. The resolution discipline

3.1. Belief as reference

An agent SHOULD hold a belief on which it will act as a reference rather than a stored value. The reference names the belief and its single lowest authority. Holding the belief as a reference makes live resolution possible; a value copied into the agent's state carries no way to detect that the authority has since changed.

3.2. Live resolution at the point of use

An agent SHOULD resolve a reference at the point of use, contemporaneously with the act that consumes the belief, by dereferencing the named authority to obtain a current value and verifying that value against the authority. A cached, derived, or proxy copy of the belief SHOULD NOT stand in for a live dereference of the named authority at the point of an act.

Where an authority is expensive to dereference on every use, an agent MAY apply a bounded exemption only when all of the following hold: the belief follows from an observed fact under current semantics, the cost of being wrong is small and readily reversible, and either a fail-closed check catches the wrong case or the belief decays at a boundary served by a live change-detection channel. A belief feeding a costly, irreversible, or externally visible act MUST NOT be exempted and MUST be re-resolved against its authority at the point of use.

3.3. Authority precedence

Where more than one source could answer for a belief, the authority is the lowest source in a precedence order that places an executing system above an artefact generated or enforced by continuous integration, above a hand-maintained document. A value claimed by a lower-precedence source MUST NOT override a live dereference of a higher-precedence authority. A document labelling itself authoritative is not, by that label, the authority.

4. Uncertainty

4.1. The uncertainty state

When the named authority is unobservable, the resolved value fails verification, or a declared freshness bound is exceeded, the belief MUST take the explicit uncertainty state rather than a prior cached value. Freshness MAY be expressed per authority as a maximum staleness interval or a monotonically-advancing epoch, and crossing the bound triggers the uncertainty state without requiring an affirmative invalidation message from the authority.

The uncertainty state is a value that a belief carries, distinct from the absence of a value and from a low numeric confidence attached to an asserted value.

4.2. Contagion

An agent MUST propagate the uncertainty state through its belief graph to every belief derived, in whole or in part, from an uncertain belief. Two beliefs that resolve to contradictory values both take the uncertainty state, and only re-resolution or escalation settles the contradiction.

4.3. The consumer contract

Uncertainty is default-closed at the point of consumption. When an uncertain belief is an input to an act classified as costly or irreversible, the agent MUST block the act or escalate for resolution rather than proceed on the uncertain belief. The classification of an act as costly or irreversible is itself a belief resolved under this discipline. The obligation applies to the conjunction of several uncertain inputs as well, and two or more individually marginal uncertainties together carry the obligation to block.

The secure-channel use cases of [SEATUC] state the same default for attestation. In its Section 5.1, a failure to complete a check required for the decision leaves the decision indeterminate, and neither rejection nor an indeterminate decision permits an operation requiring attestation.

5. Chain termination

Every resolution chain MUST terminate in exactly one constitutive root, a self-authorising source drawn from a closed set such as a cryptographic key or a ratified decision record. A constitutive root answers for itself and fails closed, and it is conferred from outside the belief graph. Before an act, an agent SHOULD reject a reference whose resolution chain is circular or fails to terminate in such a root, and SHOULD record which reference was rejected.

A ratified decision that supersedes an implementation outranks a retained but unmarked instance of that implementation. A belief in the liveness of the superseded implementation takes the uncertainty state until the implementation is removed or carries a machine-readable supersession marker.

6. The resolution result

An agent that exposes belief resolution to other components SHOULD return, with the value and atomically bound to it, at least the identifier of the authority that answered, a freshness indicator, and a provenance type. Because these are bound to the value, a consumer cannot obtain the value without them.

A provenance type is drawn from a closed set. This document does not define the set normatively, but distinguishing at least a direct read of an authority, a presumption, and an unverified inference is RECOMMENDED. A value carrying a presumption or an unverified-inference provenance type MUST NOT be relabelled as a direct read by any downstream consumer.

7. Relationship to other work

Capability and delegation systems govern the authority to act, and content-addressing and transparency logs govern the integrity of static artefacts; this discipline complements the first and composes with the second. The provenance types of Section 6 and the closed substrate-class labels of [SUBPROV] both keep an unverified inference distinct from a direct read, the first for an agent's working beliefs and the second for assertions in model output. [SUBSTRATEOBS] applies the same preference for observing a live source over a declared copy to coordination between concurrent sessions. Arbitration among several already-emitted and conflicting assertions, and the provisioning of capabilities or credentials, are out of scope for this document.

8. Security Considerations

An agent following this discipline still trusts its authorities and the freshness bounds it declares for them. It places that trust in a single named source per belief and re-checks the source at the point of use, and a failure to observe the source degrades to an explicit blocking state rather than to silent use of a stale value. An implementation that declares over-generous freshness bounds, or that permits a lower-precedence source to answer for a belief, weakens these properties.

Compromise of a constitutive root, such as a cryptographic key, or subversion of the process that ratifies a decision record, compromises every belief whose chain terminates in that root. Roots therefore warrant the protections appropriate to keying material and to governance records.

An adversary who can make an authority unobservable can drive dependent beliefs to the uncertainty state and thereby deny service by blocking costly acts. This is a fail-closed outcome and is preferable to silent action on stale values, but implementers should ensure that the escalation path for a blocked act cannot itself be starved.

9. IANA Considerations

This document has no IANA actions.

10. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.

11. Informative References

[RFC9421]
Backman, A., Ed., Richer, J., Ed., and M. Sporny, "HTTP Message Signatures", RFC 9421, DOI 10.17487/RFC9421, , <https://www.rfc-editor.org/info/rfc9421>.
[RFC9175]
Amsuess, C., Preuss Mattsson, J., and G. Selander, "Constrained Application Protocol (CoAP): Echo, Request-Tag, and Token Processing", RFC 9175, DOI 10.17487/RFC9175, , <https://www.rfc-editor.org/info/rfc9175>.
[SEATUC]
Mihalcea, I., Ed., "Security Goals and Use Cases for Integrating Remote Attestation with Secure Channel Protocols", Work in Progress, Internet-Draft, draft-ietf-seat-use-cases-02, , <https://datatracker.ietf.org/doc/draft-ietf-seat-use-cases/>.
[SUBSTRATEOBS]
Morrison, B., "Substrate-Observation as an Alternative to Envelope Coordination for Concurrent Sessions", Work in Progress, Internet-Draft, draft-morrison-substrate-observation-04, , <https://datatracker.ietf.org/doc/draft-morrison-substrate-observation/>.
[SUBPROV]
Morrison, B., "Substrate-Provenance Annotation Grammar for Large-Language-Model Output", Work in Progress, Internet-Draft, draft-morrison-substrate-provenance-grammar-05, , <https://datatracker.ietf.org/doc/draft-morrison-substrate-provenance-grammar/>.
[MORRISON-IFT]
Morrison, B., "Identity Field Theory: Toward a Physics of Being Known", , <https://doi.org/10.6084/m9.figshare.31951383>.

Document History

draft-morrison-live-reference-resolution-03 (November 2026):

draft-morrison-live-reference-resolution-02 (October 2026):

draft-morrison-live-reference-resolution-01 (October 2026):

Acknowledgements

This discipline was distilled from operational failure patterns observed in autonomous coding agents.

Author's Address

Blake Morrison
Alter Meridian Pty Ltd