sam-4screen-desktop 2026-11-5:23:6:30

.obsidian/workspace.json

@@ -210,8 +210,9 @@
       "templater-obsidian:Templater": false
     }
   },
-  "active": "26813e16e829b798",
+  "active": "8018aa52f0591df9",
   "lastOpenFiles": [
+    "010 inbox/TUIOS Coding Harness.md",
     "010 inbox/AI tool to try and implement.md",
     "300 areas/350 AI Pi Coding Agent/AI tool to try and implement.md",
     "010 inbox/_sort log.md",
@@ -238,7 +239,6 @@
     "010 inbox/Family Holiday Camping Wilsons Prom.md",
     "400 Personal Family/470 Holidays Travel/Family Holiday Camping Wilsons Prom.md",
     "010 inbox/MiniMax Voice — Cloud STT and TTS with Local Fallback.md",
-    "200 projects/Tools Software WebUI/MiniMax Voice — Cloud STT and TTS with Local Fallback.md",
     "010 inbox/Family Holiday Camping Wilsons Prom.md~",
     "010 inbox/_WATCHER",
     "300 areas/355 AI Research and Techniques",

010 inbox/TUIOS Coding Harness.md

@@ -0,0 +1,35 @@
+---
+proposed_folder: 300 areas/350 AI Pi Coding Agent
+proposed_toc: "100 Table of Contents/Areas.md → AI & Coding Agent"
+proposed_tags:
+  - project
+  - go
+  - agents
+  - system
+  - coding
+  - tuios
+confidence: 0.59
+approved: false
+proposed_for: d95b860095a7
+---
+
+# TUIOS Coding Harness
+
+**What it is.** A terminal "office" that runs inside TUIOS: a board of tasks, three worker agents in their own panes, and a person who is only interrupted when a decision is needed.
+
+**Why it exists.** To stop being the person in the middle. Instead of reading agent output and telling each agent what to do next, the work is a list of cards. Workers take cards. A green test run merges. The person handles exceptions.
+
+**How it is put together.**
+- **TUIOS** (0.12.1) supplies panes, six named workspaces, task cards with an atomic claim, worktrees, checkpoints and shipping. Most of the system was already there.
+- **The board** is a Go program written with Bubble Tea and Lip Gloss — the same toolkit TUIOS uses. It reads the task cards and takes every key.
+- **The agents** are Pi, one per worker pane, each in its own git worktree.
+- **Gitea** holds the code.
+
+**The one design rule.** One thing owns each piece of state: the task queue belongs to the TUIOS daemon, code belongs to git, decisions belong to the person.
+
+**What went wrong on the way, and is worth knowing.**
+TUIOS can draw rich panels from markup (TML). They render beautifully in a browser and take no keyboard input there, which made every button built on them dead. A plain terminal program has none of that problem. That single discovery turned a month of dead ends into one program.
+
+**What it shows.** Agent orchestration, terminal UI work in Go, task governance, and the discipline of removing components: an early plan had a custom board, a lock, a messenger and a scheduler. TUIOS already had all four.
+
+**Status.** The board, the six screens and the repair path work on three machines. The gate, the review screen and the first real project are next.

010 inbox/_sort log.md

@@ -20184,3 +20184,8 @@ What the watcher did, newest last.
 
 ### 2026-11-05 20:43:21
 - **filed** `AI tool to try and implement.md` → `300 areas/350 AI Pi Coding Agent/AI tool to try and implement.md` (type area)
+
+### 2026-11-05 22:53:34
+- **proposed** `TUIOS Coding Harness.md` → `300 areas/350 AI Pi Coding Agent` (confidence 0.59)
+-   - JEV was torn: bucket 'project' but folder implies 'area' — review before applying
+-   - JEV suggests a NEW folder may be needed (not auto-created)