From 7128e26fd069b4d9fb025c1e1e1800a77ff9fe81 Mon Sep 17 00:00:00 2001 From: axiomlogicnexus Date: Tue, 19 May 2026 22:24:54 +0200 Subject: [PATCH] Move default worktree parent out of root --- ...CEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/ops/HYPERTWIST_WORKTREE_PLACEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md b/docs/ops/HYPERTWIST_WORKTREE_PLACEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md index 591b08e..0a0304a 100644 --- a/docs/ops/HYPERTWIST_WORKTREE_PLACEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md +++ b/docs/ops/HYPERTWIST_WORKTREE_PLACEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md @@ -14,10 +14,12 @@ Policy: - Do not create new ad hoc packet worktrees directly under `C:\` such as `C:\HTB*`, `C:\CTW*`, or similar root-level packet folders unless the user explicitly approves that exact placement. -- Default clean bounded-implementation and validation worktrees to the approved - scratch parent `C:\w\...` when that route is in use. -- If `C:\w` is not appropriate, ask for a replacement parent rather than - inventing a new root-level folder family. +- Default clean bounded-implementation and validation worktrees to the + approved non-root parent `C:\Workspaces\HyperTwist-worktrees\...`. +- Do not default new HyperTwist packet worktrees to `C:\w\...` anymore unless + the user explicitly asks for that scratch parent again. +- If `C:\Workspaces\HyperTwist-worktrees` is not appropriate, ask for a + replacement parent rather than inventing a new root-level folder family. Validation artifact rule: