Rainbow — Development Status

Parent: Rainbow development

2026-10-16: workspace contains no application code, tests, assets, or build configuration. Git commands report that this workspace is not a Git repository. Contributor guidance was moved from AGENTS.md into rainbow/dev/contributing; AGENTS.md is a one-line pointer.

2026-10-16 — Design finalized; implementation has not started

Design is recorded in rainbow/architecture, rainbow/parameters and rainbow/execution, linked from rainbow. No simulation code, build configuration or tests were created. No benchmark or CPU topology assessment has been performed. Next implementation work: configuration validation and build setup, reference scattering verification, table construction, then reproducible single-frame rendering. Preserve the user's no-coding instruction until implementation is requested.

Dependency discovery: GCC 13.3, CMake 3.28.3, Ninja and pkg-config are available on this host. Installed package records confirm libgomp1, libomp-18-dev and libopenexr-dev; pkg-config reports OpenEXR 3.1.5 and Imath 3.1.9. libtomlplusplus-dev is absent in the package query and matching TOML headers were not found in /usr/include. toml++ is the confirmed missing selected dependency. No compiler/link smoke test run; no packages installed. Exact image-preview writer and any external Mie dependency remain to be selected at implementation time.

2026-10-16 — Implementation started; display-loss interruption

User authorized implementation, local Git, efficient CPU use and professional source readability. C++ source now includes TOML configuration, Mie scattering and spectral table construction, deterministic particle projection, tile rendering, PNG/EXR output, worker accumulators and merge; numerical tests were written. Completion, speed and image quality remain unverified. A display-loss/hard-power-off incident interrupted development around 11:59 BST; generated executables and several build files are empty. No rendered image exists yet. Local commit 90e5039 preserves source and telemetry; use ./git-local because the environment reserves .git as read-only.

User then requested more logging, possibly to gravlax/kelp, after observing changed fan sound. A standard-library Python sampler, bounded asynchronous SSH sender, fsync-and-ACK remote receiver, rotating logs and local user-service file were implemented. Six telemetry tests and four-second local sampling passed; a real pomelo sample was read back from gravlax after a durable acknowledgement. Receiver is installed on gravlax. Continuous local service is NOT confirmed active: sandbox user-service D-Bus access is blocked; activation commands were provided to John. Builds/renders remain stopped pending verified live logging. No stress test or hardware settings change was made.

Service activation and log paths

Incident diagnosis

2026-10-16 — Working images and verified telemetry

After John explicitly authorized SSH localhost to issue the service commands, rainbow-health.service was linked, enabled and started. Its inherited GnuPG agent had no identities, causing remote SSH rejection. Source now selects an existing unlocked user-owned SSH agent; no keys were copied/changed. Fresh remote fsync acknowledgements and live kernel following were verified. The service remains active. This supersedes earlier statements that only manual terminal activation was possible.

Renderer is built and Release tests pass; address/undefined sanitizer tests pass with leak detection unavailable under sandbox tracing. Telemetry's six tests pass. Images visually inspected: output/waterfall.png (8 million mono-radius samples) and output/spray.png (32 million truncated-lognormal samples), both 1440x900, with EXR/accumulator/resolved parameters/profiles. Spray render took 5.324 s including output on two threads; mono took 1.945 s. Source self-review and scope limits are at rainbow/dev/review.

Local Git commits: 90e5039 initial source/logger; fd26be7 unlocked-agent selection; f4e0751 validation, profiling and reproducible presets. Working tree was clean after commit. Original blackout cause remains unknown. No remote rendering workers, stress tests or hardware configuration changes were made.

version 4  ·  created 2026-10-16  ·  updated 2026-10-16