[FEATURE] Prepare complete source inputs before artifact production #643

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

Problem and motivation

The production source exporter requires a complete artifact-production contract before preparing source inputs. That couples source preparation to recipes for outputs that have not yet been implemented, including the native compiler toolchain.

Proposed behavior and scope

Add a separate complete source-input catalog and entry point. Prepare every selected repository, tracked file, generated Cargo input and original Git object through the existing fresh original producers. Keep incomplete production contracts explicit and preserve their final acceptance requirements.

Authority, security and reliability

Catalog rows select literal input data. They cannot supply owners, adopt old completions or authorize network discovery. Retain actual source, native, descriptor and output duties through positive retirement. The existing production-inventory admission remains strict and compatible.

Acceptance criteria

  • Cover the complete selected repository map, with exact commits, full tracked-file identities, Git integrity and Cargo closure.
  • Produce fresh inputs through original Git/Cargo actors and independently admit the complete tracked/generated/object result for an explicitly selected input set.
  • Reject missing or foreign roles, changed bytes, substituted receivers, unselected inputs and uncertain retirement.
  • Join the exact prepared source identities to the unchanged production contract before full build acceptance; preserve every outstanding native and external-toolchain requirement.
  • Document the two contracts and demonstrate the complete source path under explicit measured resource bounds.

Alternatives and tradeoffs

Forcing an incomplete production inventory to claim completeness would hide missing work. Keeping the current ordering makes source preparation depend on later output recipes. A separate source contract adds an interface, but keeps the two obligations explicit.

Tracking and rollout

Supports #8 and #65. Reuse the existing original constructors and keep the production entry point unchanged. The full EriX build, images, in-EriX rebuild and external toolchain rebuild remain required.

## Problem and motivation The production source exporter requires a complete artifact-production contract before preparing source inputs. That couples source preparation to recipes for outputs that have not yet been implemented, including the native compiler toolchain. ## Proposed behavior and scope Add a separate complete source-input catalog and entry point. Prepare every selected repository, tracked file, generated Cargo input and original Git object through the existing fresh original producers. Keep incomplete production contracts explicit and preserve their final acceptance requirements. ## Authority, security and reliability Catalog rows select literal input data. They cannot supply owners, adopt old completions or authorize network discovery. Retain actual source, native, descriptor and output duties through positive retirement. The existing production-inventory admission remains strict and compatible. ## Acceptance criteria - [ ] Cover the complete selected repository map, with exact commits, full tracked-file identities, Git integrity and Cargo closure. - [x] Produce fresh inputs through original Git/Cargo actors and independently admit the complete tracked/generated/object result for an explicitly selected input set. - [ ] Reject missing or foreign roles, changed bytes, substituted receivers, unselected inputs and uncertain retirement. - [ ] Join the exact prepared source identities to the unchanged production contract before full build acceptance; preserve every outstanding native and external-toolchain requirement. - [ ] Document the two contracts and demonstrate the complete source path under explicit measured resource bounds. ## Alternatives and tradeoffs Forcing an incomplete production inventory to claim completeness would hide missing work. Keeping the current ordering makes source preparation depend on later output recipes. A separate source contract adds an interface, but keeps the two obligations explicit. ## Tracking and rollout Supports #8 and #65. Reuse the existing original constructors and keep the production entry point unchanged. The full EriX build, images, in-EriX rebuild and external toolchain rebuild remain required.
erikinkinen added this to the Alpha 1 milestone 2026-11-10 02:18:09 +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#643
No description provided.