From 8446965d8802446638b8a0392a0222b8ea403465 Mon Sep 17 00:00:00 2001 From: Jelle Spreeuwenberg Date: Sun, 6 Sep 2026 18:18:57 +0200 Subject: [PATCH] docs: close workflow phase one --- docs/plans/workflow-system.md | 25 +++++++++++++------------ docs/workflow-discovery.md | 19 ++++++++++--------- 2 files changed, 23 insertions(+), 21 deletions(-) diff --git a/docs/plans/workflow-system.md b/docs/plans/workflow-system.md index d9a7bec..6a94c05 100644 --- a/docs/plans/workflow-system.md +++ b/docs/plans/workflow-system.md @@ -2,8 +2,8 @@ Source: [`../workflow-discovery.md`](../workflow-discovery.md) -The declarative workflow core is complete; pilots remain. This file is the -living handoff for operational constraints and external gates; implementation +Phase one is complete; explicitly deferred pilots remain. This file is the +living handoff for operational constraints and future work; implementation history is available in Git. ## Activation boundary @@ -32,7 +32,7 @@ restarted Kitty and closed the user's terminal session. ## Current checkpoint -- State: declarative core complete and active; pilots remain. +- State: phase one complete and active; explicitly deferred pilots remain. - Branch: `chore/workflow-system`. - Validation: `nix flake check --no-build --quiet`, all three no-link system builds, generated Zenith and Polaris Niri validation, and all six companion @@ -67,15 +67,14 @@ restarted Kitty and closed the user's terminal session. redundant live trial; notifications are intentionally disabled after their live pilot. -## Active pilot gates +## Phase-one closure -These gates do not block work on each other. - -- Run one real cross-system investigation. Create a Marimo-to-HTML report only - when that investigation gives it durable value. -- Keep Bruno, DBeaver, and PIM clients until their separate pilots decide them. -- Route issue 197 to the actual account repositories before implementation; - leave the two local dashboard planning branches available as evidence. +- The cross-system investigation and Marimo report pilots move into phase two. +- Bruno and DBeaver remain available; retiring old applications is not part of + phase one. +- Issue 197 planning is complete. Before implementation, route it to the actual + account repositories; leave the two local dashboard planning branches + available as evidence. Herdr's bounded pilot is complete. If later use exposes a problem, fall back independently to native agent sessions or native `git worktree add/list/remove`; @@ -83,6 +82,8 @@ do not add a wrapper or Worktrunk without a demonstrated gap. ## Deferred pilots +Revisit these alongside related phase-two ideas rather than as isolated cleanup. + - During a docked Zenith session, capture the external display's stable identity and test the two-output `Super+A` exchange. The current recorded session exposed only `eDP-1`. @@ -184,4 +185,4 @@ the fresh-shell GitHub read and restarted-Codex Context7 lookup must both work. ## Next step -Run one real cross-system investigation without mutating company GitHub. +Begin phase-two discovery from the user's new workflow ideas. diff --git a/docs/workflow-discovery.md b/docs/workflow-discovery.md index 251a89b..6a58677 100644 --- a/docs/workflow-discovery.md +++ b/docs/workflow-discovery.md @@ -1,7 +1,8 @@ # Workflow system blueprint -Status: declarative core implemented; pilots remain. Current gates and the -operational handoff live in [`plans/workflow-system.md`](plans/workflow-system.md). +Status: phase one implemented and active; explicitly deferred pilots remain. +The operational handoff lives in +[`plans/workflow-system.md`](plans/workflow-system.md). This document is the durable design for the workstation and surrounding Yookr workflow. Implementation history belongs in Git. @@ -160,12 +161,11 @@ generalize the exception to other repositories. Only the user activates a NixOS or Home Manager generation. Agents may evaluate and build configurations, then provide an activation command. -## Remaining pilots +## Phase-one closure -- Run one real cross-system investigation. The workbench environment, all four - SOPS-derived Dadbod connections, read-only example-query runs, and Kulala - response chaining have passed. Add a Marimo report only when the investigation - gives it durable value. +- The workbench environment, all four SOPS-derived Dadbod connections, read-only + example-query runs, and Kulala response chaining passed. The cross-system + investigation and Marimo report pilots move into phase two. - Add another ephemeral read-only rclone remote only when credentials for a new Leafcloud project become available. Irristaud listing has passed; do not upload. - Use the reviewed local Yookr OpenAPI contract while the accepted malformed @@ -176,11 +176,12 @@ and build configurations, then provide an activation command. states, local branches, parallel non-overlapping plans, and the dirty-removal guard passed; the plans show that implementation belongs outside the dashboard repository. -- Keep Bruno, DBeaver, and existing PIM clients until their independent gates are - resolved. +- Keep Bruno and DBeaver; retiring old applications is outside phase one. ## Deferred pilots +Revisit these alongside related phase-two ideas rather than as isolated cleanup. + - Capture Zenith's external display identity during a docked session and test the two-output `Super+A` exchange, including name and focus restoration on failure. - Resume Evolution and Android PIM only when the user chooses to run those daily