Datasets:

Zer0pa
/

Indus-Valley-lane-state

license: other
license_name: indus-valley-data-policy
license_link: https://github.com/Zer0pa/Indus-Valley/blob/main/DATA_POLICY.md
tags:
  - zer0pa
  - gnosis
  - indus-valley
  - indus-script
  - non-decipherment-search
  - lane-state
  - durability-mirror
  - product-page
  - landing-card
  - recovery-snapshot
size_categories:
  - n<1K

Zer0pa / Indus-Valley-lane-state

Canonical durable mirror for the Indus-Valley Gnosis lane.

This dataset is the canonical off-machine durability store for Zer0pa/Indus-Valley (GitHub, public). It holds everything needed to fully reproduce the lane after a local-Mac wipe, using only GitHub + this dataset.

Lane identity

GitHub repo: Zer0pa/Indus-Valley — public.
Portfolio: Gnosis.
Posture: non-decipherment search anchor. Search what we can't decipher.
PyPI: gnosis-indus v0.1.0 (live).
Token identity verified at last sync: Architect-Prime (org Zer0pa); HF token name Live Project Storage.
GitHub HEAD at last full source sync: 14c6b8078f64fa2f8fc56f881c2eb130ac2cb2ab (2026-05-03T23:20:30Z — PyPI Trusted Publishing + Zenodo readiness, v0.1.0 release).
Visibility: public (mirrors Zer0pa/Indus-Valley GitHub visibility).
Rights class of admitted content: derived integer IDs and cluster sequences only; no image bytes admitted; BLOCKED_RIGHTS material excluded per DATA_POLICY.md.

Canonical-location declaration

This (Zer0pa/Indus-Valley-lane-state) is the canonical lane mirror as of 2026-05-12. It supersedes the earlier private archive at Architect-Prime/gnosis-indus-artifacts, which is retained as a private archival fallback but is no longer authoritative. Both repos hold byte-identical content as of this wave; future updates land here first.

The legacy private model repo Architect-Prime/gnosis-indus-models (holding the Stage-4 structural adapter checkpoint) remains private by design: weight distribution is gated on Zer0pa legal clearance per NOTICE.md and the Gnosis Portfolio Licensing Intake. It is intentionally not mirrored here.

What is inside

Path	What it is
`Indus-Valley-source-14c6b807.tar.gz`	Wave-7 authoritative source tarball at GH HEAD `14c6b807`
`Indus-Valley-source-d6a8bb10fef8.tar.gz`	Wave-5 source tarball (preserved for provenance)
`repo/`	browsable mirror at GH HEAD `14c6b807` (98 files)
`backups/2026-04-27/indus_workspace_artifacts_2026-04-27.tar.zst`	Wave-5 workspace tarball — `/Users/zer0palab/Gnosis Portfolio/workstreams/gnosis-indus/` full state at 2026-04-27
`backups/2026-04-27/LANE_CHECKSUMS.sha256`	per-file SHA-256 over the workspace tarball
`migration-package/indus-migration-package.tar.gz`	Wave-6 migration-package tarball (24 files, 172 KB uncompressed) covering `00_brief/`, `01_prd_and_authority/`, `02_source_inventory/`, `03_data_policy/`, `04_evidence_manifest/`, `06_handover/`, and the workspace README
`migration-package/MIGRATION_PACK_SHA256.txt`	per-file SHA-256 manifest for the migration-package
`migration-package/uncompressed/`	browsable mirror of the migration-package content
`product-page-build/2026-05-12/`	Phase-1 static product page for the FPO Product-Page Wave dispatch; `index.html` + 5 PNG receipts + `product-page-audit.json`
`lane-asks/2026-05-12/`	lane orchestration state — `HANDOVER_2026-05-04.md` + `INDEX.md`
`MANIFEST.txt`	Wave-5 manifest text (historical)
`WAVE7_MANIFEST.md`	Wave-7 manifest text (durability refresh)
`WAVE7_CHECKSUMS.sha256`	Wave-7 SHA-256 checksums
`WAVE8_CANONICAL_NOTE.md`	this wave's consolidation notes
`README_legacy_AP_2026-04-27.md`	the Wave-5 README from `Architect-Prime/gnosis-indus-artifacts` (provenance)

Reproduction (post-Mac-wipe)

# Authenticate
hf auth login --token "$HF_TOKEN"          # token name: Live Project Storage
gh auth login                              # Zer0pa-Architect-Prime

# Pull the canonical lane mirror
hf download --repo-type dataset Zer0pa/Indus-Valley-lane-state \
  --local-dir ./indus-valley-lane-state

# Restore the GitHub repo (PyPI v0.1.0 release point)
git clone https://github.com/Zer0pa/Indus-Valley.git
cd Indus-Valley && git checkout 14c6b8078f64fa2f8fc56f881c2eb130ac2cb2ab

# Re-render the product page (Phase-1 static; needs only a browser)
cd ../indus-valley-lane-state/product-page-build/2026-05-12
python3 -m http.server 4640
# Open http://127.0.0.1:4640/ — Pretext loads from unpkg CDN

# Reproduce the lane runtime
cd ../../repo && pip install -e ".[test]" && pytest
# Expected: 14 passed

What this register does not claim

Does not claim decipherment of the Indus script. Phase 5 leaves substrate identification unresolved.
Does not carry sign-image bytes; image rights stay BLOCKED_RIGHTS per DATA_POLICY.md.
Does not include the full k=70 catalogue (412 signs / 70 clusters / 179 inscriptions); that remains FETCH_EXTERNAL per DATA_POLICY.md. The bundled demo fixture is small and authority-anchored.
Does not include the Stage-4 structural adapter weights; those stay in Architect-Prime/gnosis-indus-models (private) pending legal clearance.
Does not override the consuming GitHub repo's NOTICE.md legal posture. Every artifact's rights class is set there.

Update protocol

This dataset must be refreshed whenever:

GitHub Zer0pa/Indus-Valley HEAD advances and the advancement is scientifically or structurally meaningful;
the lane produces a new product-page render, audit packet, or landing-card snapshot worth durability-checkpointing;
the lane orchestration state (lane-asks/Indus-Valley/) gains a new handover or ask-queue entry;
the consuming GitHub repo's HF_CUSTODY_REGISTER.md declares a new wave.

The procedure is: stage local changes, run SHA-256 over them, hf upload --repo-type dataset Zer0pa/Indus-Valley-lane-state …, verify roundtrip, then commit the wave note to GitHub's HF_CUSTODY_REGISTER.md.

Acceptance gate

After a Mac wipe, the lane can be fully resumed from Zer0pa/Indus-Valley (GitHub) + this dataset only. No other local state is required.