[FEATURE] Retain ordinary service artifact build ownership #394

Open
opened 2026-11-06 11:20:59 +01:00 by erikinkinen · 4 comments
Owner

Problem and motivation

Ordinary Rootd, Procd and Ttyd artifacts need a build route that retains original source, Cargo and compiler ownership through artifact validation and cleanup. This is required to assemble the coherent service image for self-hosting.

Proposed behavior and scope

Add a closed ordinary-service graph and compiler route using the existing lifetime machinery. Bind exact package, source, features, dependency aliases and complete shared-library closure. Produce matching registry objects and native C companions from the selected provider graph. Preserve the process-root workload contracts.

Authority, security and reliability

Retain original input, compiler, output and cleanup owners until completion. Hashes and descriptions cannot replace those owners. Reject source or feature substitution, stale compiler outputs, mismatched registry objects and incomplete cleanup. Add no native capability grants or discovery routes.

Acceptance criteria

  • Document the ordinary-service/source/registry boundary and dependency graph.
  • Implement the complete Rootd, Procd and Ttyd graph and compiler path.
  • Preserve process-root behavior and test substitution, loss and cleanup failures.
  • Produce and validate real service artifacts with the matching shared registry.
  • Exercise the coherent release image and retain source-linked evidence.

Alternatives and tradeoffs

Sharing the retained primitives avoids a second ownership implementation. Ordinary services keep separate admission rules from process-root workloads. A raw Cargo executable proves compilation, but does not establish the dynamic service artifact contract.

Tracking and rollout

Track release acceptance in #65. Land source/registry prerequisites, then the ordinary compiler route and image integration. Remove superseded ordinary build paths after their consumers migrate. Keep the full in-EriX and external-toolchain rebuild requirements.

## Problem and motivation Ordinary Rootd, Procd and Ttyd artifacts need a build route that retains original source, Cargo and compiler ownership through artifact validation and cleanup. This is required to assemble the coherent service image for self-hosting. ## Proposed behavior and scope Add a closed ordinary-service graph and compiler route using the existing lifetime machinery. Bind exact package, source, features, dependency aliases and complete shared-library closure. Produce matching registry objects and native C companions from the selected provider graph. Preserve the process-root workload contracts. ## Authority, security and reliability Retain original input, compiler, output and cleanup owners until completion. Hashes and descriptions cannot replace those owners. Reject source or feature substitution, stale compiler outputs, mismatched registry objects and incomplete cleanup. Add no native capability grants or discovery routes. ## Acceptance criteria - [x] Document the ordinary-service/source/registry boundary and dependency graph. - [ ] Implement the complete Rootd, Procd and Ttyd graph and compiler path. - [ ] Preserve process-root behavior and test substitution, loss and cleanup failures. - [ ] Produce and validate real service artifacts with the matching shared registry. - [ ] Exercise the coherent release image and retain source-linked evidence. ## Alternatives and tradeoffs Sharing the retained primitives avoids a second ownership implementation. Ordinary services keep separate admission rules from process-root workloads. A raw Cargo executable proves compilation, but does not establish the dynamic service artifact contract. ## Tracking and rollout Track release acceptance in [#65](https://git.erikinkinen.fi/erix/integration/issues/65). Land source/registry prerequisites, then the ordinary compiler route and image integration. Remove superseded ordinary build paths after their consumers migrate. Keep the full in-EriX and external-toolchain rebuild requirements.
erikinkinen added this to the Alpha 1 milestone 2026-11-06 11:20:59 +01:00
Author
Owner

The retained ordinary-service DSO route is now isolated in #424. A fresh native fixture builds two transitive shared libraries, the actual C companion and an inspected service ELF under the same retained operation, with confirmed cleanup. Complete current-service artifacts, image composition and guest acceptance remain open.

The retained ordinary-service DSO route is now isolated in [#424](https://git.erikinkinen.fi/erix/integration/pulls/424). A fresh native fixture builds two transitive shared libraries, the actual C companion and an inspected service ELF under the same retained operation, with confirmed cleanup. Complete current-service artifacts, image composition and guest acceptance remain open.
Author
Owner

Retained compilation inputs are now isolated in #425, following #424. The consumer keeps actual source and checkout descriptors while preserving current byte, namespace, lock and tool checks. A fresh native service fixture passes. Complete current-service performance and guest acceptance remain open; separate Cargo producers still require their own phase admission.

Retained compilation inputs are now isolated in [#425](https://git.erikinkinen.fi/erix/integration/pulls/425), following #424. The consumer keeps actual source and checkout descriptors while preserving current byte, namespace, lock and tool checks. A fresh native service fixture passes. Complete current-service performance and guest acceptance remain open; separate Cargo producers still require their own phase admission.
Author
Owner

Split source comparison and read accounting into #426 and #427, stacked on #425. Comparisons retain the compilation consumer’s original file owners and still read current bytes and check the complete namespace. Accounting preserves the full row totals and error order while reducing repeated path work. Both remain WIP for current-service, image and guest acceptance.

Split source comparison and read accounting into #426 and #427, stacked on #425. Comparisons retain the compilation consumer’s original file owners and still read current bytes and check the complete namespace. Accounting preserves the full row totals and error order while reducing repeated path work. Both remain WIP for current-service, image and guest acceptance.
Author
Owner

The file-identity optimization is split into #430. It constructs the same nine-field observation directly and shares it with the service scope, preserving fresh source checks and original failure order. Full current-service timing and image/guest acceptance remain open.

The file-identity optimization is split into #430. It constructs the same nine-field observation directly and shares it with the service scope, preserving fresh source checks and original failure order. Full current-service timing and image/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#394
No description provided.