[FEATURE] Admit declared tool payloads through four isolated image profiles #4

Open
opened 2026-09-12 07:56:23 +02:00 by erikinkinen · 5 comments
Owner

Problem and motivation

Self-hosting needs imported development tools while trusted EriX implementation and clean images retain clean-room provenance. Packaging must distinguish the two and reject undeclared transitive runtime payloads.

Proposed behavior and scope

Implement versioned payload manifests, offline source/recipe records, explicit extended-dev and extended-release profiles, a reviewed release subset, and independent closure/contamination tests across all four image profiles. Keep every imported dependency traceable to a required tool.

This issue records planned work; its unchecked criteria are not implementation proof. The normative basis is Phase 6 and AC1–AC24.

Payload manifest format

The first format describes candidates without admitting them. Each record has a
unique ID, name and version, tool/library kind, explicit build-machine, EriX-host
and output targets, source archive digest, license expression and license/notice
file digests, recipe and ordered patch digests, selected features, declared
runtime dependencies, native dynamic-library names and their owning payloads,
and a realm-policy reference with its exact digest.

Paths name canonical relative files in the supplied offline record; the parser
never opens them, resolves installed tools or downloads sources. Hashes and
records describe bytes, not approval, source consumption or capabilities. The
realm-policy reference likewise creates no grant or default build realm.

Use a strict versioned TOML format with immutable parsed records. Reject unknown
fields, duplicate IDs or list members, missing digests, noncanonical paths,
unknown dependencies, cycles, target mismatches and dynamic-library owners
outside the declared runtime closure. Every native dynamic-library owner must
also be an explicit direct runtime dependency: a transitive path cannot replace
that native edge. Compute the complete closure iteratively so its size is bounded
by the caller's admitted input bytes, without a fixed dependency depth or
package-count limit.

The maintained manifest starts empty. Examples and tests contain only original
metadata fixtures; no upstream tool or runtime is approved by adding the schema.
Source ingestion, actual ELF checks, clean-profile exclusion, extended-image
selection and guest execution keep their own acceptance criteria.

Offline source ingestion and recipe storage

The byte-only pipeline takes complete immutable manifest, provenance and artifact bytes and explicit root IDs. Intake and decode require caller-admitted aggregate input allowances; export independently requires its output allowance before encoding allocation. Independently select the reviewed provenance catalog and its full digest. Its source rows bind payload name/version, upstream release or revision, archive digest and original review evidence; verify the supplied archive against both that catalog and the manifest. These records preserve the caller's review premise and do not approve sources or attest signature verification.

Supply every selected archive, license, notice, ordered patch, recipe, policy and provenance-evidence file by canonical relative label. Require exact closure and complete digest/identity coverage; refuse missing, extra, repeated, conflicting or changed inputs. Labels never trigger filesystem lookup. Keep imported bytes separate from EriX-authored source and trusted Cargo dependencies. No fetching, extraction, executable resolution, recipe execution or profile selection occurs.

Use strict version-one erix.payload-provenance and erix.payload-recipe TOML records. Recipes bind payload/source/patch/features, build/host/output targets, the complete explicit environment, exact tool version/target/digests, ordered literal argument vectors and working-directory labels, dependency recipe/input identities and expected output roles/kinds/paths. Check dependency owners, output roles and the complete acyclic recipe graph, including explicitly selected build-only dependencies. Environment/argv remain literal data without inherited keys or shell expansion. Expected outputs contain no invented build status.

Return a frozen content-addressed store with complete original bytes. Its portable ERIXPST1 schema-one framing carries a counted canonical ASCII JSON index and digest-sorted complete blob extents; labels and roles correlate actual bytes. Count complete intake, including supplied labels and selection metadata, before hashing/parsing. Export revalidation requires its own explicit aggregate input allowance; count exact framing/index/blob output before encoding allocation. Deduplication requires equal bytes and never refunds intake work. Introduce no incidental payload, tool, archive or dependency-depth ceiling.

Decode the entire canonical framing, exact extent/digest/role inventory and recipe relationships before returning a store. Refuse unknown versions, duplicate keys/blobs, noncanonical ordering, truncation, trailing data, tampering and missing/orphaned blobs. Reimport requires the independently selected provenance digest again; bundle consistency cannot supply approval authority. Equivalent complete inputs produce identical stored bytes while preserving semantic patch/command order. Add independent round-trip, malformed, identity, quota, scale and no-effect controls. Filesystem persistence, owned build execution, actual input consumption, ELF admission, four image profiles and guest use remain separate requirements.

Image profiles and packaging isolation

Use four explicit selections: dev, release, extended-dev and
extended-release. Existing development/release images remain clean-room.
Extended configurations explicitly inherit their corresponding maintained clean
configuration and retain non-clean-room provenance even with no imported roots.
Derive a separate dev/release runtime flavour for existing service and console
features; preserve Cargo's independent debug/release selection and native
capacity, filesystem and launch policy.

A byte-only resolver takes immutable labelled configuration bytes with a
caller-supplied aggregate allowance. Its filesystem adapter receives explicit
roots/selections, captures only original selected regular files and rejects
missing/ambiguous parents, links, escapes, changed files, cycles and conflicting
profile declarations before build or cache effects. Count complete labels/bytes
before parsing. Resolve iteratively within supplied storage without a fixed
inheritance-depth or file-count limit. Merge declared scalar/table values and
replace arrays as a whole, then apply the existing complete runtime validation.
Clean selections cannot inherit extended declarations; overrides, filenames,
aliases and environment labels cannot erase provenance.

