[FEATURE] Execute the original native graph from complete source-input bundles #652

Open
opened 2026-11-10 05:34:37 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Complete source preparation and native artifact execution have different acceptance boundaries. The existing offline graph accepts a complete production inventory, while the maintained source-input bundle already describes the tracked files, generated Cargo inputs and original Git objects needed to begin fresh producers. Requiring later release outputs at this intake prevents using those prepared inputs for the original native build.

Proposed behavior and scope

Add an explicit, closed source-input-bundle offline execution selection to Integration. Admit every selected role and all three byte roots through an actual SourceInputAdmission, then retain the original graph, matrix, code, tools, caller and source lifetimes while genuine fresh Git/Cargo/native producers execute. Keep the legacy production-inventory route and strict final production join unchanged. This does not mark release obligations, a native prefix, an image or guest behavior complete.

Authority, security and reliability

Wire paths, hashes and metadata remain descriptive inputs. Register the actual reader before acquisition and require its full successful byte verification before exposing original object-role views. Preserve exact original recipients, full role coverage, registry members, ancestry, byte charges, native limits and independent cleanup. Refuse mixed/partial selections, replacement/copy, mutation, withdrawal and unsettled consumers. There is no acquisition fallback, reconstructed producer, constructor bypass or success-status conversion.

Acceptance criteria

  • Add distinct literal CLI selection and document its execution versus final acceptance boundary.
  • Execute genuine small dependency/source/library producers from a complete source-only bundle with fresh admission and no acquisition fallback.
  • Check actual full-reader completion and original object-view identity/coverage before borrowing.
  • Refuse missing inputs, source/lock mismatch, copied or changed actors, aliasing and withdrawal; preserve first failure and original cleanup.
  • Keep existing strict production-v4/final-join controls and canonical graph role/action coverage.
  • Preserve original native owner interface and all resource clocks; regenerate complete source declarations.
  • Exercise the future full source/native/image/guest acceptance separately without reducing its obligations.

Alternatives and tradeoffs

Treating source-only inputs as a completed production inventory would conflate execution permission with later artifact acceptance. Keeping the existing complete-production route alone prevents independent source preparation from feeding fresh producers. Reuse the same initialized concrete source/object readers and fresh provider rather than creating a generic callback or metadata-to-owner mechanism.

Tracking and rollout

Depends on #643's independent source-input design and the prepared-source strict production join. Implement on a separate feature branch and compose normally after focused genuine controls. Existing strict routes remain compatible; no default fallback or global source-mode change is planned.

## Problem and motivation Complete source preparation and native artifact execution have different acceptance boundaries. The existing offline graph accepts a complete production inventory, while the maintained source-input bundle already describes the tracked files, generated Cargo inputs and original Git objects needed to begin fresh producers. Requiring later release outputs at this intake prevents using those prepared inputs for the original native build. ## Proposed behavior and scope Add an explicit, closed source-input-bundle offline execution selection to Integration. Admit every selected role and all three byte roots through an actual SourceInputAdmission, then retain the original graph, matrix, code, tools, caller and source lifetimes while genuine fresh Git/Cargo/native producers execute. Keep the legacy production-inventory route and strict final production join unchanged. This does not mark release obligations, a native prefix, an image or guest behavior complete. ## Authority, security and reliability Wire paths, hashes and metadata remain descriptive inputs. Register the actual reader before acquisition and require its full successful byte verification before exposing original object-role views. Preserve exact original recipients, full role coverage, registry members, ancestry, byte charges, native limits and independent cleanup. Refuse mixed/partial selections, replacement/copy, mutation, withdrawal and unsettled consumers. There is no acquisition fallback, reconstructed producer, constructor bypass or success-status conversion. ## Acceptance criteria - [ ] Add distinct literal CLI selection and document its execution versus final acceptance boundary. - [ ] Execute genuine small dependency/source/library producers from a complete source-only bundle with fresh admission and no acquisition fallback. - [ ] Check actual full-reader completion and original object-view identity/coverage before borrowing. - [ ] Refuse missing inputs, source/lock mismatch, copied or changed actors, aliasing and withdrawal; preserve first failure and original cleanup. - [ ] Keep existing strict production-v4/final-join controls and canonical graph role/action coverage. - [ ] Preserve original native owner interface and all resource clocks; regenerate complete source declarations. - [ ] Exercise the future full source/native/image/guest acceptance separately without reducing its obligations. ## Alternatives and tradeoffs Treating source-only inputs as a completed production inventory would conflate execution permission with later artifact acceptance. Keeping the existing complete-production route alone prevents independent source preparation from feeding fresh producers. Reuse the same initialized concrete source/object readers and fresh provider rather than creating a generic callback or metadata-to-owner mechanism. ## Tracking and rollout Depends on #643's independent source-input design and the prepared-source strict production join. Implement on a separate feature branch and compose normally after focused genuine controls. Existing strict routes remain compatible; no default fallback or global source-mode change is planned.
erikinkinen added this to the Alpha 1 milestone 2026-11-10 05:34:37 +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#652
No description provided.