Pith Number

pith:T5PHJO3Y

pith:2026:T5PHJO3Y4P4VFKBAZUN2IVSVPW

not attested not anchored not stored refs resolved

Protocol-Driven Development: Governing Generated Software Through Invariants and Evidence

Deying Yu, Jun He

A machine-enforceable protocol of structural, behavioral, and operational invariants becomes the primary artifact, admitting an implementation only when it produces a verifiable evidence chain of compliance.

arxiv:2605.12981 v1 · 2026-05-13 · cs.SE · cs.AI · cs.LG

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

Add to your LaTeX paper

\usepackage{pith}
\pithnumber{T5PHJO3Y4P4VFKBAZUN2IVSVPW}

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

An implementation is admitted if and only if it satisfies the governing protocol and produces a verifiable Evidence Chain of compliance.

C2weakest assumption

That comprehensive, machine-enforceable protocols of the form (S, B, O) can be practically authored for real-world components and that evidence chains can be produced and verified without prohibitive cost or incompleteness.

C3one line summary

PDD treats protocols of invariants as sovereign, admitting implementations only when they satisfy the protocol triplet and produce a verifiable evidence chain of compliance.

References

25 extracted · 25 resolved · 0 Pith anchors

[1] Beck, Kent , title =

[2] Hoare, C. A. R. , title =. Communications of the ACM , volume =. 1969 , doi = 1969

[3] and Grumberg, Orna and Peled, Doron A

[4] Lamport, Leslie , title =

[5] ACM Transactions on Software Engineering and Methodology , volume = 2002

Receipt and verification

First computed	2026-05-18T03:09:08.546459Z
Builder	pith-number-builder-2026-05-17-v1
Signature	Pith Ed25519 (`pith-v1-2026-05`) · public key
Schema	pith-number/v1.0

Canonical hash

9f5e74bb78e3f952a820cd1ba456557d8960d40a01950b41c896e53beba734ab

Aliases

arxiv: 2605.12981 · arxiv_version: 2605.12981v1 · doi: 10.48550/arxiv.2605.12981 · pith_short_12: T5PHJO3Y4P4V · pith_short_16: T5PHJO3Y4P4VFKBA · pith_short_8: T5PHJO3Y

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/T5PHJO3Y4P4VFKBAZUN2IVSVPW \
  | 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: 9f5e74bb78e3f952a820cd1ba456557d8960d40a01950b41c896e53beba734ab

Canonical record JSON

{
  "metadata": {
    "abstract_canon_sha256": "dfc24faf3320cae48c96cc43d202cddbd99a07cf3b41c2a245c9117359f1d07d",
    "cross_cats_sorted": [
      "cs.AI",
      "cs.LG"
    ],
    "license": "http://creativecommons.org/licenses/by/4.0/",
    "primary_cat": "cs.SE",
    "submitted_at": "2026-05-13T04:23:14Z",
    "title_canon_sha256": "41c66627a80f79ed1382c6ab27b21e1d53cb5ed5308be2c5676a146d79c79fbf"
  },
  "schema_version": "1.0",
  "source": {
    "id": "2605.12981",
    "kind": "arxiv",
    "version": 1
  }
}