After preflight, stage one canonical complete effective configuration and its
source-chain/profile identity. Every producer and consumer, including generated
boot configuration, uses the same bound bytes. Preserve the original selection
separately and revalidate the snapshot before use. Clear inherited exports and
emit only fixed quoted values derived from the resolved record. Share the
resolver across fixture, scenario, appliance and disk entry points. Profile
metadata creates no capability and changes no native boot table.

Select tool roots against the complete candidate manifest; require exact runtime
closure, build-input classification and target agreement. Extended release also
requires an independently selected reviewed workflow record with exact root
identities and rationale. Exclude development-only generators, test harnesses,
debuggers and network-fetch tools throughout its transitive closure; include a
dependency library only when a selected tool requires it. A name or feature flag
does not establish approval. The maintained candidate manifest is empty: that
does not supply a reviewed release workflow or complete release-subset evidence.
Requests for imported artifacts refuse before build/package effects until the
separate admission producer supplies genuine source, recipe, ELF, functional
and realm evidence. Do not add an approval boolean or a synthetic success record.

Carry original source/build identity, provenance, profile, closure and release
selection through executable/object/alias inventories. Renaming, hard links,
symlinks and lookup aliases preserve the underlying classification; reject
shadowing and mismatched target/body identities. Preserve native aliases,
fixtures, launch policy and assets. Imported libraries cannot enter trusted
EriX Cargo dependencies or replace its native shared-object registry. Common
native compiler caches may be reused only for identical source/compiler/flags
and roles. Bind packaging caches to the complete profile/import/workflow
identity and revalidate bodies and closure on every hit; directory names and
stored labels supply no provenance.

Create an immutable expected product and installation plan from the explicit
native producer declarations before staging enumeration or filesystem writes.
Declare every executable, transitive object, manifest, native asset, alias,
diagnostic fixture, script, timestamp seed and profile record. Retain the complete
profile/effective-configuration/source-chain/import tuple, producer role, intended
destination, full body and alias group. Enumerating an existing staging entry
cannot make it a wanted product. Unknown or imported products refuse clean-image
consumption; an empty import list cannot turn an extended image clean.

Bind that tuple and the complete transitive product classification through
executable, shared-object and registry caches. Independently inspect each cache's
whole namespace, entry types and bodies before restore or publication. A legacy
record lacking classification is a miss, not native or imported approval; a
failed read remains an error. Cache misses may invoke only the existing explicit
native producer. Include the new host modules in the complete builder input
closure without changing guest ELF or boot metadata formats.

The install plan retains raw pathname bytes, full Linux mode, applicable UID/GID,
logical bodies, exact symlink targets, special-node encodings and hard-link
groups. Preserve the existing private/coreutils/extop aliases, realm fixtures,
native assets and optional script/time additions. Plan formatter-generated root
and lost+found entries separately. Declare permitted inode sharing and exact
link counts; independent products must not acquire an accidental shared inode.
Serialized byte names use a canonical injective encoding with its expansion
charged before allocation. Add no text-encoding, name-count or traversal-depth
ceiling beyond the actual format constraints and caller allowances.

Walk the complete actual host staging and installed namespace independently of
the expected list. Reconcile regular files, directories, symlinks, FIFOs,
character devices, block devices and sockets, including complete byte names,
directory child sets, dot/dot-dot topology, full modes and logical bodies.
Never follow symlinks or create host special nodes while checking. Preserve fast,
slow and inline link targets and both supported device encodings. Device numbers
are data, not host routes. Refuse extra, missing, duplicate, truncated or changed
entries, unexpected inode sharing, directory cycles, unknown attributes/features
and uninspectable content. Format-reserved allocations remain distinct from the
user namespace; require a recognized clean read-only filesystem check and reject
orphaned or malformed allocations. This inventory does not certify free or slack
blocks.

The ext4 reader receives the wanted original read-only image description and
explicit tool roles. Retain original CLOEXEC witnesses and native signal custody
while granting only the image read role to the literal filesystem tool. Compose
the existing file-description and native child/reaper owners in a thematic
adapter; the current command-owner API has no descriptor-transfer or stream
intake operation and must not be presented as a generic file owner. Preregister
child, pipe, output and partial-acquisition records before effects. Unrelated
Bash, Cargo, compiler, Git and VM recipients receive no inventory descriptors.
Retire each original independently once; unknown acquisitions or closes remain
retained and refuse reuse. Numeric inode selectors and serialized paths cannot
select custody, cleanup or a replacement image.

Parse the selected tools' complete byte framing, not human-rendered filenames or
lines. Preserve embedded newlines, spaces, quotes, backslashes and non-UTF8 names.
Check exact inode ranges, recognized metadata fields, complete body extents and
EOF. An exit of zero cannot override refused operations, checksum retries,
unparsed diagnostics, partial output or unsupported geometry/features. Keep
stdout a non-TTY read role and disable pager creation. No mounting, tree extraction
or guest execution belongs to this adapter.

