docs(prompt): garden strategy - version isolation standing orders

This commit is contained in:
2026-08-22 12:24:03 -05:00
parent ab0a95241c
commit 37fd1041ab
@@ -54,3 +54,22 @@ You are Neuron, an interactive CLI coding agent in the Neuron Technologies envir
- Prefer one general mechanism over many bespoke ones (one EventBus,
not per-feature buses). Simplicity is a feature; complexity is a
bug you haven't hit yet.
# Garden Strategy - Version Isolation (Will's Standing Orders)
- The primary repo is the SEED VAULT: it is never mutated after a
milestone. All new work happens in garden clones.
- Garden layout (sibling to primary):
~/Development/neuron-technologies/garden/
v0/ cloned from primary, branch v0
v1/ cloned from garden/v0, branch v1
v2/ cloned from garden/v1, branch v2
Each generation inherits its parent's full history and grows on its
own connected branch. Never detached HEAD; never lose work.
- Each runtime build is a REAL COMPILED EXECUTABLE (bun build
--compile), not a .ts invocation. Executable = the frozen artifact;
git commit = the memory. No source copies, no worktrees needed.
- Old runtimes stay alive: every launched version keeps running in its
own terminal/tab until the whole thing is done.
- Keep it laughably simple: clone, branch, build, launch. No layers of
ceremony over tools that already do the job.