phrdaya phr-p02 (5-8) passes link checks; counts REGISTERED without a per-declaration run. Chunk gate passes; no witness verified.

The passage

Passage excerpt exactly as hashed (from phrdaya/passages.jsonl). Devanagari is not in the ledger, so none is rendered. The recorded hash covers this excerpt, not the edition volume.

cittam

Reading translation: withheld. no pack L2 entry maps to this passage excerpt (verse-level mapping required, none found) The verify pack carries the layer bytes; no English is quoted without a verified verse mapping.

Claim table

ClaimStatusBasis
Link completenessPASSassurance.trace_links_present + gaps
Human reviewUNREVIEWED (machine rendering; no human sign-off)assurance.review
Phrdaya.lean :: pentads_thirtyfiveSPAN-PINNED, run UNBOUND (tier R)trace formal; EVIDENCE registry reference only
Deterministic chunk gatePASS (none)proofs.chunk_gate
Manuscript witnessUNPINNED (0 verified corpus-wide)identity.witness
Source-span completenessUNKNOWNassurance: ledger span is an excerpt; volume not hashed

What this does NOT establish

Verify it

  1. Fetch the trace: curl -s https://svatantrya.net/data/traces/phrdaya-phr-p02.json
  2. Fetch the pack manifest: curl -s https://svatantrya.net/data/verify/phrdaya-phr-p02/manifest.json
  3. For each artifact: curl -s https://svatantrya.net/data/verify/phrdaya-phr-p02/<name> | sha256sum, then compare that hash with the same artifact's 'sha256' above and in the trace. If every artifact matches and the trace's recorded verdict/gaps agree with what you read, the chain is intact. A mismatch means the upstream bytes changed after the trace was made: treat the trace as stale, not the hash as wrong.
  4. If every hash matches and the verdict/gaps here agree with the trace, the chain is intact. A mismatch means upstream bytes changed: treat the trace as stale, not the hash as wrong.

Hashes

source excerpt: 315039b687fbe736a3c2245f686dc1f9e5aa97578a4fecb2341d1c874451a5c2
  ledger: phrdaya/passages.jsonl · edition: GRETIL (CANDIDATE-WORK)
layer argmap: 44cc00d624707c63…  phrdaya/data/phr-p02.argmap.json  BOUND
layer c1: 44a39104997c2248…  phrdaya/data/phr-p02.c1.json  BOUND
layer c2: 51d37536949b1bea…  phrdaya/data/phr-p02.c2.json  BOUND
layer l0: c33784d102eacc40…  phrdaya/data/phr-p02.l0.json  BOUND
layer l2: 94160b76317835ec…  phrdaya/data/phr-p02.l2.json  BOUND
layer l3: 571883f78aaa1a00…  phrdaya/data/phr-p02.l3.json  BOUND
layer l4: cda7c166de9c3c4d…  phrdaya/data/phr-p02.l4.json  BOUND
layer t1: 5ce3f455929d35c2…  phrdaya/data/phr-p02.t1.json  BOUND
song proof phrdaya/proof/proof-phr-p02.json: 470c15c2ffbf3718a62e5693f5d5952dfe3152880e177189960c2958c2fa2de2  PASS (0 warnings)
trace bundle traces/phrdaya-phr-p02.json: 8e39c7d4a8e2c2aa5190618f7c29cd4cec0da1e85126cfccc9dea74a9fec7b79
verify pack artifacts (bytes):
source.txt  315039b687fbe736…  6B
phr-p02.argmap.json  44cc00d624707c63…  3210B
phr-p02.c1.json  44a39104997c2248…  745B
phr-p02.c2.json  51d37536949b1bea…  1383B
phr-p02.l0.json  c33784d102eacc40…  2487B
phr-p02.l2.json  94160b76317835ec…  993B
phr-p02.l3.json  571883f78aaa1a00…  1380B
phr-p02.l4.json  cda7c166de9c3c4d…  1524B
phr-p02.t1.json  5ce3f455929d35c2…  1543B
proof-phr-p02.json  470c15c2ffbf3718…  1712B

Chain

HopValueStatus
SOURCE edition + spanGRETIL; verses 5-8 excerptCANDIDATE-WORK; span UNKNOWN
LAYERSshas below; song-file pathsBOUND
GATE deterministicnonePASS
FORMAL theoremsregistry references, run_bound falseREGISTERED
TRACE bundle8e39c7d4a8e2c2aa…COMPLETE (links present only)
PACK manifest10 artifactslinks present
WITNESSnone verifiedUNPINNED
REVIEWnone boundUNREVIEWED
PUBLICATIONhuman sign-off required; never automaticNOT_AUTHORIZED

Cite this

Svatantrya Reader, “phrdaya phr-p02 (5-8)”, https://svatantrya.net/claim/phrdaya/phr-p02/, version trace 8e39c7d4a8e2c2aa5190618f7c29cd4cec0da1e85126cfccc9dea74a9fec7b79 (full sha256 of the trace bundle). Retrieve and re-verify: curl -s https://svatantrya.net/data/traces/phrdaya-phr-p02.json | sha256sum must print this digest. Translators/editors of record: not established here — see edition record. The URL serves the live version; the digest pins the cited bytes. There is no archival resolver: the digest is integrity evidence, not durable storage or scholarly validation. “Complete” means links present — not approval, proof, or witness verification.

Related

Provenance