From a4e79fef85601ecf1eb8bc2db8023003a650d845 Mon Sep 17 00:00:00 2001 From: Byron Wall Date: Thu, 12 Nov 2026 21:57:14 -0500 Subject: [PATCH] docs: retire dataflow-logic-visibility All five milestones merged on 2026-10-29 (#268, #272, #274, #278, #279). Move the durable facts into the lasting docs, add the closure record to docs/initiative-history.json, and remove the planning folder. Co-Authored-By: Claude Opus 5.5 --- docs/dataflow-coverage.md | 12 + docs/initiative-history.json | 16 + .../implementation-plan.md | 127 ----- .../initiative-map.json | 487 ------------------ .../dataflow-logic-visibility/intent-brief.md | 52 -- .../dataflow-logic-visibility/shape-brief.md | 75 --- site/src/docs/pages/design.md | 2 +- 7 files changed, 29 insertions(+), 742 deletions(-) delete mode 100644 docs/intent/dataflow-logic-visibility/implementation-plan.md delete mode 100644 docs/intent/dataflow-logic-visibility/initiative-map.json delete mode 100644 docs/intent/dataflow-logic-visibility/intent-brief.md delete mode 100644 docs/intent/dataflow-logic-visibility/shape-brief.md diff --git a/docs/dataflow-coverage.md b/docs/dataflow-coverage.md index 022de27c..901264d4 100644 --- a/docs/dataflow-coverage.md +++ b/docs/dataflow-coverage.md @@ -47,6 +47,18 @@ The work came from the data-flow experience audit (October 2026). The audit trac - State: a zustand store (a `store` row) holds what its function returns and what its `set` receives; a selector reads the field it names, and calling a member read through the hook (`setCount` after `useStore((s) => s.setCount)`) runs the store's function, never the selector it is written beside. a setter's value reaches its getter's reads (#182); a function handed to a setter (`setCount((c) => c + step)`, a store path's `setState("todos", (list) => […])`) stands for what it returns, and its parameter is the current state; a Solid store path (`setStore("left", "title", v)`) writes `left.title` alone, so a sibling field never sees it, an updater there (inline or named) receives that field, not the whole store, and a predicate in the path (`(item) => item.id === id`) is a test, never stored; a store or signal's initial value seeds it field by field, so `createStore({ left, right })` keeps `left` and `right` apart; a state-pair row marked `lazy` (React's `useState`) calls a function initial value, and Solid's `createSignal` holds it; a `useReducer` dispatch binds the reducer's action, and the reducer's return is the state; state-pair factory and getter calls are framework-modelled (#188), modelled in the collector (#196). - Ends: a binding every read of which decides a branch (`if (forgotten)` in nested branches, `ready && `, ``, through `!` or an accessor's call) ends at its binding, decides a branch. A parameter or local binding the program never reads (`_level`, `const { isSuccess } = useQuery()`) ends there, named "never read": the checker proves the value goes nowhere, so the trace is `ok`, not a dead end; the value-flow ledger draws every in-place end (a branch test, a write, never read) as a terminal row, as the graph does. A service write or read is a method on a client's contract, or a function-valued field a declaration file declares (a generated client's); a callback prop the project declares (`props.save(x)`) is never one. A thrown value ends at the throw (#207). An exported value that nothing in the program reads ends at its export, the module's API, not at a dead end; a call through a callback an export nothing in the program calls was handed (`onSeen(id)`, `props.onPick(x)` in a component nothing renders) ends there too, at the module's API, never a library method on a parameter (`items.forEach`); one the program reads, by name or through `import * as`, walks on to that read. A function handed to a timer (`setTimeout`, `requestAnimationFrame`) ends there: the callback runs later. A function handed to a page element as a handler (`