[FEATURE] Build the Coreutils text scenario through the owned native graph #599

Open
opened 2026-11-08 12:15:00 +01:00 by erikinkinen · 1 comment
Owner

Problem and motivation

The maintained Coreutils text scenario exercises SHA2, pipelines, pathname operations and offline manuals. The owned native image graph currently projects only the Directory scenario, so it cannot produce the matching launch policy through that same graph.

Proposed behavior and scope

Add explicit selection of the existing Coreutils text scenario. Preserve all 77 component roles and 79 baseline actions, including genuine native SHA2 and Boot-tool products. Select the original dev VM runtime, Rootd initial-shell/text-script policy, normal Exsh catalog and Kernel runtime harness. Keep the Directory companion and its catalog exclusive to the Directory case.

Authority, security and reliability

Retain and compare the actual scenario and runtime bytes against the selected Integration source before generated Cargo or native work. Scenario names and configuration data grant no source or execution authority. Preserve original producer, product, helper and image lifetimes, sticky refusal and cleanup duties. Keep existing build and guest deadlines unchanged; never reuse an earlier ELF as a new graph product.

Acceptance criteria

  • Project the complete maintained Coreutils text recipe from the original source while preserving the baseline graph.
  • Keep Directory-specific companion inputs and catalogs confined to that scenario; reject mixed selections and substituted source/runtime bytes before effects.
  • Preserve the exact SHA2, pathname, manual and text markers, ordering, uniqueness, refusal markers and guest limits.
  • Cover both recipe projections, unsupported combinations, source substitution and sticky failure; update operator and architecture documentation.
  • Build the matching image through its original graph and run the authenticated guest workload with its full oracle.

Alternatives and tradeoffs

The legacy image recipe already expresses this workload, but does not demonstrate the owned native graph-to-image route. Sharing a closed scenario dispatcher avoids duplicating ownership logic while keeping recipe-specific products explicit.

Tracking and rollout

Build on the Directory graph producer and its scenario design. Implement on a separate feature branch without changing the active Directory build. Image and guest acceptance remain separate from source completion.

Implementation: #600.

## Problem and motivation The maintained Coreutils text scenario exercises SHA2, pipelines, pathname operations and offline manuals. The owned native image graph currently projects only the Directory scenario, so it cannot produce the matching launch policy through that same graph. ## Proposed behavior and scope Add explicit selection of the existing Coreutils text scenario. Preserve all 77 component roles and 79 baseline actions, including genuine native SHA2 and Boot-tool products. Select the original dev VM runtime, Rootd initial-shell/text-script policy, normal Exsh catalog and Kernel runtime harness. Keep the Directory companion and its catalog exclusive to the Directory case. ## Authority, security and reliability Retain and compare the actual scenario and runtime bytes against the selected Integration source before generated Cargo or native work. Scenario names and configuration data grant no source or execution authority. Preserve original producer, product, helper and image lifetimes, sticky refusal and cleanup duties. Keep existing build and guest deadlines unchanged; never reuse an earlier ELF as a new graph product. ## Acceptance criteria - [x] Project the complete maintained Coreutils text recipe from the original source while preserving the baseline graph. - [x] Keep Directory-specific companion inputs and catalogs confined to that scenario; reject mixed selections and substituted source/runtime bytes before effects. - [x] Preserve the exact SHA2, pathname, manual and text markers, ordering, uniqueness, refusal markers and guest limits. - [x] Cover both recipe projections, unsupported combinations, source substitution and sticky failure; update operator and architecture documentation. - [ ] Build the matching image through its original graph and run the authenticated guest workload with its full oracle. ## Alternatives and tradeoffs The legacy image recipe already expresses this workload, but does not demonstrate the owned native graph-to-image route. Sharing a closed scenario dispatcher avoids duplicating ownership logic while keeping recipe-specific products explicit. ## Tracking and rollout Build on [the Directory graph producer](https://git.erikinkinen.fi/erix/integration/pulls/598) and its [scenario design](https://git.erikinkinen.fi/erix/integration/issues/594). Implement on a separate feature branch without changing the active Directory build. Image and guest acceptance remain separate from source completion. Implementation: [#600](https://git.erikinkinen.fi/erix/integration/pulls/600).
erikinkinen added this to the Alpha 1 milestone 2026-11-08 12:15:00 +01:00
Author
Owner

The source implementation is published in #600. The text recipe retains the 79 baseline actions and normal Exsh catalog, while Directory keeps its separate companion. Matching image and guest acceptance remain open.

The source implementation is published in [#600](https://git.erikinkinen.fi/erix/integration/pulls/600). The text recipe retains the 79 baseline actions and normal Exsh catalog, while Directory keeps its separate companion. Matching image and guest acceptance remain open.
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#599
No description provided.