PGL / Gnomledger

The machine can disappear. The evidence cannot.

Project Genome Ledger is Veklom's durable provenance layer. It preserves append-only execution events, lineage and independently checkable hash-chain state so the truth of a governed action does not vanish with the process that performed it.

Current classification
Runtime-backed
RUNTIME

Gnomledger is a standalone FastAPI service with append-only ledger APIs, per-identity chain verification, lineage surfaces and a canonical local health endpoint. Runtime proof still depends on the specific deployed instance being observed.

Architectural role
Durable evidence / provenance and lineage
Owns
01Append-only ledger event persistence with hash-chain integrity checks.
02Execution and identity provenance that survives process restarts.
03Lineage / ancestry relationships for machine identities and execution artifacts.
04Independent ledger verification surfaces used by other Veklom services.
Boundary

Power stays narrow on purpose.

PGL records evidence; it does not mint consequence authority.
A ledger event cannot make a false provider outcome true. The upstream evidence must still be attributable and correctly bound.
CAPPO owns authorization; EEE defines a portable execution-evidence artifact; Guardian owns bounded recovery behavior.
Interfaces

The surface should tell you where the truth comes from.

Veklom does not promote a configured URL or a code path into a runtime claim. Interfaces are shown so operators can verify the actual boundary themselves.

Canonical local API
http://127.0.0.1:8001
Health
GET /health
Append event
POST /api/v1/ledger/events
Verify chain
GET /api/v1/ledger/agents/{id}/verify
Claim boundary

PGL proves the integrity and continuity of what was recorded. Strong external-consequence claims still require the evidence event to be bound to the real provider/result rather than merely appended successfully.