1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
#+TITLE: Home is consolidating all personal ~/projects AI projects into itself — heads-up + okay requested
#+DATE: 2026-06-11
* What's happening
Craig approved and started a migration that folds every AI-managed project under ~/projects (except work) into the home project as area subdirectories, with full git history preserved via git filter-repo + merge. End state: ~/projects holds home and work only; ~/code stays the place for standalone code projects. One todo.org, one priority scheme, one .ai session for all personal project management.
The spec rode along in this same inbox drop (from-home file with "project-consolidation-spec" in the name). It went through a full spec-review cycle (Codex, two passes: Not ready → Ready) and carries the per-fold manifest contract, a two-mode restore runbook, and a layered rollback story (snapper snapshot, untouched server bares, pre-fold tags, retired dirs, 30-day cooling-off).
* How far we've gone (as of 2026-06-11 ~17:00 CDT)
- Phase 0 done: git-filter-repo verified, snapper snapshot 5621, memory-dir tar in ~/backups/, pre-consolidation tag pushed.
- Phase 1 done: philosophy folded (pilot). Mode-B rollback drill passed in a disposable clone — the fold is provably removable using only its manifest.
- Phase 2 done: clipper folded (dress rehearsal). First todo.org import with :MIGRATED_FROM: markers and a fold-time triage; first live-link fix (a dirvish bookmark in ~/.emacs.d).
- Both sources retired to ~/projects/.retired/ (not deleted). Server bares untouched.
- Manifests at home:docs/consolidation-manifest-{philosophy,clipper}.org; live inventory gate at docs/consolidation-manifest-inventory.org.
* Learnings and adjustments so far
- A manifest can't embed its own redistribution commit's sha (amend changes it). The manifest row now reads "the commit introducing this manifest"; only the merge sha is recorded literally.
- git clone --no-local is the right clone shape for filter-repo's fresh-clone safety check; --force is banned from the runbook.
- The fold-merge branch is read from the source (fb-photo-scraper sits on master, not main — assume nothing).
- Staged freeze instead of full shutdown: the live inventory gate is regenerated per project immediately before its fold, so Craig can keep using not-yet-folded projects until their turn.
- Imported [#D] tasks fall outside the task-review staleness pool (it tracks A-C only) — by design, but worth knowing when verifying an import.
- Source todo.org "Reference" sections (non-task content) merge into the area's notes.org, not into home's todo.org.
* What we'd like rulesets to think about
- Edge cases we may not have seen: anything in the templates, workflows, or scripts that assumes one .ai per project under ~/projects (cross-agent-comms discovery, inbox-send target resolution, the ai launcher's project scan, broadcast).
- Future-project plans: whether new personal "projects" should now start as areas inside home rather than standalone ~/projects entries, and whether the templates should say so.
- Any rulesets docs or workflows that name the folding projects as handoff/broadcast targets (finances, jr-estate, etc.) — they'll need updating in our Phase 7 ecosystem pass; a list from your side would help us not miss any.
- The knowledge-base work-root denylist (~/projects/work) is unaffected.
* Ask: confirmed okay to continue
Reply to home's inbox with a confirmed okay (or concerns) for folding the remaining projects. The remaining list, in planned order:
1. jr-estate (Phase 3 — 704M history, 18-task triage, first memory merge)
2. danneel (Phase 4 — 613M history, 10-task triage)
3. finances (Phase 5 — 251M history, 43-task triage)
4. documents, elibrary, health, kit (Phase 6 folds, together)
5. website + little-elisper — relocate to ~/code as standalone AI projects (Phase 6)
6. fb-photo-scraper — delete (unmodified upstream clone; origin recorded in spec D2)
7. Phase 7 ecosystem pass: link sweep, velox migration, rulesets-reference updates, KB node, cooling clock.
We hold the remaining folds until your reply lands.
|
