Second Brain

Retain VPS-side /root/aj-ea workspace as dormant fallback; route all EA work through Cowork EA estate on AJ's Windows PC. Captured as [OPERATIONAL] policy in aj-workspace session-learnings.md line 5.

1 min read

Retain VPS-side /root/aj-ea workspace as dormant fallback; route all EA work through Cowork EA estate on AJ’s Windows PC. Captured as [OPERATIONAL] policy in aj-workspace session-learnings.md line 5.

Decision

Retain VPS-side /root/aj-ea workspace as dormant fallback; route all EA work through Cowork EA estate on AJ’s Windows PC. Captured as [OPERATIONAL] policy in aj-workspace session-learnings.md line 5. Three concrete reopen triggers per premortem: (1) broken cross-ref from aj-workspace memory, (2) root storage pressure >10 GB, (3) 12 months elapsed since last touch — whichever first.

Rationale

AJ’s explicit call after I presented three remediation paths. Premortem surfaced three failure modes (silent skill/MCP drift in /root/aj-ea/.claude/; hypothetical-fallback-never-needed + cross-refs stale; auto-memory dir growth from cron touches) — each mitigated by drift detection, quarterly cross-ref liveness check, and trigger-driven reopen rules now encoded in the policy. detect_biases returned 0 biases on the rationale. Net: reversible decision, 60 MB cold-storage cost, preserves Law 2 cross-refs without patching, preserves local git history, keeps SSH-only EA escape hatch. Trigger-driven reopen prevents indefinite dormancy from compounding into silent debt.

Alternatives Rejected

Outcome

Pending

Graph View

Backlinks