[FEATURE] Package generated Cargo locks as explicit offline inputs #192

Open
opened 2026-10-24 11:45:10 +02:00 by erikinkinen · 1 comment
Owner

Problem and motivation

The offline source bundle contains exact tracked Git trees. Cargo also produces final root lockfiles, which cannot be inserted into those trees without breaking their original identity. The build needs a separate, verifiable generated-input section.

Proposed behavior and scope

Export the final root lockfiles from their actual completed Cargo preparation owner. Extend the existing build-scope inventory with versioned lock records and explicit workspace/member coordinates. Copy the exact lock bytes into a fresh, separately selected generated-input root. Offline admission checks the complete lock set and its selected original source bindings.

Authority, security and reliability

Require the actual completing owner and identity-registered completion view; a status file or equivalent dictionary cannot reconstruct ownership. Preserve distinct runtime/tooling roles and exact main SourceIDs. Use retained no-follow directory/file handles, caller budgets and existing once-only cleanup. Reject missing, extra, changed and escaping inputs. Export must not run Cargo or Git, refresh a lock, rewrite a manifest, manufacture Git objects or transport a Cargo home/cache. Hashes select bytes; they do not prove publisher identity or guest execution.

Acceptance criteria

  • Retain final lock completion only after every original resolution and final input check succeeds.
  • Record actual workspace roots, members, final lock bytes and exact source-role bindings in the existing versioned inventory.
  • Export into an explicit fresh generated-input root while preserving all tracked source bytes and their identity.
  • Admit the complete exact offline lock set; reject substitutions, extra/missing entries, wrong modes, path escapes and mismatched SourceIDs.
  • Cover foreign or incomplete owners, multiple workspaces and source roles, partial copy, interruption and cleanup without producer replay.
  • Update CLI help, component documents, source-bundle guidance and the technical manual.

Alternatives and tradeoffs

Copying a Cargo home would mix generated locks with host-specific paths, mutable caches and unrelated state. Explicit generated inputs keep portable lock bytes separate from original source objects. The dependency graph and guest-local source mapping need their own complete contracts.

Tracking and rollout

Extends offline source bundles. Complete dependency-graph metadata, original Git object transport, toolchain inputs, guest installation and full self-hosting remain separate requirements.

## Problem and motivation The offline source bundle contains exact tracked Git trees. Cargo also produces final root lockfiles, which cannot be inserted into those trees without breaking their original identity. The build needs a separate, verifiable generated-input section. ## Proposed behavior and scope Export the final root lockfiles from their actual completed Cargo preparation owner. Extend the existing build-scope inventory with versioned lock records and explicit workspace/member coordinates. Copy the exact lock bytes into a fresh, separately selected generated-input root. Offline admission checks the complete lock set and its selected original source bindings. ## Authority, security and reliability Require the actual completing owner and identity-registered completion view; a status file or equivalent dictionary cannot reconstruct ownership. Preserve distinct runtime/tooling roles and exact main SourceIDs. Use retained no-follow directory/file handles, caller budgets and existing once-only cleanup. Reject missing, extra, changed and escaping inputs. Export must not run Cargo or Git, refresh a lock, rewrite a manifest, manufacture Git objects or transport a Cargo home/cache. Hashes select bytes; they do not prove publisher identity or guest execution. ## Acceptance criteria - [ ] Retain final lock completion only after every original resolution and final input check succeeds. - [ ] Record actual workspace roots, members, final lock bytes and exact source-role bindings in the existing versioned inventory. - [ ] Export into an explicit fresh generated-input root while preserving all tracked source bytes and their identity. - [ ] Admit the complete exact offline lock set; reject substitutions, extra/missing entries, wrong modes, path escapes and mismatched SourceIDs. - [ ] Cover foreign or incomplete owners, multiple workspaces and source roles, partial copy, interruption and cleanup without producer replay. - [ ] Update CLI help, component documents, source-bundle guidance and the technical manual. ## Alternatives and tradeoffs Copying a Cargo home would mix generated locks with host-specific paths, mutable caches and unrelated state. Explicit generated inputs keep portable lock bytes separate from original source objects. The dependency graph and guest-local source mapping need their own complete contracts. ## Tracking and rollout Extends [offline source bundles](https://git.erikinkinen.fi/erix/integration/issues/191). Complete dependency-graph metadata, original Git object transport, toolchain inputs, guest installation and full self-hosting remain separate requirements.
Author
Owner

The completing Cargo owner now exposes its registered final-lock view to the existing pipeline. Inventory v2, two-root export, offline checking and ordinary output-receipt checking are implemented and committed locally. Workspace coordinates come from Cargo; selected rows are immutable, and explicit time/material allowances cover the export.

The component and technical manuals are updated. Coordinated publication remains pending. Complete dependency-graph transport, guest-local source mapping and toolchain closure remain open.

The completing Cargo owner now exposes its registered final-lock view to the existing pipeline. Inventory v2, two-root export, offline checking and ordinary output-receipt checking are implemented and committed locally. Workspace coordinates come from Cargo; selected rows are immutable, and explicit time/material allowances cover the export. The component and technical manuals are updated. Coordinated publication remains pending. Complete dependency-graph transport, guest-local source mapping and toolchain closure remain open.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:22 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#192
No description provided.