From 853a81a89399794ef8ab70f723f06ce509a9d624 Mon Sep 17 00:00:00 2001 From: Emil Date: Wed, 2 Sep 2026 04:57:58 +0300 Subject: [PATCH] README: record that the kernel's open questions are closed Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01N1qPfzq8TDCUMFMV3UwV5N --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index b69ff21..215ab4f 100644 --- a/README.md +++ b/README.md @@ -47,6 +47,19 @@ encoder — no `SixLabors.ImageSharp` (its license isn't MIT/Apache) and no desktop screenshot tool, so this is checkable without a screen at all, exactly the introspection story `docs/kernel-contract.md#7` argues for. +**The kernel is closed.** All four questions the original design left open +— `Time`/`Log`'s home, whether the Event Bus is real infrastructure or +event-components, whether frame stages are fixed or plugin-extensible, and +the data-oriented-fast-path question — are resolved, each with working code +behind it, not just an answer written into the doc. `Time` and the Event +Bus (`Publish`/`Subscribe`, leak-safe the same way `Schedule` already is) +both shipped; `sandbox.echo` subscribes to `PluginLoaded` for real, so the +200-cycle leak test now proves `EventBus` doesn't leak too, not just +`Schedule`. See the resolutions in +[`docs/kernel-contract.md`](docs/kernel-contract.md) — one of the four +(the fast path) is deliberately still open, but with a concrete trigger +condition instead of a deadline, not left vague. + No physics yet — see the build order (M0–M4) in [`docs/kernel-contract.md`](docs/kernel-contract.md) for what's next.