Reconcile the filesystem after every installer and optional later addition.
Construct and verify the complete appliance tree before archiving, then inspect
the actual tar stream without extraction, including raw names, symlinks,
hard-links, special records and complete regular bodies. Bound compressed,
expanded, PAX and sparse material; unrecognized forms refuse. Keep result receipts
outside the checked namespace. Check the entire ESP namespace and boot/native
seed bodies, then independently compare the assembled GPT data extent with the
verified ext4 bytes. Bind the complete final image before checksums, compression
and identity publication. Derived runtime disks carry explicit profile data and
verify their copied data extent; they cannot discover a different packet or
fallback backend.

Every caller supplies finite total/quiet clocks and aggregate source, image-read,
logical-body, transport, record/path and encoded-output allowances. Charge input,
retained copies, requested reads, names, encoding expansion, writes and readback
before allocation or effects. Keep attempted, returned and confirmed prefixes
distinct. Traversal and cache phases share the original absolute deadline; they
cannot reset it or substitute hidden smaller limits. Exhaustion means incomplete
or refused, never a partial complete inventory. Accounting does not claim physical
memory confinement or observation of every internal tool read.

Before/after whole-image bytes and original description metadata detect observed
change; they cannot exclude a hostile write-and-restore or prove the tool consumed
a particular copy. Original image custody and source/tool premises stay explicit.
Hashes, sidecars and consistent plans supply no source approval, imported-tool
admission, compiler-input consumption or detached-child proof. Add independent
contamination controls for direct/transitive products, aliases, every cache tier,
staging, archive and final partitions, plus all-type, byte-name, quota, framing,
partial-effect and retirement controls. Four full image builds and guest use keep
their separate acceptance criteria.

Persist profile identity, provenance, base flavour, source chain, import closure
and reviewed release selection in appliance and final artifact metadata. Normal
output labels extended images non-clean-room. Stage outputs privately and
accept final manifests/checksums only after complete preflight, produced-body
and installed-content checks; retain original failures and unpromoted artifacts.
No network, device, raw-block, key or global-discovery grant follows from a
profile selection.

The configuration creator retains original input, directory and staged-output
descriptions through the actual producer lifetime. Reserve acquisition/result
records before native effects; require wanted CLOEXEC witnesses and actual
same-open-description comparison under the original complete native signal
scope. Reads, writes, permissions and once-only retirement retain declared
intent, actual progress and first uncertainty. Unsupported comparisons refuse
without metadata or inode fallback. Reuse existing signal/reaper primitives;
do not impersonate a child owner as a generic file owner or refresh identity
from an observed replacement.

For shell entry points, the creator owns the genuine literal shell invocation
through its original native child/wait custody. Keep original input and staged
output descriptions through that lifetime, with witnesses confined to their
native owner. The shell and unrelated Cargo, compiler, Git and VM tools receive
no profile descriptors. Existing compiler, VM, artifact and cleanup gates remain.

Use a bounded data-only packet containing the complete source bodies, candidate
manifest, profile record and effective configuration. Precharge its full encoded
extent and native write copies before publication; retain partial write and
once-only output-retirement state. A fresh private packet file is an ordinary
selected data source. Only fixed profile/parser/generator/startup/media calls
receive its body on their explicitly selected standard input. Capture their
own complete regular input through CLOEXEC native custody, copy immutable data,
re-resolve every source and compare the full effective bytes and canonical packet
identity. Small descriptive requests can name the selection and extent; no
PID or numeric descriptor route substitutes for original custody. Preserve
valid large packets within explicit allowances rather than imposing argv or
environment string limits as configuration limits.

Packet paths, modes, hashes and records grant no creator identity, source
approval, payload admission, native object rights or cleanup authority. Data
consistency is separate from the original invocation, interpreter, helper-source
and filesystem premises. Unknown acquisition, close, source association or
namespace ownership stays retained and refuses reuse. Retire original
descriptions after genuine child cleanup; do not delete entries by matching a
pathname or serialized claim. Group closure does not establish a generic
detached cohort. Consumer data copies and before/after observations do not
exclude hostile filesystem writers or prove compiler input consumption.

Holding original input descriptions detects substitution but does not prevent
external writes. Retain observed-change limitations and independently freeze
consumer configuration bytes; no before/after hash or snapshot label supplies
hostile-writer exclusion or immutable compiler-input consumption. Pure
resolution accepts exact builtin/record types, excluding subclass callbacks,
and charges aggregate input/work/output before parsing, hashing or allocation.
Add original positive, substitution, unknown-effect, cancellation and cleanup
controls alongside the complete producer/consumer wiring.

Controls cover legacy clean semantics, all four identities, override and
inheritance contamination, deep bounded chains, cycles and changed inputs,
unknown roots, development-only release dependencies, alias/body substitution,
forged cache labels, mixed closure and unlisted installed content. Wire the
resolver and identity through every maintained producer and consumer; empty
extended files alone are insufficient. Genuine admitted payloads, four complete
image builds, guest use and the external Rust/LLVM guest rebuild retain their
separate acceptance criteria.

Authority, security and reliability

Extended-image selection grants no device, raw-block, key, global-discovery or network access. Place admitted executable/library objects on ext4 with exact manifests and realm policy. Imported libraries cannot become dependencies of trusted clean-room Rust components.

