c/ietf-draft-analyzer
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add ASCII art figures to all 6 generated Internet-Drafts

Browse Source 
Each draft gets 2 illustrative figures:
- ABVP: architecture components + verification workflow
- ATD: example DAG structure + execution state transitions
- HITL: primitive framework overview + approval workflow sequence
- AEM/PPALP: federated learning architecture + aggregation flow
- RARP: cross-domain architecture + two-phase rollback protocol
- APAE: layered architecture + cross-domain provenance tracking

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Christian Nennemann
2026-03-04 02:20:39 +01:00
parent 404092b938
commit 3c3d7e649f
6 changed files with 236 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
data/reports/generated-drafts/draft-ai-agent-rollback-protocol-00.txt
View File

@@ -319,6 +319,30 @@ Table of Contents
gateway-intercomm-framework] to provide cross-domain rollback
coordination capabilities.
Domain A Domain B
+---------------------+ +---------------------+
| +------+ +------+ | | +------+ +------+ |
| |Agt 1 | |Agt 2 | | | |Agt 3 | |Agt 4 | |
| +--+---+ +--+---+ | | +--+---+ +--+---+ |
| | | | | | | |
| +--+---------+----+ | | +--+---------+----+ |
| |Checkpoint Manager| | | |Checkpoint Manager| |
| +--------+---------+ | | +--------+---------+ |
| | | | | |
| +--------+---------+ | | +--------+---------+ |
| |Rollback Coordintr| | | |Rollback Coordintr| |
| +--------+---------+ | | +--------+---------+ |
+----------|------------+ +----------|------------+
| |
+----------+ +--------------+
| |
+----+--+----+
| Agent |
| Gateway |
+------------+
Figure 1: RARP Cross-Domain Architecture
The core RARP architecture consists of three primary component
types: Rollback Coordinators, Checkpoint Managers, and Agent
Rollback Interfaces. Rollback Coordinators serve as the
@@ -461,6 +485,28 @@ Table of Contents
to validate the rollback request against their local checkpoint
metadata.
Coordinator Agent A Agent B Agent C
| | | |
|--PREPARE---->| | |
|--PREPARE---------------->| |
|--PREPARE------------------------------>|
| | | |
|<--READY------| | |
|<--READY------------------| |
|<--READY---------------------------------|
| | | |
|--COMMIT----->| | |
|--COMMIT----------------->| |
|--COMMIT------------------------------->|
| | | |
| (rollback) | (rollback) | (rollback) |
| | | |
|<--DONE-------| | |
|<--DONE-------------------| |
|<--DONE---------------------------------|
Figure 2: Two-Phase Coordinated Rollback
The coordination messaging framework builds upon the Cross-Domain
Agent Collaboration Protocol [draft-han-rtgwg-agent-gateway-
intercomm-framework] to enable rollback operations across