From 5b6a5e4f19347c98e8fc0f9046280bbabc82e8f9 Mon Sep 17 00:00:00 2001 From: giles Date: Thu, 2 Jul 2026 15:01:25 +0000 Subject: [PATCH] plan: fix P0.3b conformance count (596, not 599) Co-Authored-By: Claude Opus 4.8 --- plans/business-logic-fed-flows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plans/business-logic-fed-flows.md b/plans/business-logic-fed-flows.md index f14e5ddf..5758ec70 100644 --- a/plans/business-logic-fed-flows.md +++ b/plans/business-logic-fed-flows.md @@ -218,7 +218,7 @@ covers everything until a DAG's cost/latency/placement forces the substrate. persists string-keyed effect records to the blog store (dodging the keyword/persist top-level split); host/blog-load-flowlog! rebuilds it on boot (serve.sh). Proof: published on blog.rose-ash.com, RESTARTED the container, /flows still showed validate+notify (reloaded from the - store). blog 208/208, conformance 599/599. Whole-list rewrite per effect — cap/rotate later. + store). blog 208/208, conformance 596/596. Whole-list rewrite per effect — cap/rotate later. - 2026-07-02 — P0.3 DONE + LIVE-VERIFIED. The seam wired into the live publish path: on-publish registry + in-process transport + host driver + the execute-fold runner, fired by the draft→ published transition in both write handlers. Published a real post on blog.rose-ash.com → /flows