Apply the priority order: security, reliability, then performance. Keep suspected vulnerabilities in the repository’s restricted SECURITY.md reporting channel.

Acceptance criteria

  • Implement a versioned third-party payload manifest containing name, version, source
    digest, license/notices, target, recipe/patch digests, features, runtime dependency closure,
    dynamic dependencies and realm authority policy.
  • Define offline source ingestion and reproducible recipe storage; keep imported
    sources/patches separate from EriX-authored ISC implementation and never add imported
    libraries to trusted EriX Cargo dependencies.
  • Add explicit runtime.extended-dev.toml and runtime.extended-release.toml,
    labeled non-clean-room in metadata/output. Preserve existing clean runtime.dev.toml and
    runtime.release.toml semantics.
  • Enforce clean-profile exclusion across configuration inheritance, local overrides,
    aliases, caches, transitive libraries and packaged contents; test intentional imported-payload
    contamination fails closed.
  • Enforce a reviewed extended-release subset; exclude development-only
    generators/test harnesses/debuggers and unneeded dependency libraries.
  • Verify every admitted target ELF and declared DT_NEEDED closure,
    source/license/recipe record and authority envelope; reject unknown payloads, mismatched
    targets, dependency-only orphans and mutable unpinned sources.
  • Reconcile the phase inventory with newly discovered packaging and documentation
    dependencies before admission; update normative inventory, manifest schema/records and tests
    rather than silently expanding imports.
  • Package admitted tools on ext4 with bounded executable/library manifests; the build
    realm gets no raw block/device/key/global discovery or network capability from extended-image
    selection.
  • Test all four profile builds, labels, artifact inventories and clean-room exclusion
    independently; extended-tool success never certifies clean-room implementation provenance.

For each implementation slice, retain actual formatting, strict Clippy, unit/doctest and warning-denied build results for all altered Rust repositories and valid configurations. Add relevant runtime VM coverage, monitor older unit/VM regressions in exact-head CI, and update canonical component documents and affected technical-manual/API material. Every authored code file must remain below 1,000 physical lines, with meaningful inline documentation and missing_docs enforcement in Rust crates.

Alternatives and tradeoffs

Unlabeled mixed images obscure both licensing and security boundaries. Preserve clean profile semantics and use a separate manifest-controlled extended closure rather than broad configuration inheritance.

Tracking and rollout

Dependencies: integration#1

Dependencies identify required contracts and closure gates; preparatory inventory/design can proceed in parallel under one owner per edited file. Link bounded implementation issues and their PRs here before claiming acceptance. Use feature/posix-compat, regular signed commits in the canonical contribution format, and WIP PRs linked to the exact coherent component graph. All cross-repository Cargo/catalog selections and CI helpers use full 40-character lowercase commit hashes, including transitive dependencies; do not substitute branch, tag or implicit HEAD selection.

Close criteria only with their own reviewed deliverables and validation evidence. Pending, skipped, cancelled, failed or predecessor-only results remain distinct. Keep main images unchanged until explicit promotion direction; technical completion does not authorize merges, release tags or publication.

