This E28 draft exposes software-factory/confined-executor from the private packed distribution. Independent Astra review passed; it was merged on 1 October 2026 after an Opus 5.5 review and accepted locally the same day by the owner-designated acceptance reviewer after a Fable 5.1 review. It runs a caller's bounded Node program against caller-supplied snapshots and returns host observations. The supported boundary remains Node 26.8.1 on macOS arm64, tested on macOS 27.0. Other hosts are refused; the package's broader Node engine field does not expand this module's runtime support.
Install and typecheck
Obtain the reviewed private software-factory-0.1.0.tgz and pin that exact artefact in the application's lockfile. There is no registry publication or runtime dependency. The root package remains private. Earlier Journal and foundations contracts remain separate entry points.
npm install ./software-factory-0.1.0.tgz
npm install --save-dev @types/node@26.6.3
This subpath requires the caller's Node development declarations: the public result contains Buffer, and cancellation accepts AbortSignal. Its declaration entry explicitly references Node types. The external proof uses the already-installed @types/node 26.6.3 and its undici-types declaration dependency, with strict checking and no skipLibCheck; it also proves that absent Node types fail. These are development declarations, not runtime imports. The Journal and foundations keep their existing independent declaration tests.
Run a caller-owned snapshot
Create a canonical private directory owned by the controller (mode 0700). Importing the package and constructing an executor create nothing. Explicit runtime discovery reads the host; only run creates a namespace and launches a process.
import { Buffer } from 'node:buffer';
import {
ConfinedExecutor, confinedProfile, describeRuntime, snapshotDigest,
type SnapshotFile,
} from 'software-factory/confined-executor';
const files: readonly SnapshotFile[] = [
{ path: 'main.mjs', content: Buffer.from('console.log("snapshot checked")') },
];
const input: readonly SnapshotFile[] = [];
const runtime = describeRuntime();
const profile = confinedProfile();
const executor = new ConfinedExecutor({ root: '/caller/private/executor' });
const result = await executor.run({
runtime: runtime.digest,
profile: profile.digest,
program: { files, digest: snapshotDigest(files), entry: 'main.mjs', args: [] },
input: { files: input, digest: snapshotDigest(input) },
timeoutMs: 1000, maxOutputBytes: 4096, cpuSeconds: 2, maxDescriptors: 64,
});
Discovery above proposes pins for a new caller-approved run. Keep those pins with the caller's request. A mismatch refuses dispatch: do not rediscover and silently replace established pins. Include every program dependency in the supplied snapshot; .mjs files avoid relying on TypeScript execution inside installed packages. The private package executes compiled JavaScript, while the executor hashes the actual supplied program and input bytes, host runtime and instantiated profile. It requires no Factory journal, Candidate, worker, recipe or provider.
Interpret the result
not-started means no process was launched. observed records admission, actual exit, pipe closure, stop reason, bounded stdout/stderr, identities and namespace disposition. Read attributable and problems before using the observation. unresolved means resources are unknown and quarantined; it is neither failure nor permission to retry in place. Printed output is never a Verdict or trusted control record.
When timeoutMs elapses the host requests SIGKILL of the live unreaped child, as it does for cancellation and output overflow; this is not a hard completion deadline, and unconfirmed termination is reported as unresolved. Output retains a bounded prefix and reports total bytes seen. A quarantined or foreign root entry consumes capacity after a controller restart and is never reclaimed automatically. Keep the disposition for explicit caller recovery. Controller loss does not stop an orphaned program; this slice adds no restart recovery or durable execution ledger.
This is the existing stateless boundary: no hard memory or aggregate-disk bound, no hard CPU-time termination guarantee, and no expanded platform claim. Runtime filesystem replacement races remain outside the proof. The full executor contract owns limits, error order and all types.
Proof and compatibility
The tarball-only external application uses public imports and caller-owned temporary storage. It checks a useful multi-file snapshot, exact source/package runtime and profile identities, file-write/process/network denial with an unconfined positive control, preserved environment bounds, timeout/cancellation/output limits, pin refusal, namespace substitution and retained state across separate controllers. Existing local boundary evidence remains separately scoped.
The executor source bytes and sf-confined-runtime/1, sf-confined-node-stateless/1 and sf-confined-snapshot/1 protocols remain unchanged. No historical manifest or receipt is rewritten. This does not package the guarded fixture worker or repository collector: their TypeScript resource manifests need a separate protocol-aware design. The repository keeps the initial draft evidence. The current PR identifies its combined artefact and final checks; Broader adoption gates remain open.
