Migrating a Team from Shared Folders to LoRADock

Provide a staged artifact migration that preserves provenance. The useful result is a method that preserves evidence, exposes constraints, and makes the next decision reviewable. This note describes an engineering workflow rather than a claim about a particular organization or production event.

Establish the boundary

Inventory files, duplicate names, missing metadata, and uncertain ownership. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Use a fixed holdout or review sample for this step. It should include normal records, rare boundary cases, and at least one input designed to fail safely. A useful change improves the intended condition without removing evidence about a known limitation.

A minimum manifest before importing any weight file

Define a minimum manifest before importing any weight file. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Compute digests and group identical files

Compute digests and group identical files. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Assign stable slugs and initial versions without rewriting history

Assign stable slugs and initial versions without rewriting history. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Import public and restricted artifacts separately

Import public and restricted artifacts separately. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

A parallel period before making the registry authoritative

Run a parallel period before making the registry authoritative. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Practical check

Bash inventory commands and a CSV manifest template. The example below is intentionally small enough to run as a preflight check before a longer release, migration, or build workflow.

curl -fsSLO https://your-instance.example/download/qwen7b-ticket-triage
shasum -a 256 qwen7b-ticket-triage

Evidence for the next decision

Keep the input digest, outcome, and reviewer note with the resulting artifact or postmortem. Treating folder timestamps as reliable training dates. When the current evidence is incomplete, preserve the failing example, define the missing validation, and defer promotion until the result can be compared fairly.

Make the process idempotent. Repeating the same step on unchanged input should not append metadata, discard extra detail, or silently change ownership. Idempotence makes retries safe and exposes hidden state when outputs differ.

Review results by failure category rather than a single blended number. A small number of high-risk failures can outweigh an improvement on common cases, particularly when the output feeds a release or escalation workflow.

Keep accepted and rejected examples together. A concise rejected sample with its expected outcome is a durable regression test and prevents the same edge condition from returning as an unexplained surprise.

Use a separate holdout set for release decisions. Training records can guide implementation, but they cannot demonstrate that the process behaves correctly on new wording, new sources, or a changed input order.