Skip to main content

Module migration

Module migration 

Source
Expand description

Explicit operator-only legacy migration. Never used by model tools or startup.

Each atomic source is the original project’s built-in JSONL file and validated context archives. Preview contains counts and hashes, never bodies, tags, IDs or notes. Sources are opened read-only, nofollow, without creating directories/lock files. Apply rereads and verifies the preview and sends ONE <=24 MiB transaction. It never edits config, deletes source, switches selection or performs dual writes. Stop legacy writers for cutover: file locks are advisory, and old appenders do not participate in them. Retained descriptors plus a second read detect changes before dispatch; they cannot make uncooperative legacy processes transactional.

Structs§

MigrationManifest
Safe to display to the operator: fixed-size metadata, never source text.

Enums§

MigrationSource
Explicit operator source. These paths/aliases must never originate in a model tool parameter. No automatic plugin discovery or prefix conversion.

Constants§

MAX_APPLY_BYTES
The complete RPC envelope, not merely its records, must fit this limit.

Functions§

apply
Operator-only apply; the source is freshly read and checked, never taken from an editable saved preview. Only metadata is returned by the service. On an unknown commit, retry this same preview, not a newly generated record set.
apply_from
preview_from
preview_in
Offline preview. Does not start the service or create/open a destination brain.