railiance-fabric/docs/registry-reset-operations.md

Registry Reset Operations

RAIL-FAB-WP-0016 allows a destructive registry graph reset, but only after an archive has been produced and the operator uses an explicit confirmation token.

Export Archive Only

railiance-fabric registry export-reset-archive \
  .railiance-fabric/reset-archive.json \
  --registry-url http://127.0.0.1:8765

The archive contains:

• repository registrations,
• current combined graph export,
• stored graph snapshots,
• discovery snapshots and accepted graph snapshot links,
• artifacts,
• library inventory,
• prior reset events,
• rollback notes.

Guarded Reset

railiance-fabric registry reset-graph-data \
  --registry-url http://127.0.0.1:8765 \
  --archive .railiance-fabric/reset-archive.json \
  --confirm RESET-RAILIANCE-FABRIC-GRAPH-DATA \
  --reason "canon-aligned graph reset before full reingest"

The command first writes the archive, computes its SHA-256, then calls the registry reset endpoint. The registry records a reset event with the archive path, archive checksum, reason, and dropped row counts.

The reset deletes graph snapshots, discovery snapshots, artifacts, and library inventory. Repository registration rows are preserved so reingest can start from the known repo list.

Rollback Limits

The archive is a JSON evidence bundle, not an automatic SQLite restore. Use it to inspect or manually reinsert prior registry data if needed. After reset, the intended source of truth is a fresh scan and acceptance pass over registered and local repositories using the canon-aligned model.

Do not run the reset until the replacement scanner/projection path has passed validation and a sample reingest review.