Datasets:

Zer0pa
/

Indus-Valley-lane-state

Trigger: urgent storage / auth / cleanup brief — operator authorized (and now requires) use of the Zer0pa org HF allocation for lane durability. The 2026-04-27 direction "no Zer0pa-org HF storage for this lane" is superseded by the 2026-05-12 brief ("USE THE ORGANIZATION STORAGE ALLOCATION UNLESS IT IS FULL/FILLING"). Visibility is set to public to mirror the underlying GitHub repo (Zer0pa/Indus-Valley is public).

Token identity verified: Architect-Prime (org Zer0pa) via hf auth whoami on the live HF Hub; HF token name Live Project Storage.

What Wave 8 changed

Created Zer0pa/Indus-Valley-lane-state (HF dataset, public).
Mirrored the full contents of Architect-Prime/gnosis-indus-artifacts (Wave-5 + Wave-6 + Wave-7) into the new canonical Zer0pa-org dataset; 153 files; 8.6 MB local snapshot.
Declared Zer0pa/Indus-Valley-lane-state as the canonical lane mirror via README and via the on-GitHub HF_CUSTODY_REGISTER.md Wave-8 section.
Retained Architect-Prime/gnosis-indus-artifacts (private) as an archival fallback — not deleted, no longer authoritative. Both repos are byte-identical as of this wave.
Did not touch Architect-Prime/gnosis-indus-models (still private). Stage-4 structural adapter weights remain legally-gated per NOTICE.md and the Gnosis Portfolio Licensing Intake; weight distribution requires Zer0pa legal clearance. This is by design and is not a fragmentation gap.

Rights-class check

Every artifact in this dataset has already been rights-class-cleared during Wave-5/6/7. Specifically:

The Wave-5 source tarball, the Wave-7 source tarball, and the browsable repo/ mirror all derive from Zer0pa/Indus-Valley GitHub, which is public.
The backups/2026-04-27/indus_workspace_artifacts_2026-04-27.tar.zst workspace tarball was admitted under the Wave-5 rule "derived integer IDs and cluster sequences only; no image bytes admitted; BLOCKED_RIGHTS material excluded". The same constraint applies to its public mirror here.
The migration-package/ content consists of governance docs (PRD, AUTHORITY_INDEX, EVIDENCE_MANIFEST, data-policy summary, source inventory, handover) — all suitable for public review.
The product-page-build/2026-05-12/ artifacts are derived exclusively from the public GitHub README and public §A truth envelope.
The lane-asks/2026-05-12/ files are lane orchestration handover documents — no operator credentials, no embargoed claims.

No BLOCKED_RIGHTS material is published in this wave. Image bytes remain off this dataset. The full k=70 catalogue remains FETCH_EXTERNAL per DATA_POLICY.md.

Org-quota awareness

The brief notes that multiple agents are pushing simultaneously. I followed the naming convention used by peer lanes (Zer0pa/<LaneName>-lane-state) — e.g. Zer0pa/ZPE-FT-lane-state, Zer0pa/ZPE-Geo-lane-state, Zer0pa/ZPE-Image-lane-state, Zer0pa/ZPE-Mocap-lane-state, Zer0pa/ZPE-Bio-lane-state. The new dataset is 8.6 MB; no quota concern at this size class.

Acceptance gate (this wave)

After this wave, a Mac wipe is safe. Reproduction path:

gh auth login                              # Zer0pa-Architect-Prime
hf auth login --token "$HF_TOKEN"          # Live Project Storage
hf download --repo-type dataset Zer0pa/Indus-Valley-lane-state \
  --local-dir ./indus-valley-lane-state
git clone https://github.com/Zer0pa/Indus-Valley.git

That is sufficient to fully resume the lane.

Migration audit trail

Source (HF)	Destination (HF)	Notes
`Architect-Prime/gnosis-indus-artifacts` (private)	`Zer0pa/Indus-Valley-lane-state` (public)	full byte-mirror; canonical pointer moved to Zer0pa-org
`Architect-Prime/gnosis-indus-models` (private)	(unchanged)	stays private per legal-clearance gate; NOT migrated