Skip to main content

Run the Kernel

The smallest verified end-to-end path currently uses the transient integration harness. There is no released standalone installer that assembles only npm packages. The harness uses integration-owned backend adapters and its default runtime copies under target/foundation; use it as developer validation, not as a production deployment recipe.

1. Obtain the integration repository​

git clone https://github.com/drumee/transient.git
cd transient

The repository contains pinned source evidence required by the image build. A shallow selection of only target/ is insufficient.

2. Validate prerequisites​

scripts/test-env/kernel/check.sh

3. Start and inspect​

scripts/test-env/kernel/up.sh
scripts/test-env/kernel/status.sh

Observable state:

  • GET http://127.0.0.1:28642/-/svc/kernel.status returns a successful Kernel status envelope;
  • the UI runtime and Hello plugin indices are served;
  • MariaDB contains the intrinsic runtime schema and bootstrapped identities;
  • Redis responds and the push router is configured.

Call the anonymous Hello service:

curl --fail --silent --show-error \
  --header 'content-type: application/json' \
  --data '{}' \
  http://127.0.0.1:28642/-/svc/hello.ping

The response contains status: "ok" and data.message: "Hello from Drumee".

4. Stop the disposable environment​

scripts/test-env/kernel/down.sh

For a one-command build, launch, assertion, binary data-plane check, and cleanup:

scripts/test-env/kernel/test.sh

This exact command was verified for this documentation. It checks service and plugin routes, Yellow Page domain ACL, Redis, streamed binary upload, and Nginx delivery, then removes the three disposable containers and network.

Complete Finder and data-plane validation​

The complete validation path additionally requires standalone Finder and System MFS checkouts. The default sibling layout is:

workspace/
├── transient/
├── finder/
└── system-mfs/

From transient, the verified command is:

scripts/test-env/kernel/phase4.8-validation.sh

The historical script name is retained, but the current suite includes the completed Finder stabilization and standalone-repository boundary. It runs Finder core and browser scenarios, backend dispatch, multi-client synchronization, transfer/data-plane checks, the disposable Kernel environment, and standalone System MFS tests. Alternative checkout locations are explicit:

KERNEL_FINDER_ROOT=/path/to/finder \
KERNEL_SYSTEM_MFS_ROOT=/path/to/system-mfs \
scripts/test-env/kernel/phase4.8-validation.sh

KERNEL_FINDER_ROOT must point to the standalone drumee/finder source checkout. The basic scripts/test-env/kernel/test.sh path remains the smaller Hello/Kernel integration proof and does not replace the complete Finder suite.

What this path proves—and does not​

The basic path proves the integrated runtime can start, bootstrap identity/session state, dispatch a capability, serve its frontend bundle, route push traffic, and keep large binary delivery outside bounded JSON control requests. The complete path separately validates the public standalone Finder source boundary and its integration. Neither path proves production hardening, a supported upgrade policy, or a supported production npm-only Minimal Kernel distribution or installer.