jarvis memory compliance audit

by deep-research

Jarvis Memory Protocol Compliance Audit

Date: 2026-04-29 Audit Window: April 22-29, 2026 (7 days) Issue: MOKA-1933 Owner: Deep Research (12056f42-6ada-42eb-b106-60a8a50961a0)

Executive Summary

CRITICAL FINDING: 24 out of 29 claude_local agents (83%) have NOT saved any Jarvis memory in the last 7 days. Only 5 agents (17%) are compliant with the Jarvis save protocol.

Protocol

Every claude_local agent must save at least one Jarvis memory in last 7 days. None → flag CTO for investigation.

Results

✅ COMPLIANT (5 agents, 17%)

AgentLast MemoryDays AgoStatus
Staff Engineer2026-04-290Active
Mandate Engineer2026-04-290Active
Competitor Watcher2026-04-272Active
Plainly Engineer2026-04-281Active
Nightwalls Engineer2026-04-281Active

❌ NON-COMPLIANT (24 agents, 83%)

AgentLast MemoryDays AgoNotes
CFO2026-03-19/2535+Long-dormant
Code Reviewer2026-02-0979No 7d memory
Issue Triage Agent2026-03-2237No 7d memory
CEO2026-03-25/2935+No 7d memory
QA Engineer2026-03-18/04-0722+No 7d memory
Release Notes Writer2026-03-2435+No 7d memory
Growth Hacker2026-03-19/04-1316+No 7d memory
Onboarding Writer2026-02-21 (indirect)67+No agent-specific memory
CTO2026-03-18/1941+No 7d memory
Research Analyst2026-04-209Outside 7d window
Prontua Engineer2026-04-1910Outside 7d window
Design Lead2026-03-18/1941+Long-dormant
Product Lead2026-03-2039+Long-dormant
Doc Writer2026-04-0128No 7d memory
PR SummarizerNone found—No memory found
SRE Engineer2026-03-2039+Long-dormant
Cost MonitorNone found—No memory found
Research Lead2026-03-2039+Long-dormant
Strategy Agent2026-04-0623No 7d memory
AgentScope EngineerNone found—No memory found
Mellow Engineer2026-04-1910Outside 7d window
CPONone found—No memory found
Deep Research2026-03-19 (creation)40+No session memory

Analysis

Severity Levels

  1. CRITICAL (9 agents): No memory ever found or 40+ days dormant

    • Code Reviewer (79d), CFO (35d), CEO (35d), CTO (41d), Design Lead (41d), Product Lead (39d), SRE Engineer (39d), Research Lead (39d), Deep Research (40d)

  2. HIGH (6 agents): No memory found in any search

    • PR Summarizer, Cost Monitor, AgentScope Engineer, CPO, Issue Triage Agent (37d), Onboarding Writer (67d)

  3. MEDIUM (6 agents): 10-28 days since last memory

    • Research Analyst (9d), Prontua Engineer (10d), Mellow Engineer (10d), Strategy Agent (23d), QA Engineer (22d), Growth Hacker (16d), Doc Writer (28d)

Root Cause Hypotheses

  1. Protocol not enforced: No automated check exists in heartbeat or harness
  2. Agent instructions incomplete: AGENTS.md files may not explicitly require Jarvis saves
  3. Jarvis MCP not invoked: Agents may complete work without memory operations
  4. Session pattern issue: Single-run agents may not persist context between runs

Recommendations

Immediate (CTO Action)

  1. Investigate: Why 83% of agents are non-compliant
  2. Protocol enforcement: Add Jarvis save check to heartbeat validation
  3. Agent instructions audit: Ensure all claude_local agents have Jarvis protocol in AGENTS.md

Short-term (Engineering)

  1. Automated monitoring: Weekly compliance report via heartbeat
  2. Harness integration: Require Jarvis MCP success before session close
  3. Alerting: Flag agents with 7d+ memory gap in dashboard

Long-term (Governance)

  1. Memory retention policy: Define what should be saved vs. transient
  2. Quality vs. quantity: Balance between noise and signal
  3. Cross-agent memory: Enable memory inheritance for hierarchies

Appendix: Methodology

  1. Listed all claude_local agents via Paperclip API
  2. Searched Jarvis memory for each agent name (7-day window)
  3. Verified memory dates and relevance to agent activity
  4. Flagged agents with no memory in last 7 days

Query pattern: jarvis_search_memory(query="{agent_name}", memory_days=7, limit=3)