[FEATURE] Deliver and admit inventory-bound offline source bundles #191

Open
opened 2026-10-24 09:11:46 +02:00 by erikinkinen · 0 comments
Owner

Problem and motivation

An offline EriX build needs the complete selected source trees, recipes and configuration before it can start. The build-scope inventory already records those inputs, but the appliance currently carries built outputs and a revision list rather than a source bundle.

Proposed behavior and scope

Materialize a fresh source directory from the actual completed owned-source objects, using the existing build-scope inventory as the sole manifest. Keep inventory roles distinct, including separate runtime and tooling revisions of Integration. Add an offline admission command that takes the selected inventory digest and source root and rejects missing, extra or changed inputs before a build.

This first interface covers reviewed tracked-source trees. Generated Cargo locks, dependency metadata, external toolchain inputs, signing trust and installation into a guest build realm still need their own complete input contracts. A source-tree check alone does not establish a self-hosted build.

Authority, security and reliability

The caller supplies the original source owners, completed selections, inventory digest and fresh destination. Borrow their existing read authority; do not rediscover Git, branches, ignore rules or source locations. Check exact roles, revisions, paths, modes, sizes and hashes. Preserve original root and parent identities and literal link data; follow no unreviewed link.

Keep partial output and the original failure on interruption. Do not adopt an old destination, replay source production, copy compiled caches or turn serialized paths and coordinates into source ownership. A matching digest establishes consistency with the caller's selected input, not trust in a publisher.

Acceptance criteria

  • Reuse the existing complete build-scope inventory, with exact role and revision coverage and no second source manifest.
  • Produce a fresh bundle only from actual completed owned-source selections; retain their checks and partial-output ownership.
  • Admit the bundle offline through explicit root and inventory inputs, with exact path, mode, size and hash coverage.
  • Reject missing or extra roles and files, changed recipes/configuration/locks, stale inputs and root or parent substitution; retain supported literal-link semantics.
  • Cover partial production and interruption, distinct Integration revisions, and extra Git, target or output trees without ignore-based exceptions.
  • Document the CLI, ownership and remaining generated-input/toolchain contracts, including the technical manual.

Alternatives and tradeoffs

A new archive manifest would duplicate the inventory and invite conflicting source selections. Copying an existing checkout or appliance also carries discovery rules or build outputs that do not belong in this input boundary. A directory bundle lets the guest consume reviewed source bytes without a Git service; archive transport and signing can be layered onto the same inventory later.

Tracking and rollout

Continue the build-realm work, build-scope inventory and Integration review. Establish source-tree delivery and admission first, then join generated Cargo inputs through their existing contracts before claiming a complete offline build bundle.

## Problem and motivation An offline EriX build needs the complete selected source trees, recipes and configuration before it can start. The build-scope inventory already records those inputs, but the appliance currently carries built outputs and a revision list rather than a source bundle. ## Proposed behavior and scope Materialize a fresh source directory from the actual completed owned-source objects, using the existing build-scope inventory as the sole manifest. Keep inventory roles distinct, including separate runtime and tooling revisions of Integration. Add an offline admission command that takes the selected inventory digest and source root and rejects missing, extra or changed inputs before a build. This first interface covers reviewed tracked-source trees. Generated Cargo locks, dependency metadata, external toolchain inputs, signing trust and installation into a guest build realm still need their own complete input contracts. A source-tree check alone does not establish a self-hosted build. ## Authority, security and reliability The caller supplies the original source owners, completed selections, inventory digest and fresh destination. Borrow their existing read authority; do not rediscover Git, branches, ignore rules or source locations. Check exact roles, revisions, paths, modes, sizes and hashes. Preserve original root and parent identities and literal link data; follow no unreviewed link. Keep partial output and the original failure on interruption. Do not adopt an old destination, replay source production, copy compiled caches or turn serialized paths and coordinates into source ownership. A matching digest establishes consistency with the caller's selected input, not trust in a publisher. ## Acceptance criteria - [ ] Reuse the existing complete build-scope inventory, with exact role and revision coverage and no second source manifest. - [ ] Produce a fresh bundle only from actual completed owned-source selections; retain their checks and partial-output ownership. - [ ] Admit the bundle offline through explicit root and inventory inputs, with exact path, mode, size and hash coverage. - [ ] Reject missing or extra roles and files, changed recipes/configuration/locks, stale inputs and root or parent substitution; retain supported literal-link semantics. - [ ] Cover partial production and interruption, distinct Integration revisions, and extra Git, target or output trees without ignore-based exceptions. - [ ] Document the CLI, ownership and remaining generated-input/toolchain contracts, including the technical manual. ## Alternatives and tradeoffs A new archive manifest would duplicate the inventory and invite conflicting source selections. Copying an existing checkout or appliance also carries discovery rules or build outputs that do not belong in this input boundary. A directory bundle lets the guest consume reviewed source bytes without a Git service; archive transport and signing can be layered onto the same inventory later. ## Tracking and rollout Continue the [build-realm work](https://git.erikinkinen.fi/erix/integration/issues/8), [build-scope inventory](https://git.erikinkinen.fi/erix/integration/issues/1) and [Integration review](https://git.erikinkinen.fi/erix/integration/pulls/12). Establish source-tree delivery and admission first, then join generated Cargo inputs through their existing contracts before claiming a complete offline build bundle.
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#191
No description provided.