## Problem and motivation Self-hosting needs imported development tools while trusted EriX implementation and clean images retain clean-room provenance. Packaging must distinguish the two and reject undeclared transitive runtime payloads. ## Proposed behavior and scope Implement versioned payload manifests, offline source/recipe records, explicit extended-dev and extended-release profiles, a reviewed release subset, and independent closure/contamination tests across all four image profiles. Keep every imported dependency traceable to a required tool. This issue records planned work; its unchecked criteria are not implementation proof. The normative basis is [Phase 6 and AC1–AC24](https://git.erikinkinen.fi/erix/docs/src/branch/main/phases/6.md). ### Payload manifest format The first format describes candidates without admitting them. Each record has a unique ID, name and version, tool/library kind, explicit build-machine, EriX-host and output targets, source archive digest, license expression and license/notice file digests, recipe and ordered patch digests, selected features, declared runtime dependencies, native dynamic-library names and their owning payloads, and a realm-policy reference with its exact digest. Paths name canonical relative files in the supplied offline record; the parser never opens them, resolves installed tools or downloads sources. Hashes and records describe bytes, not approval, source consumption or capabilities. The realm-policy reference likewise creates no grant or default build realm. Use a strict versioned TOML format with immutable parsed records. Reject unknown fields, duplicate IDs or list members, missing digests, noncanonical paths, unknown dependencies, cycles, target mismatches and dynamic-library owners outside the declared runtime closure. Every native dynamic-library owner must also be an explicit direct runtime dependency: a transitive path cannot replace that native edge. Compute the complete closure iteratively so its size is bounded by the caller's admitted input bytes, without a fixed dependency depth or package-count limit. The maintained manifest starts empty. Examples and tests contain only original metadata fixtures; no upstream tool or runtime is approved by adding the schema. Source ingestion, actual ELF checks, clean-profile exclusion, extended-image selection and guest execution keep their own acceptance criteria. ### Offline source ingestion and recipe storage The byte-only pipeline takes complete immutable manifest, provenance and artifact bytes and explicit root IDs. Intake and decode require caller-admitted aggregate input allowances; export independently requires its output allowance before encoding allocation. Independently select the reviewed provenance catalog and its full digest. Its source rows bind payload name/version, upstream release or revision, archive digest and original review evidence; verify the supplied archive against both that catalog and the manifest. These records preserve the caller's review premise and do not approve sources or attest signature verification. Supply every selected archive, license, notice, ordered patch, recipe, policy and provenance-evidence file by canonical relative label. Require exact closure and complete digest/identity coverage; refuse missing, extra, repeated, conflicting or changed inputs. Labels never trigger filesystem lookup. Keep imported bytes separate from EriX-authored source and trusted Cargo dependencies. No fetching, extraction, executable resolution, recipe execution or profile selection occurs. Use strict version-one `erix.payload-provenance` and `erix.payload-recipe` TOML records. Recipes bind payload/source/patch/features, build/host/output targets, the complete explicit environment, exact tool version/target/digests, ordered literal argument vectors and working-directory labels, dependency recipe/input identities and expected output roles/kinds/paths. Check dependency owners, output roles and the complete acyclic recipe graph, including explicitly selected build-only dependencies. Environment/argv remain literal data without inherited keys or shell expansion. Expected outputs contain no invented build status. Return a frozen content-addressed store with complete original bytes. Its portable `ERIXPST1` schema-one framing carries a counted canonical ASCII JSON index and digest-sorted complete blob extents; labels and roles correlate actual bytes. Count complete intake, including supplied labels and selection metadata, before hashing/parsing. Export revalidation requires its own explicit aggregate input allowance; count exact framing/index/blob output before encoding allocation. Deduplication requires equal bytes and never refunds intake work. Introduce no incidental payload, tool, archive or dependency-depth ceiling. Decode the entire canonical framing, exact extent/digest/role inventory and recipe relationships before returning a store. Refuse unknown versions, duplicate keys/blobs, noncanonical ordering, truncation, trailing data, tampering and missing/orphaned blobs. Reimport requires the independently selected provenance digest again; bundle consistency cannot supply approval authority. Equivalent complete inputs produce identical stored bytes while preserving semantic patch/command order. Add independent round-trip, malformed, identity, quota, scale and no-effect controls. Filesystem persistence, owned build execution, actual input consumption, ELF admission, four image profiles and guest use remain separate requirements. ### Image profiles and packaging isolation Use four explicit selections: `dev`, `release`, `extended-dev` and `extended-release`. Existing development/release images remain clean-room. Extended configurations explicitly inherit their corresponding maintained clean configuration and retain non-clean-room provenance even with no imported roots. Derive a separate dev/release runtime flavour for existing service and console features; preserve Cargo's independent debug/release selection and native capacity, filesystem and launch policy. A byte-only resolver takes immutable labelled configuration bytes with a caller-supplied aggregate allowance. Its filesystem adapter receives explicit roots/selections, captures only original selected regular files and rejects missing/ambiguous parents, links, escapes, changed files, cycles and conflicting profile declarations before build or cache effects. Count complete labels/bytes before parsing. Resolve iteratively within supplied storage without a fixed inheritance-depth or file-count limit. Merge declared scalar/table values and replace arrays as a whole, then apply the existing complete runtime validation. Clean selections cannot inherit extended declarations; overrides, filenames, aliases and environment labels cannot erase provenance. After preflight, stage one canonical complete effective configuration and its source-chain/profile identity. Every producer and consumer, including generated boot configuration, uses the same bound bytes. Preserve the original selection separately and revalidate the snapshot before use. Clear inherited exports and emit only fixed quoted values derived from the resolved record. Share the resolver across fixture, scenario, appliance and disk entry points. Profile metadata creates no capability and changes no native boot table. Select tool roots against the complete candidate manifest; require exact runtime closure, build-input classification and target agreement. Extended release also requires an independently selected reviewed workflow record with exact root identities and rationale. Exclude development-only generators, test harnesses, debuggers and network-fetch tools throughout its transitive closure; include a dependency library only when a selected tool requires it. A name or feature flag does not establish approval. The maintained candidate manifest is empty: that does not supply a reviewed release workflow or complete release-subset evidence. Requests for imported artifacts refuse before build/package effects until the separate admission producer supplies genuine source, recipe, ELF, functional and realm evidence. Do not add an approval boolean or a synthetic success record. Carry original source/build identity, provenance, profile, closure and release selection through executable/object/alias inventories. Renaming, hard links, symlinks and lookup aliases preserve the underlying classification; reject shadowing and mismatched target/body identities. Preserve native aliases, fixtures, launch policy and assets. Imported libraries cannot enter trusted EriX Cargo dependencies or replace its native shared-object registry. Common native compiler caches may be reused only for identical source/compiler/flags and roles. Bind packaging caches to the complete profile/import/workflow identity and revalidate bodies and closure on every hit; directory names and stored labels supply no provenance. Create an immutable expected product and installation plan from the explicit native producer declarations before staging enumeration or filesystem writes. Declare every executable, transitive object, manifest, native asset, alias, diagnostic fixture, script, timestamp seed and profile record. Retain the complete profile/effective-configuration/source-chain/import tuple, producer role, intended destination, full body and alias group. Enumerating an existing staging entry cannot make it a wanted product. Unknown or imported products refuse clean-image consumption; an empty import list cannot turn an extended image clean. Bind that tuple and the complete transitive product classification through executable, shared-object and registry caches. Independently inspect each cache's whole namespace, entry types and bodies before restore or publication. A legacy record lacking classification is a miss, not native or imported approval; a failed read remains an error. Cache misses may invoke only the existing explicit native producer. Include the new host modules in the complete builder input closure without changing guest ELF or boot metadata formats. The install plan retains raw pathname bytes, full Linux mode, applicable UID/GID, logical bodies, exact symlink targets, special-node encodings and hard-link groups. Preserve the existing private/coreutils/extop aliases, realm fixtures, native assets and optional script/time additions. Plan formatter-generated root and lost+found entries separately. Declare permitted inode sharing and exact link counts; independent products must not acquire an accidental shared inode. Serialized byte names use a canonical injective encoding with its expansion charged before allocation. Add no text-encoding, name-count or traversal-depth ceiling beyond the actual format constraints and caller allowances. Walk the complete actual host staging and installed namespace independently of the expected list. Reconcile regular files, directories, symlinks, FIFOs, character devices, block devices and sockets, including complete byte names, directory child sets, dot/dot-dot topology, full modes and logical bodies. Never follow symlinks or create host special nodes while checking. Preserve fast, slow and inline link targets and both supported device encodings. Device numbers are data, not host routes. Refuse extra, missing, duplicate, truncated or changed entries, unexpected inode sharing, directory cycles, unknown attributes/features and uninspectable content. Format-reserved allocations remain distinct from the user namespace; require a recognized clean read-only filesystem check and reject orphaned or malformed allocations. This inventory does not certify free or slack blocks. The ext4 reader receives the wanted original read-only image description and explicit tool roles. Retain original CLOEXEC witnesses and native signal custody while granting only the image read role to the literal filesystem tool. Compose the existing file-description and native child/reaper owners in a thematic adapter; the current command-owner API has no descriptor-transfer or stream intake operation and must not be presented as a generic file owner. Preregister child, pipe, output and partial-acquisition records before effects. Unrelated Bash, Cargo, compiler, Git and VM recipients receive no inventory descriptors. Retire each original independently once; unknown acquisitions or closes remain retained and refuse reuse. Numeric inode selectors and serialized paths cannot select custody, cleanup or a replacement image. Parse the selected tools' complete byte framing, not human-rendered filenames or lines. Preserve embedded newlines, spaces, quotes, backslashes and non-UTF8 names. Check exact inode ranges, recognized metadata fields, complete body extents and EOF. An exit of zero cannot override refused operations, checksum retries, unparsed diagnostics, partial output or unsupported geometry/features. Keep stdout a non-TTY read role and disable pager creation. No mounting, tree extraction or guest execution belongs to this adapter. Reconcile the filesystem after every installer and optional later addition. Construct and verify the complete appliance tree before archiving, then inspect the actual tar stream without extraction, including raw names, symlinks, hard-links, special records and complete regular bodies. Bound compressed, expanded, PAX and sparse material; unrecognized forms refuse. Keep result receipts outside the checked namespace. Check the entire ESP namespace and boot/native seed bodies, then independently compare the assembled GPT data extent with the verified ext4 bytes. Bind the complete final image before checksums, compression and identity publication. Derived runtime disks carry explicit profile data and verify their copied data extent; they cannot discover a different packet or fallback backend. Every caller supplies finite total/quiet clocks and aggregate source, image-read, logical-body, transport, record/path and encoded-output allowances. Charge input, retained copies, requested reads, names, encoding expansion, writes and readback before allocation or effects. Keep attempted, returned and confirmed prefixes distinct. Traversal and cache phases share the original absolute deadline; they cannot reset it or substitute hidden smaller limits. Exhaustion means incomplete or refused, never a partial complete inventory. Accounting does not claim physical memory confinement or observation of every internal tool read. Before/after whole-image bytes and original description metadata detect observed change; they cannot exclude a hostile write-and-restore or prove the tool consumed a particular copy. Original image custody and source/tool premises stay explicit. Hashes, sidecars and consistent plans supply no source approval, imported-tool admission, compiler-input consumption or detached-child proof. Add independent contamination controls for direct/transitive products, aliases, every cache tier, staging, archive and final partitions, plus all-type, byte-name, quota, framing, partial-effect and retirement controls. Four full image builds and guest use keep their separate acceptance criteria. Persist profile identity, provenance, base flavour, source chain, import closure and reviewed release selection in appliance and final artifact metadata. Normal output labels extended images non-clean-room. Stage outputs privately and accept final manifests/checksums only after complete preflight, produced-body and installed-content checks; retain original failures and unpromoted artifacts. No network, device, raw-block, key or global-discovery grant follows from a profile selection. The configuration creator retains original input, directory and staged-output descriptions through the actual producer lifetime. Reserve acquisition/result records before native effects; require wanted CLOEXEC witnesses and actual same-open-description comparison under the original complete native signal scope. Reads, writes, permissions and once-only retirement retain declared intent, actual progress and first uncertainty. Unsupported comparisons refuse without metadata or inode fallback. Reuse existing signal/reaper primitives; do not impersonate a child owner as a generic file owner or refresh identity from an observed replacement. For shell entry points, the creator owns the genuine literal shell invocation through its original native child/wait custody. Keep original input and staged output descriptions through that lifetime, with witnesses confined to their native owner. The shell and unrelated Cargo, compiler, Git and VM tools receive no profile descriptors. Existing compiler, VM, artifact and cleanup gates remain. Use a bounded data-only packet containing the complete source bodies, candidate manifest, profile record and effective configuration. Precharge its full encoded extent and native write copies before publication; retain partial write and once-only output-retirement state. A fresh private packet file is an ordinary selected data source. Only fixed profile/parser/generator/startup/media calls receive its body on their explicitly selected standard input. Capture their own complete regular input through CLOEXEC native custody, copy immutable data, re-resolve every source and compare the full effective bytes and canonical packet identity. Small descriptive requests can name the selection and extent; no PID or numeric descriptor route substitutes for original custody. Preserve valid large packets within explicit allowances rather than imposing argv or environment string limits as configuration limits. Packet paths, modes, hashes and records grant no creator identity, source approval, payload admission, native object rights or cleanup authority. Data consistency is separate from the original invocation, interpreter, helper-source and filesystem premises. Unknown acquisition, close, source association or namespace ownership stays retained and refuses reuse. Retire original descriptions after genuine child cleanup; do not delete entries by matching a pathname or serialized claim. Group closure does not establish a generic detached cohort. Consumer data copies and before/after observations do not exclude hostile filesystem writers or prove compiler input consumption. Holding original input descriptions detects substitution but does not prevent external writes. Retain observed-change limitations and independently freeze consumer configuration bytes; no before/after hash or snapshot label supplies hostile-writer exclusion or immutable compiler-input consumption. Pure resolution accepts exact builtin/record types, excluding subclass callbacks, and charges aggregate input/work/output before parsing, hashing or allocation. Add original positive, substitution, unknown-effect, cancellation and cleanup controls alongside the complete producer/consumer wiring. Controls cover legacy clean semantics, all four identities, override and inheritance contamination, deep bounded chains, cycles and changed inputs, unknown roots, development-only release dependencies, alias/body substitution, forged cache labels, mixed closure and unlisted installed content. Wire the resolver and identity through every maintained producer and consumer; empty extended files alone are insufficient. Genuine admitted payloads, four complete image builds, guest use and the external Rust/LLVM guest rebuild retain their separate acceptance criteria. ## Authority, security and reliability Extended-image selection grants no device, raw-block, key, global-discovery or network access. Place admitted executable/library objects on ext4 with exact manifests and realm policy. Imported libraries cannot become dependencies of trusted clean-room Rust components. Apply the priority order: security, reliability, then performance. Keep suspected vulnerabilities in the repository’s restricted SECURITY.md reporting channel. ## Acceptance criteria - [x] Implement a versioned third-party payload manifest containing name, version, source digest, license/notices, target, recipe/patch digests, features, runtime dependency closure, dynamic dependencies and realm authority policy. - [x] Define offline source ingestion and reproducible recipe storage; keep imported sources/patches separate from EriX-authored ISC implementation and never add imported libraries to trusted EriX Cargo dependencies. - [x] Add explicit `runtime.extended-dev.toml` and `runtime.extended-release.toml`, labeled non-clean-room in metadata/output. Preserve existing clean `runtime.dev.toml` and `runtime.release.toml` semantics. - [ ] Enforce clean-profile exclusion across configuration inheritance, local overrides, aliases, caches, transitive libraries and packaged contents; test intentional imported-payload contamination fails closed. - [ ] Enforce a reviewed extended-release subset; exclude development-only generators/test harnesses/debuggers and unneeded dependency libraries. - [ ] Verify every admitted target ELF and declared DT_NEEDED closure, source/license/recipe record and authority envelope; reject unknown payloads, mismatched targets, dependency-only orphans and mutable unpinned sources. - [ ] Reconcile the phase inventory with newly discovered packaging and documentation dependencies before admission; update normative inventory, manifest schema/records and tests rather than silently expanding imports. - [ ] Package admitted tools on ext4 with bounded executable/library manifests; the build realm gets no raw block/device/key/global discovery or network capability from extended-image selection. - [ ] Test all four profile builds, labels, artifact inventories and clean-room exclusion independently; extended-tool success never certifies clean-room implementation provenance. For each implementation slice, retain actual formatting, strict Clippy, unit/doctest and warning-denied build results for all altered Rust repositories and valid configurations. Add relevant runtime VM coverage, monitor older unit/VM regressions in exact-head CI, and update canonical component documents and affected technical-manual/API material. Every authored code file must remain below 1,000 physical lines, with meaningful inline documentation and missing_docs enforcement in Rust crates. ## Alternatives and tradeoffs Unlabeled mixed images obscure both licensing and security boundaries. Preserve clean profile semantics and use a separate manifest-controlled extended closure rather than broad configuration inheritance. ## Tracking and rollout Dependencies: [integration#1](https://git.erikinkinen.fi/erix/integration/issues/1) Dependencies identify required contracts and closure gates; preparatory inventory/design can proceed in parallel under one owner per edited file. Link bounded implementation issues and their PRs here before claiming acceptance. Use `feature/posix-compat`, regular signed commits in the canonical contribution format, and WIP PRs linked to the exact coherent component graph. All cross-repository Cargo/catalog selections and CI helpers use full 40-character lowercase commit hashes, including transitive dependencies; do not substitute branch, tag or implicit HEAD selection. Close criteria only with their own reviewed deliverables and validation evidence. Pending, skipped, cancelled, failed or predecessor-only results remain distinct. Keep main images unchanged until explicit promotion direction; technical completion does not authorize merges, release tags or publication.
erikinkinen changed title from [FEATURE] [P13] Admit declared tool payloads through four isolated image profiles to [FEATURE] Admit declared tool payloads through four isolated image profiles 2026-09-12 08:02:02 +02:00
Author
Owner

