Palomar Registry
Native namespace palomar-registry
Source-native objects
Repository bindings
A source observation does not create a local scientific record.
Exact observation
observation:palomar-registry:d5994e671a0ec7cc
observation: sha256:306220a43c9696396c9f0cbb87ddb3d3352941a4b411988269386911c2492688
retained exact bytes · immutable artifact retention
Source-native objects and Repository bindings
1 exact source-native objects
1 rows · complete coverage
0 exact links to local Repository records
Coverage and omissions
The one exact Palomar registry entry served at the declared versioned entry URL, with its two evidence reports re-verified against the digests inside the entry.
The challenge render is retained as a locator and provider tree digest only; its bytes are not archived.
Beyond the two digest-verified reports, the evidence tree — comparator log tail, resource usage, Mathlib cache and the rest — is pinned by evidence_tree_sha256 and not archived.
Comparator, Lean-kernel, and NanoDa results are folded into Palomar's single mechanical pass and retained as one scoped external check (palomar-mechanical); Vela re-derives none of them and none is a Vela Verification.
Palomar's registered status and trust level are Palomar-local external standing; they create no Vela Standing, Verification, acceptance, or admission.
Palomar claims no novelty, no quality assessment, no peer review, no publication status, and no informal-proof verification; these attributed nonclaims are registry-level prose, not per-record data.
The semantic review is an LLM review under a pinned policy commit; its outcome and bounded findings are attributed observations, never adjudication.
The submitter relationship is an asserted field; Palomar publishes no signed consent artifact.
Only the admission outcome — status registered with its timestamps — is observable; the registry's admission decision process is internal.
Version relations are reconstructed from the shared registry ID and integer versions; Palomar publishes no supersedes or corrects field, and the reason for a new version is unobservable.
Palomar publishes no digest or signature over the entry JSON; authenticity rests on TLS retrieval plus the consumer-computed retained-bytes root, and version-URL immutability is Palomar's assertion.
Source declarations, observations, source-native object rows, and Repository bindings record provenance. None creates scientific Standing; only an admitted local Claim can enter the attributed Decision path.
- Release root
- sha256:c9d14c459c518937e758918b5897dc3b22f1a55f07739afe99502f5b046c907a
- Declaration root
- sha256:0b156480f46fc1e84218fce8f7e96f34a3660111c8c12bedf1c0da8b5ce67963
- Adapter root
- sha256:753f8e0579c8df2b00b3252be6e7903828e452f958f62a68c8efc96edfc4cdcb
- Source row root
- sha256:0b156480f46fc1e84218fce8f7e96f34a3660111c8c12bedf1c0da8b5ce67963
- Acquisition root
- sha256:d5994e671a0ec7cc9bf676e7188f01eaf7034d9995bbda3f7367c51120c3a6c0
- Observation root
- sha256:a3c53cc7646897e1355ce64ebd16dbdc5eec63e624ae19de3dbf0403ba77c588
- Projected source-native rows root
- sha256:d0f87c766291e0ee2876a13e784d5837b144c193c26a796bd4b1bff73591bf7f
- Snapshot root
- sha256:306220a43c9696396c9f0cbb87ddb3d3352941a4b411988269386911c2492688