Pith Number
pith:H4RKABVB
pith:2026:H4RKABVBPKFUXC76IIUULWAHG3
not attested
not anchored
not stored
refs pending
How Do Developers Maintain and Evolve Their Agents' Instructions? An Empirical Study
arxiv:2606.25257 v1 · 2026-06-24 · cs.SE
Add to your LaTeX paper
\usepackage{pith}
\pithnumber{H4RKABVBPKFUXC76IIUULWAHG3}
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
· sign in to
claim
4
Citations
5
Replications
✓
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.
Receipt and verification
| First computed | 2026-06-25T00:18:22.324667Z |
|---|---|
| Builder | pith-number-builder-2026-05-17-v1 |
| Signature | Pith Ed25519
(pith-v1-2026-05) · public key |
| Schema | pith-number/v1.0 |
Canonical hash
3f22a006a17a8b4b8bfe422945d80736c803f042d3ed1223edd5ab122287d6d7
Aliases
· · · · ·Agent API
Verify this Pith Number yourself
curl -sH 'Accept: application/ld+json' https://pith.science/pith/H4RKABVBPKFUXC76IIUULWAHG3 \
| 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: 3f22a006a17a8b4b8bfe422945d80736c803f042d3ed1223edd5ab122287d6d7
Canonical record JSON
{
"metadata": {
"abstract_canon_sha256": "d32c60732317dbafe810f54a0f808f0701140768aa303a99a2f2fbfd61aee3a7",
"cross_cats_sorted": [],
"license": "http://creativecommons.org/licenses/by/4.0/",
"primary_cat": "cs.SE",
"submitted_at": "2026-06-24T00:32:18Z",
"title_canon_sha256": "ae52a3d1cab281164c365ceb435f569321e2d1951fc855deff924178be999377"
},
"schema_version": "1.0",
"source": {
"id": "2606.25257",
"kind": "arxiv",
"version": 1
}
}