dirigence/reliquary
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

📝 Close grotto-work session journal; headless-forks goal decisions

Browse Source
This commit is contained in:
g4borg
2026-10-16 22:21:21 +02:00
parent d3736898fc
commit bef84b3391
2 changed files with 137 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/workpad/goals/headless-forks.md
+23
View File
@@ -47,6 +47,29 @@ The Athanor learns plans, design and implementer reports, not code. For hard wor
- **Agent-tool forks**: replaced. Complex blocks go to forks of the trained implementer, and fresh Agent-tool agents stay for mechanical or distant blocks. The Agent-tool fork path is dropped from athanor.md.
- **Model**: always an explicit full model id. The fingerprint requires it anyway, which also sidesteps plan mode's silent Haiku→Sonnet upgrade. *(Igor's default, not asked; user may override.)*
### Decided 2026-10-16, naming (user)
- A headless worker launched by the helper is a **gremlin**. The skill becomes `spire:gremlins` and the helper `gremlins.py`; the env marker, state folder and ledger names follow.
- The command that creates one is **`spawn`**. Forking the base (`--resume <base> --fork-session`) is one *way* to spawn. Keeping `spawn` separate from `fork` leaves room for other spawn methods later.
- The trained session stays the **base**. "Mogwai" was considered and dropped (trademark-adjacent, a second invented word).
- When: a mechanical rename block at the start of Phase 3, before the skill and procedure text is written, so the release ships with the final names.
### Decided 2026-10-16, platforms (user)
- 0.3.0 ships **Windows-only**. On any other platform, `where` fails closed (`ok: false` with a clear reason), and the Athanor falls back to the 0.2.2 shape (fresh agents, no gremlins). SKILL.md says so.
- Linux testing is a follow-up (WSL Ubuntu and Docker are available on the dev host). macOS stays unsupported until someone can test it.
### Amended 2026-10-16, release gating (user)
- 0.3.0 is **not released from Windows alone**. The work stays on the `headless-forks` branch, which gets pushed but not merged. When the Windows phases are done, an Igor on a native Linux machine and one on a Mac check out the branch, test, fix their platform and lift the fail-closed gate for it. Only then is the branch merged and released. WSL is fine for development.
- The Windows build still ends with a handoff document for those Igors (what to test, known POSIX gaps M14 and the /proc tree walk, the smoke recipe).
- Strongly suggested by the user: pick this up as Rust work right away as well (see reports/2026-10-16-01-session-harness-app-forms.md). Not started yet.
### Decided 2026-10-16, platform seam (user)
- Phase 3 adds a refactor block. All platform-specific code (detached spawn, process table, tree kill, liveness, locks, path normalisation) moves behind one interface, with `WindowsPlatform` and `PosixPlatform` implementations. No scattered `IS_WINDOWS` branches stay outside it. The green Windows suite guards the refactor.
- Plus: a path-form test matrix (`C:\…`, `C:/…`, MINGW `/c/…`, `/tmp/…`, UNC, WSL `/mnt/c/…`) and a WSL check: does the helper run under WSL Ubuntu, and does PATH interop wrongly resolve `claude` to the Windows exe? Findings feed the Linux and Mac handoff. WSL stays fail-closed unless it passes.
## Later
- Dirigent harness / MCP tool takes over the helper's job ("stable for the constables").