# Workflow system execution

Source: [`../workflow-discovery.md`](../workflow-discovery.md)

Apply the global and repository-local `AGENTS.md` files and the ponytail skill
at full intensity throughout. Preserve user work, prefer native capabilities,
and add no abstraction without a demonstrated repeated need.

## Current checkpoint

- Tranche: bootstrap and repository ownership reconciliation
- State: active
- Branch: `chore/workflow-system`
- Baseline: `nix flake check --no-build --quiet` passed on 2026-09-05; only
  the existing dirty-tree and unknown `modules` output warnings were emitted.
- Next: resolve the dashboard converter and private-state decisions, then
  finish machine-local cleanup and close the ownership tranche.

## Progress

| Batch | State | Evidence or blocker |
| --- | --- | --- |
| Bootstrap and repository ownership | Active | Repositories moved intact; dashboard and machine-local cleanup decisions remain |
| Declarative workstation foundation | Pending | Depends on canonical paths |
| Repository contracts and workbench | Pending | Depends on repository reconciliation |
| Desktop, agents, notes, PIM, transcription | Pending | Independent pilots follow foundation changes |
| Conditional retirement and completion | Pending | Requires per-pilot evidence |

## Repository checkpoints

| Repository | Branch | Commit | Purpose |
| --- | --- | --- | --- |
| NixOS configuration | `chore/workflow-system` | `d7dcc7b` | Discovery and execution baseline |

## Human actions

- Decide whether the one-time legacy dashboard BSON migration is still needed.
- Confirm whether the authoritative dashboard copy's `.env` and `.data` should
  supersede the divergent private state in the sync copy.
- Rotate the exposed Context7 key and provide `CONTEXT7_API_KEY` through a
  mode-0600 machine-local environment file on each workstation before removing
  the static user-config header.
- Relocate the mode-0644 `/home/kiri/work/SECRETS` file to an approved private
  owner and restrict it; its contents have not been inspected.
- Destructive cleanup, credentials, activation, and empirical pilot decisions
  will be surfaced here before use.

## Decisions and discoveries

- Use `/home/kiri/work/repos/yookr-dashboard-new` as the reconciliation base;
  its `feat/gogv2` head is 17 commits newer than the sync copy and matches its
  remote-tracking branch.
- Preserve the sync copy until authored changes and raw/generated data have
  been classified. Do not commit its database dump.
- Active repositories now live under `/home/kiri/dev/work`; inactive material
  is preserved intact under `.archive`, and the registered dashboard sensor
  worktree is under `.worktrees`.
- The sync dashboard's staged application changes are superseded. Its unique
  `convert_dashboards.py` is still referenced, but absent, in the authoritative
  flake. Its exports, `.env`, and MongoDB state remain untouched and private.
- The obsolete `feat/echarts-domain` worktree path is absent; its branch remains
  and its prunable metadata has not been removed.
- Shared Codex defaults and MCP endpoints are generated at
  `/etc/codex/config.toml`; Context7 reads its header from the environment. The
  unused generic `~/.config/mcp/mcp.json` owner is removed on next activation.
- Run independent pilots in parallel, but gate every retirement separately.