Version 1 of the payload manifest is implemented, with immutable records and deterministic dependency closure. It records source, license, notice, recipe and patch digests, separate build/host/output targets, features, runtime and dynamic dependencies, and the realm-policy reference. The maintained manifest is empty; parsing creates no authority or payload admission.

The format specification and development manual now describe that boundary. Offline source ingestion and the four image profiles remain open.

Version 1 of the payload manifest is implemented, with immutable records and deterministic dependency closure. It records source, license, notice, recipe and patch digests, separate build/host/output targets, features, runtime and dynamic dependencies, and the realm-policy reference. The maintained manifest is empty; parsing creates no authority or payload admission. The [format specification](https://git.erikinkinen.fi/erix/integration/src/branch/feature/posix-compat/docs/payload-manifest.md) and development manual now describe that boundary. Offline source ingestion and the four image profiles remain open.
Author
Owner

Offline ingestion and recipe storage are implemented in Integration and described in the manual. Intake checks the independently selected provenance, complete supplied bytes and recipe closure; the immutable store has canonical framing and separate input/output allowances. Relative labels open no paths and grant no execution authority. Image isolation, ELF admission and guest use retain their separate criteria.

Offline ingestion and recipe storage are implemented in [Integration](https://git.erikinkinen.fi/erix/integration/commit/f14be3cd082c410e4c43125bc8c9f975feb76ef9) and described in [the manual](https://git.erikinkinen.fi/erix/docs/commit/8ee44cc676465ae2a60192f7cdfc856e48a4944a). Intake checks the independently selected provenance, complete supplied bytes and recipe closure; the immutable store has canonical framing and separate input/output allowances. Relative labels open no paths and grant no execution authority. Image isolation, ELF admission and guest use retain their separate criteria.
Author
Owner

The build manual now covers the four runtime profiles, inherited configuration and the complete configuration packet retained with an appliance. Extended profiles keep their non-clean-room label even when empty. Imported-tool admission and in-EriX builds remain separate requirements.

Documentation change · Image packaging design.

The build manual now covers the four runtime profiles, inherited configuration and the complete configuration packet retained with an appliance. Extended profiles keep their non-clean-room label even when empty. Imported-tool admission and in-EriX builds remain separate requirements. [Documentation change](https://git.erikinkinen.fi/erix/docs/commit/3a2a84b1879108b0a99dcdaee62f57baf1dd8ad6) · [Image packaging design](https://git.erikinkinen.fi/erix/integration/issues/4).
Author
Owner

Four explicit image profiles are implemented in bae5480a. Extended profiles inherit the corresponding clean runtime configuration and retain their non-clean-room labels through appliance and disk packaging. Fixed consumers receive complete configuration packets, and packaging rechecks the retained source, configuration and profile records.

The explicit-profile criterion in the packaging issue is complete. Imported-tool admission, complete installed-content checks and all four full image builds remain open. The manual describes the configuration contract.

Four explicit image profiles are implemented in [bae5480a](https://git.erikinkinen.fi/erix/integration/commit/bae5480a21749440481c144ad7b7d50c064dbfce). Extended profiles inherit the corresponding clean runtime configuration and retain their non-clean-room labels through appliance and disk packaging. Fixed consumers receive complete configuration packets, and packaging rechecks the retained source, configuration and profile records. The explicit-profile criterion in [the packaging issue](https://git.erikinkinen.fi/erix/integration/issues/4) is complete. Imported-tool admission, complete installed-content checks and all four full image builds remain open. [The manual](https://git.erikinkinen.fi/erix/docs/commit/3a2a84b1879108b0a99dcdaee62f57baf1dd8ad6) describes the configuration contract.
Author
Owner

Deadline contexts now retain the first error and independent restoration errors through entry, phase changes and cleanup. A caught phase failure remains a failure, and attempted effects cannot be replayed. The source, fixtures and CI entry are updated in this commit; the deadline contract describes the records and ownership limits.

Complete native mask composition, image exclusion and creator/descendant lifetime remain open. The size gate and complete encrypted media handoff are progressing in parallel.

Deadline contexts now retain the first error and independent restoration errors through entry, phase changes and cleanup. A caught phase failure remains a failure, and attempted effects cannot be replayed. The source, fixtures and CI entry are updated in [this commit](https://git.erikinkinen.fi/erix/integration/commit/c9f2b52b149bd056856b2594e497595c8b49365e); the [deadline contract](https://git.erikinkinen.fi/erix/integration/src/commit/c9f2b52b149bd056856b2594e497595c8b49365e/docs/startup-deadlines.md) describes the records and ownership limits. Complete native mask composition, image exclusion and creator/descendant lifetime remain open. The size gate and complete encrypted media handoff are progressing in parallel.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:08 +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#4
No description provided.