Skip to content
Cube coverageMH-362,64,583 clusters × 492Pan-India653 districts × 39reference →
Bhārata Strata · Maharashtra · Nanded · provenance / warrant

By what warrant? — cell 4850007153

The attest verb answers "by what warrant do you say this?" for this Nanded locality cell: it RE-COMPUTES the SHA-256 of the source shard (never echoes the stored one) and walks the artefact's ancestry lineage. Fail-closed — it proves provenance or refuses, but never fabricates it.

Byte integrity
✓ verified
recomputed vs recorded SHA-256
Artefact version
v1.8.0
BharataStrata_MH36_Unified_v1_8
Cube sequence
#8
re-bake epoch (transaction-time)
Doctrine baseline
v2.4
genesis doctrine version

Re-computed byte integrity

Source shard
derived/bharata_strata/sprint-6/mh36-unified-v1.8/admin_code=485/mh36_unified_v1_8.parquet
SHA-256 recorded
0d704ad602791609ec17b2206fa5fa27a43230dc7bce7e35ba92dbb991a88804
SHA-256 recomputed
0d704ad602791609ec17b2206fa5fa27a43230dc7bce7e35ba92dbb991a88804
Verdict
match — integrity verified (P5: recomputed, not echoed)

Ancestry lineage

Artefact
BharataStrata_MH36_Unified_v1_8
Version
v1.8.0-tier-b-label-correction-coastal-tiles-doctrine-v2.4
Parent
v1.7
Published
2026-06-23 12:25 UTC
Ancestry chain
  1. mh36_unified_v1_5 (452 cols, doctrine v2.4 per-tier pin chains)
  2. mh36_unified_v1_6 (452 cols, sprint-7-step-4b K=2 shallow re-emit)
  3. mh36_unified_v1_7 (477 cols, sprint-d9-c5-c6 DEEP re-emit with tier_t_v1)
  4. mh36_unified_v1_8 (492 cols, VALUE-only tier_b label correction: 5 tier_b_v1_*_s2_rgb_* cols replaced from the corrected overlay; ~19,251 null tile ids -> 0; schema fingerprint UNCHANGED)

Version-dynamic shallow re-stamp (§17.4.4): columns byte-identical to the re-stamped version v1.8; only per_tier_pin_manifest + reemit_trigger + publish_utc are refreshed. All deep-emit ANCESTRY (network_features_promotion / tier_t genesis / ancestry chain) is preserved. Version + cube_seq are unchanged — a re-stamp is a freshness event, never a re-projection or a version bump.

Re-witness this warrant

curl -s https://api.gridrock.ai/mcp -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"attest",
       "arguments":{"subject":"cell","admin_code":485,"cluster_id":4850007153}}}'

Scope: the live MH-36 cube. The SHA-256 is recomputed server-side on every call (P5) — a stored hash is never simply echoed back.