Bridge Contract for Agent Session Governance

Existing agent protocols --- the Agent Transfer Protocol (AGTP), the Governance Audit Record (GAR) and the Protocol for Agent Communication Exchange (PACE) --- define transport, audit and resumption semantics for agent sessions, but, in the versions read, none defines what an intermediate bridge MUST do when the client is detached and the agent keeps executing, or when the human in the loop is unavailable. We argue that the reason is scope rather than oversight; this rests on a reading of those drafts and would weaken if one of them were extended to own these duties. This document defines the Bridge Contract BC = (S, E, R, C): a Session Identity Descriptor, Mandatory Governance Events, a Resume Record that the bridge keeps for itself, and Conformance Criteria. Re-attach is a challenge-response in which the client proves possession of a registered key over a single-use nonce and the last event it saw, and the bridge accepts only a consistent prefix. The log is hash-chained, which detects edits and reordering inside it but not the truncation of its last events without a head held outside the log. The normative model is a product state machine of attachment, human and lifecycle, with invariants I1--I15 and derived timers. The contract complements AGTP, GAR and PACE and does not replace them. Evidence: the product model is checked with TLC on bounded configurations; a conformance suite (T1--T158) and a mutation check in which every MUST invariant except the inspection-only I-SIGN-JWKS has a killed mutant, on a Python bridge; vectors V01--V134 pass on it, and all but the checkpoint-emission vectors (V52--V54, V88, V89; they need a feature the crate lacks) pass on a Rust crate. Both implementations have the same author; no third-party implementation exists. The evidence shows the consistency of one reading of the text, not independent confirmation; the limits are stated in the limitations section and the limitations register, which also lists where the reference bridges do not yet meet the text, among them the replay of a request refused before its key was registered.

Authors

Publication Details

Journal
Zenodo (CERN European Organization for Nuclear Research)
Published
2026-11-21
DOI
https://doi.org/10.5281/zenodo.24409592
Primary Topic
Access Control and Trust
Type
preprint
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
preprint

Bridge Contract for Agent Session Governance

Sergei Strebulaev
Zenodo (CERN European Organization for Nuclear Research)
Access Control and Trust
preprint

Bridge Contract for Agent Session Governance

Sergei Strebulaev
preprint en

Abstract

Existing agent protocols --- the Agent Transfer Protocol (AGTP), the Governance Audit Record (GAR) and the Protocol for Agent Communication Exchange (PACE) --- define transport, audit and resumption semantics for agent sessions, but, in the versions read, none defines what an intermediate bridge MUST do when the client is detached and the agent keeps executing, or when the human in the loop is unavailable. We argue that the reason is scope rather than oversight; this rests on a reading of those drafts and would weaken if one of them were extended to own these duties. This document defines the Bridge Contract BC = (S, E, R, C): a Session Identity Descriptor, Mandatory Governance Events, a Resume Record that the bridge keeps for itself, and Conformance Criteria. Re-attach is a challenge-response in which the client proves possession of a registered key over a single-use nonce and the last event it saw, and the bridge accepts only a consistent prefix. The log is hash-chained, which detects edits and reordering inside it but not the truncation of its last events without a head held outside the log. The normative model is a product state machine of attachment, human and lifecycle, with invariants I1--I15 and derived timers. The contract complements AGTP, GAR and PACE and does not replace them. Evidence: the product model is checked with TLC on bounded configurations; a conformance suite (T1--T158) and a mutation check in which every MUST invariant except the inspection-only I-SIGN-JWKS has a killed mutant, on a Python bridge; vectors V01--V134 pass on it, and all but the checkpoint-emission vectors (V52--V54, V88, V89; they need a feature the crate lacks) pass on a Rust crate. Both implementations have the same author; no third-party implementation exists. The evidence shows the consistency of one reading of the text, not independent confirmation; the limits are stated in the limitations section and the limitations register, which also lists where the reference bridges do not yet meet the text, among them the replay of a request refused before its key was registered.

Zenodo (CERN European Organization for Nuclear Research)
Access Control and Trust
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon