# Appendix A — Agent Records and Handoff Schemas
# Book: Agent Architectures: Advanced Strategies for Intelligent LLM Systems
# Chapter URL: https://programmer.ie/books/agent-architectures/80-chapter/
# Prose fingerprint (sha256, normalized): ec7ab52f3934497f5b92cb2cfb85c3d5349ca2103ad1aa2d630c1c2ee0f71888
# Snapshot generated at build time by Hugo. This is the complete rendered prose
# of the chapter; it is not a transcript of the source file.

Handoff record One record per transfer between roles. Every claim carries its evidence status and source.
{ &#34;role&#34;: &#34;researcher&#34;, &#34;task_id&#34;: &#34;urban-transport-001&#34;, &#34;claim&#34;: &#34;Micromobility is increasingly regulated through city-level safety rules.&#34;, &#34;evidence&#34;: &#34;source URL or document path&#34;, &#34;evidence_type&#34;: &#34;background | source | observation | derivation&#34;, &#34;status&#34;: &#34;unverified | verifying | verified | disputed | superseded&#34;, &#34;confidence&#34;: &#34;low | medium | high&#34;, &#34;open_questions&#34;: [&#34;Which cities changed policy in the last 12 months?&#34;], &#34;requested_action&#34;: &#34;verify source date&#34;, &#34;provenance&#34;: &#34;retrieval query + document id, or step that produced it&#34; } Decision event The minimum trace that lets you answer later: who decided, from which state, using what evidence, and what changed?
decision_id run_id actor input_state_id proposed_action authority_check (allowed | needs review | rejected, with policy reference) evidence_used accepted_or_rejected output_state_id Role record name: critic version: 1.3.0 model: recorded_at_runtime prompt_id: critic_prompt_v4 input_schema: candidate_summary_v2 output_schema: critique_v1 tools: [citation_checker] memory_access: [current_task_log] authority: recommend_only status: production Memory-entry fields content stored_by / stored_at source / provenance valid_at / known_at (when true / when recorded) supersedes / superseded_by scope (which project, task, or context may use it) expiry or review date These shapes are starting points. Their value is not the field list — it is that every handoff, decision, and memory becomes inspectable by someone other than its author.