We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
#123 SHIPPED + CLOSED — non-iterable loop in: now fails loudly (server v3.39.6) Home (Last refreshed + Recently closed #123 row + Ecosystem map server cell → v3.39.6 + Sessions-log preview + Releases preview), Sessions-Log, Releases (v3.39.6 row), and Umbrella-Decoupled-Context-Event-Chain (Recent activity row). server#258 (squash 275b914) → v3.39.6 7f109a9. #127 stays OPEN (separate perf follow-up).
docs(dashboard): #121 second-half — server v3.39.5 (server#257) Off-server system/* WAL-chain wedge fully fixed. #256 (v3.39.4) was only the first half; #121 reopened after a v3.39.4 prod re-cutover still wedged system/scheduled_cleanup on the system-pool worker. #257 gates both off-server-drive sites in trigger_orchestrator_inner on should_publish so system/* execs drive server-built run_state; regular execs keep the off-server path. Touched Home (header + ecosystem-map server cell + sessions/releases previews + recently-closed #121 row), Sessions-Log (new entry), Releases (header + timeline row), Umbrella-Decoupled-Context-Event-Chain (recent-activity row).
#121 off-server WAL-chain-incomplete loop on system/ execs FIXED — server v3.39.4 Home (Last-refreshed + Recently-closed #121 row + Ecosystem-map server cell v3.39.3->v3.39.4 + Sessions-log preview + Releases preview), Sessions-Log (new top entry), Releases (v3.39.4 timeline row + Last-refreshed), Umbrella-Decoupled-Context-Event-Chain (Recent-activity row). server#256 (squash 28b17cb -> v3.39.4 77aaa06): link the gate-off command.claimed through ChainHeads (no more orphaned NULL-prev_event_id spine head) + don't route system/ execs to the off-server WAL drive (their events never enter the WAL -> __offserver_retry__ loop). Server-only. Live prod off-server-cutover wedge is the real-world repro.
docs(wiki): record #125 + #126 — tools task_sequence control flow + http data-shape fixes (v3.14.0) + worker v5.40.3 adoption; 10×1000 batch pft clean; #127 perf follow-up filed
#124 SHIPPED + CLOSED — distributed task_sequence forward set:/sibling bindings no longer render empty (server v3.39.3) Home (Last refreshed + Recently closed + Ecosystem map server cell + Sessions-log preview + Releases preview), Sessions-Log, Releases (v3.39.3 row), and Umbrella-Decoupled-Context-Event-Chain (Recent activity row). server#255 (squash d53e095) -> v3.39.3 365d3be. #121 / #123 / #125 / #126 stay OPEN -- separate, not resolved by this.
#120 SHIPPED + CLOSED — reduce barrier no longer deadlocks on open/asymmetric loop joins (server v3.39.2) Home (Last refreshed + Recently closed + Ecosystem map server cell + Sessions-log preview + Releases preview), Sessions-Log, Releases (v3.39.2 row), and Umbrella-Decoupled-Context-Event-Chain (Recent activity row). server#254 (squash fbb855f) -> v3.39.2 28e8950.
#119 + #118 SHIPPED + gate-ON kind-validated + CLOSED — off-server restart-rehydration unblocks the terminal-finalize FinalizedGuard; single+multi-replica blemish-free
#117 SHIPPED — off-server spine ordered by prev_event_id chain + walked from real tip worker v5.40.1 (worker#122 baeae78) + e2e #72 cdf1768. High-concurrency fan-out reduce wedge fixed: the off-server from_events spine was sorted by event_id; the worker walked from max(event_id) but the real causal tip is event_ids.last() (ChainHeads watermark), so under a fan-out id-inversion the max-id walk missed the inverted tip and the reduce never fired. Now builds from expected_head + orders by the prev_event_id chain walk. 2-replica affinity gate-ON stress: 6/6 iterations, 108/108 execs COMPLETE, 15 real id-inversions all fired reduce_customer + completed. Single-replica 7/8 (1 fail = separate pre-existing terminal-finalize race, non-wedging). Updated: Sessions-Log (new entry), Releases (worker v5.40.1 row + last refreshed), Home (last refreshed + recently-closed #117), Umbrella-Decoupled- Context-Event-Chain (#117 sibling note).
docs(wiki): #116 program-scale step 2 — execution-affinity write ordering shipped + multi-replica validated Umbrella Recent-activity + Next-steps, Home (Last refreshed + ecosystem-map server cell v3.39.0 + #115 row + sessions/releases previews), Sessions-Log, Releases (server v3.39.0). #117 follow-up linked.
#115 program-scale step 1: multi-replica coherence data layer (server v3.38.0) + execution-affinity staged Home (Last refreshed + ecosystem map server v3.38.0 + sessions/releases previews), Sessions-Log (full entry), Releases (v3.38.0 row), Umbrella-Decoupled-Context-Event-Chain (program-scale activity row). NATS-KV-backed ChainHeads + ExecDescriptor (NOETL_REPLICA_COHERENCE=nats_kv, default local); single-replica parity proven, 2-replica resolves proven, full completion staged on execution-affinity.
wiki: #115 Phase 5 atomic-working-item context (tenet 6) shipped — server v3.37.0 + worker v5.40.0 Home (Last refreshed + Active-umbrella #115 + Ecosystem map server v3.37.0/worker v5.40.0 + Sessions/Releases preview), Sessions-Log (Phase 5 entry), Releases (server v3.37.0 + worker v5.40.0 rows), Umbrella-Decoupled-Context-Event-Chain (Phase 5 plan row SHIPPED + activity log + §6.3 #77-dependency resolved).
#115 Phase 6 SHIPPED — hot-path noetl.event read class retired (audit-only); server v3.36.0 + ops + e2e Home (Last refreshed + #115 umbrella status + server ecosystem cell v3.35→v3.36 + sessions/releases previews), Sessions-Log (new entry), Releases (v3.36.0 row), Umbrella-Decoupled-Context-Event-Chain (Recent activity Phase 6 row). Gate-ON literal-zero validated: hot-path scan Δ0 + drive state_build Δ0 ⇒ ZERO noetl.event scans on the hot path end-to-end; audit/replay still work. RFC never-scan end state (tenet 3) reached under the flag. Default event_scan, prod unchanged.
docs(wiki): #115 Phase 4 REMAINDER — stateless off-server drive edge (server v3.35.0 + worker v5.39.0 + e2e) Home (Last refreshed + #115 umbrella row + server/worker ecosystem version cells → v3.35.0 / v5.39.0), Sessions-Log (new 2026-06-20 entry), Releases (server v3.35.0 + worker v5.39.0 rows), Umbrella-Decoupled- Context-Event-Chain (Recent-activity row + Phase 4 marked COMPLETE in Next-concrete-steps). Zero server state rebuild + zero noetl.event reads on the drive path under offserver; completes #107 step 2 server-side.
#115 Phase 4 DRIVE CUTOVER shipped + gate-ON parity-validated — worker v5.38.0 + server v3.34.0 + ops + e2e Home (Last refreshed + #115 umbrella row + worker/server ecosystem version cells), Sessions-Log (new top entry), Releases (worker v5.38.0 + server v3.34.0 rows + preamble), Umbrella-Decoupled-Context-Event-Chain (status + Recent-activity row).
docs(wiki): #115 Phase 4 KERNEL+FLAG SHIPPED + shadow kind-validated (worker v5.37.0 + server v3.33.0) Off-server state builder: pool-side WAL chain index + chain-walk spine (parity by construction) + cache keyed by immutable chain head (CacheHit/Incremental/ ColdRebuild) + live WAL shadow loop, gate-ON kind-validated (993 WAL events / 0 noetl.event scans / 28 cold + 21 incremental / fresh fan-out COMPLETED, sole-writer + lag-0). Drive cutover staged. Home (Last refreshed + #115 row + server/worker version cells + Sessions/Releases previews), Sessions-Log, Releases, and Umbrella-Decoupled-Context-Event-Chain (Recent activity + Next steps) updated in lockstep with the ai-meta pointer bumps.
docs(wiki): #115 Phase 3 MERGED (server v3.32.0) + Phase 4 (off-server state builder) started Home (Last refreshed + #115 row + server v3.32.0 ecosystem cell + Sessions/Releases previews), Sessions-Log, Releases (timeline row + Last refreshed), and Umbrella-Decoupled-Context-Event-Chain (Recent activity + Next steps) updated in lockstep with the ai-meta repos/server pointer bump to 8338417.
#115 Phase 3 IMPLEMENTED + kind-validated (chain-walk state builder, server#245 open) Home (Last refreshed + #115 umbrella row), Sessions-Log (Part B entry filled in), and the umbrella page (status header + Recent-activity row + Next-steps Phase 3→implemented) drift together. Chain-walk state builder behind NOETL_STATE_BUILD_MODE: parity 41/41 match, no-scan proven (event_scans=0, 1064 PK hops), all topologies COMPLETE gate-ON. PR open for review; ai-meta repos/server pointer bump staged for after merge.
#115 Phase 2 MERGED → pointers bumped (server v3.31.0 + noetl ecd16a2) + Phase 3 started Part A close-out of the one-level event chain. Home (Last refreshed + ecosystem server v3.31.0 / noetl ecd16a2 cells + #115 umbrella row + Releases preview), Sessions-Log (new top entry), Releases (timeline + per-repo server v3.31.0 row + Last refreshed), and the umbrella page (status header + Recent-activity row + Next-steps Phase 2→merged / Phase 3→in-progress) all drift together. Phase 3 (chain-walk state builder, server-side, flagged NOETL_STATE_BUILD_MODE default event_scan) now in progress.
#115 Phase 2 implemented + kind-validated: one-level prev_event_id event chain (server#244 + noetl#667 open, awaiting merge)
#115 Phase 1 shipped: references-in-state consume side (closed #113 + #114) Home (Last refreshed + #115 active row Phase-1 status + #101 consume-side-done + removed closed #113/#114 from active + added to Recently closed + server v3.30.0 / worker v5.36.0 ecosystem cells), Sessions-Log (new entry prepended), Releases (timeline + per-repo server v3.30.0 + worker v5.36.0 rows + lead), Umbrella-Decoupled-Context-Event-Chain (Status + Phase 1 ✅ SHIPPED + Recent activity + Next steps). worker#117 (v5.36.0) + server#243 (v3.30.0); all 9 #113 stalls COMPLETE gate-ON.
RFC #115: Decoupled Context + Event Chain — file design + dashboard wiring New Umbrella-Decoupled-Context-Event-Chain.md (full RFC). Wires the dashboard per wiki-maintenance Rule 0a: Home Active-umbrellas row + Last-refreshed headline, Sessions-Log entry, _Sidebar link, and a reframe banner + Home-row note on Umbrella-Orchestrator-Scaling (#101). Refs noetl/ai-meta#115