Pith Number

pith:DGB6V6WG

pith:2026:DGB6V6WGUHMEE7BORMFJHLC7RD

not attested not anchored not stored refs resolved

MemLineage: Lineage-Guided Enforcement for LLM Agent Memory

Ciyan Ouyang, Rui Hou

By tracking derivation lineage in agent memory, MemLineage prevents poisoned entries from justifying sensitive actions while preserving useful recall.

arxiv:2605.14421 v1 · 2026-05-14 · cs.CR · cs.AI

Open paper page JSON Open Graph Bundle Merged state Verified badge What is a Pith Number?

Add to your LaTeX paper

\usepackage{pith}
\pithnumber{DGB6V6WGUHMEE7BORMFJHLC7RD}

Prints a linked badge after your title and injects PDF metadata. Compiles on arXiv. Learn more · Embed verified badge

Record completeness

1 Bitcoin timestamp

2 Internet Archive

3 Author claim open · sign in to claim

4 Citations open

5 Replications open

✓ Portable graph bundle live · download bundle · merged state

The bundle contains the canonical record plus signed events. A mirror can host it anywhere and recompute the same current state with the deterministic merge algorithm.

Claims

C1strongest claim

MemLineage is the only configuration in that harness that drives all three columns to zero ASR, while sub-millisecond per-operation overhead keeps it well below the noise floor of any LLM call.

C2weakest assumption

That the LLM-mediated derivation lineage accurately identifies which prior entries influenced each new memory and that the max-of-strong-edges propagation rule correctly captures all paths that could justify sensitive actions.

C3one line summary

MemLineage enforces untrusted-path persistence in LLM agent memory through Merkle logs, per-principal signatures, and max-of-strong-edges lineage propagation, achieving zero ASR on three poisoning workloads with sub-millisecond overhead.

References

20 extracted · 20 resolved · 6 Pith anchors

[1] Bernstein, Niels Duif, Tanja Lange, Peter Schwabe, and Bo-Yin Yang 2012 · doi:10.1007/s13389-

[2] Carsten Bormann and Paul E. Hoffman. Concise binary object representation (CBOR). RFC 8949, Internet Engineering Task Force (IETF), December

[3] Verified via IETF datatracker

[5] Ghost in the Agent: Redefining Information Flow Tracking for LLM Agents · arXiv:2604.23374

[6] Agentpoison: Red-teaming llm agents via poisoning memory or knowledge bases 2024

Receipt and verification

First computed	2026-05-17T23:39:07.248373Z
Builder	pith-number-builder-2026-05-17-v1
Signature	Pith Ed25519 (`pith-v1-2026-05`) · public key
Schema	pith-number/v1.0

Canonical hash

1983eafac6a1d8427c2e8b0a93ac5f88c41c567b9e68e15c360c89e7a22d9f48

Aliases

arxiv: 2605.14421 · arxiv_version: 2605.14421v1 · doi: 10.48550/arxiv.2605.14421 · pith_short_12: DGB6V6WGUHME · pith_short_16: DGB6V6WGUHMEE7BO · pith_short_8: DGB6V6WG

Agent API

Resolver JSON Graph JSON Events JSON Schema Signing key

Verify this Pith Number yourself

curl -sH 'Accept: application/ld+json' https://pith.science/pith/DGB6V6WGUHMEE7BORMFJHLC7RD \
  | jq -c '.canonical_record' \
  | python3 -c "import sys,json,hashlib; b=json.dumps(json.loads(sys.stdin.read()), sort_keys=True, separators=(',',':'), ensure_ascii=False).encode(); print(hashlib.sha256(b).hexdigest())"
# expect: 1983eafac6a1d8427c2e8b0a93ac5f88c41c567b9e68e15c360c89e7a22d9f48

Canonical record JSON

{
  "metadata": {
    "abstract_canon_sha256": "9f1abe1c73cf4768664ab401964f8df2d0771eed2e33a5dde2583b6ffda0c7ff",
    "cross_cats_sorted": [
      "cs.AI"
    ],
    "license": "http://creativecommons.org/licenses/by/4.0/",
    "primary_cat": "cs.CR",
    "submitted_at": "2026-05-14T06:07:54Z",
    "title_canon_sha256": "15306b4c326d885ef26a00ac830272d9ef9a1c8653a8bc235c9ebc8badf2f445"
  },
  "schema_version": "1.0",
  "source": {
    "id": "2605.14421",
    "kind": "arxiv",
    "version": 1
  }
}