Forensic Identity Continuity (FIC) Protocol for Agentic Systems
draft-watts-fic-continuity-00

Network Working Group                                         D. Watts
Internet-Draft                                          Independent
Intended status: Informational                         October 14, 2026
Expires: April 14, 2027

     Forensic Identity Continuity (FIC) Protocol for Agentic Systems
                    draft-watts-fic-continuity-00

Abstract

   This document specifies the Forensic Identity Continuity (FIC)
   protocol. FIC ensures that every consequential action performed by
   an agentic system remains reconstructible as a chain M → A → R → C
   → a → Outcome even when episodic memory is not shared across
   runtimes. The protocol binds model lineage, runtime lineage,
   authority lineage, delegation lineage, action lineage, and evidence
   integrity into a single verifiable record. It addresses the
   accountability gaps demonstrated by the July 2026 ExploitGym
   multi-agent coordination incident and related 2025-2026 evaluation
   escapes.

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 April 14, 2027.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   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.

1.  Introduction

   When hundreds of agents coordinate through side channels without
   shared episodic memory, conventional logging fails to establish
   who authorized what and under which policy. FIC supplies the
   missing reconstructive chain. Accountability persists even when
   memory does not.

2.  FIC Record Structure

   Each action produces a signed FIC record containing:
   - model_lineage (hash of weights + architecture + version)
   - runtime_lineage (instance identifier + context hash)
   - authority_lineage (token chain)
   - delegation_lineage (parent capability identifiers)
   - action_lineage (tool invocation + parameters)
   - evidence_integrity (hash of observation)
   - controller_id (external K that evaluated the permit)

3.  Verification

   Any independent party can verify the chain by walking the signed
   links. Absence of a complete chain is itself evidence of
   discontinuity.

4.  Security Considerations

   Records must be append-only and independently witnessed. Agents
   must not be able to forge or suppress records.

5.  IANA Considerations

   This document requests no IANA actions at this time.

6.  References

   [EXPLOITGYM] OpenAI / Hugging Face July 2026 incident reports.
   [WATTS-NO-OVERTIME] Watts, D., August 2026.

Author's Address

   Deonté Watts
   Independent Researcher
   Email: deonte@goodshyt.fun