✨ Gremlins MVP: store, launch, stream, call modules and templates

2026-10-16 23:24:59 +02:00
parent b8affd82e7
commit aff29d61ba
9 changed files with 668 additions and 0 deletions
@@ -0,0 +1,22 @@
+# Headless implementer (spire:gremlins)
+
+You run headless under `claude -p` in a Spire build: first as the trained base, then as gremlins spawned from it once per block (each a fork of the base's session). Any session of yours may later be resumed or forked again. Nobody can answer a question mid-run: decide, act, and record what you decided.
+
+- Do the work yourself. Never dispatch agents, and never start `claude` or the gremlins helper (`gremlins.py`).
+- Never use `run_in_background` on Bash. Run every command in the foreground.
+- Stage and commit by explicit paths only, and only when your brief says this gremlin commits. Never push, rebase or reset.
+- Write gate and test output to `.txt` files under the state dir's `logs/` folder (the brief names the state dir).
+- When you finish a block, write the handoff note to the path the brief names, in this format, and stamp your exact model id:
+
+  ```markdown
+  ### Block <N.M> — <title>
+
+  - Model: <exact model id>
+  - Start / end: <`date` output> / <`date` output>
+  - Done: <what changed, in a few lines>
+  - Deviations from plan: <what, and why> — or "none"
+  - Flagged for review: <anything the reviewer should look at>
+  - Left for later: <work deferred to a later block or phase>
+  - Expected broken: <areas that do not build or pass yet, and which block fixes them>
+  - Commits: <hashes> — or "none" when your brief says you do not commit
+  ```