10x-init

To set up a directory structure for change tracking, you can scaffold a standardized /context layout that creates dedicated folders for in-flight changes, archived history, and foundation documentation without overwriting existing files.

Idempotent repository scaffolding creates directories and canonical README files only if they are absent. This ensures teams can establish consistent documentation conventions safely, rerunning the setup without modifying or destroying any existing project content.

To structure cross-change living docs, create a foundation directory within your context workflow. This designated space holds cross-change documentation, separate from in-flight changes and archived history, ensuring living docs remain uncluttered by change-scoped content.

Yes, you can run context workflow setup multiple times safely. The scaffolding process applies idempotent create-if-absent behavior, meaning it initializes the directory skeleton and README files only when they are missing and never overwrites existing content.

The best way to organize archived history and in-flight changes is separating them into distinct context directories. This repository convention establishes an archive treated as read-only history and a dedicated folder for active changes.

You need to initialize a foundation directory when starting a new project or adopting repository conventions from day one. It provides a consistent place for cross-change living docs, separating foundational architecture from isolated change tracking.