Detailed Analysis
A Reddit user on r/ClaudeAI presents a detailed architectural question about structuring "Cowork" — a Claude-based workflow system organized around hierarchical `CLAUDE.md` instruction files — for two entirely separate professional contexts: a consulting practice with multiple clients and an independent SaaS product build. The post reflects a sophisticated, if self-described non-technical, understanding of the challenges involved in using AI assistants across siloed workstreams. The proposed folder architecture separates the two roles at the top level (`Consultant/` and `SaaS/`) with a shared `_shared/` directory for cross-cutting identity documents, and drills down into per-client subdirectories under the consulting branch. The core questions center on how instruction layers cascade (or should be prevented from cascading), where to place `CLAUDE.md` files in the hierarchy, and how to maintain voice consistency without duplicating documents.
The questions raised illuminate a rapidly emerging design challenge in AI-augmented personal productivity: how to give a single AI assistant enough persistent context to be genuinely useful, while preventing context bleed between unrelated or confidential workstreams. The user's concern about "drift" — the gradual erosion of role-specific behavior as context layers interact unexpectedly — is particularly telling. Cowork-style systems rely on hierarchical markdown files that the Claude environment reads at session initialization, meaning that file placement is effectively a form of scoped instruction programming. The user's instinct to isolate clients at the folder level and place `CLAUDE.md` files at the client directory root is architecturally sound, but the unresolved questions about whether Claude reads all upstream parent files reveals a critical gap: most users do not yet have a clear mental model of how context inheritance actually works in these systems.
The multi-client confidentiality concern is arguably the most consequential question in the post. In professional consulting contexts, the accidental blending of client information — even at the level of terminology, project framing, or implicit associations — represents a meaningful risk. The user is asking, in effect, whether folder-level separation constitutes genuine information isolation or merely organizational tidiness. This is a question that current AI workflow tooling has not answered clearly or publicly, and the ambiguity is significant: unlike traditional software where access controls are enforced at the system level, AI context management depends on instruction-layer discipline rather than hard technical boundaries.
The post sits at the intersection of two broader trends. First, the professionalization of personal AI workflows — users are no longer simply prompting Claude for one-off tasks but engineering persistent, role-aware environments that approximate the functionality of dedicated software tools. The architecture the user is attempting resembles a lightweight content management system for AI instruction sets, complete with inheritance, modularity, and override logic. Second, there is a growing recognition that voice and identity consistency across AI interactions requires deliberate document management — the user's shared `voice-and-anti-AI.md` file gestures at the emerging practice of maintaining canonical style guides that constrain AI output toward a specific authorial persona. Both trends point toward a future in which "AI workflow architecture" becomes a distinct skill set, separate from both traditional software engineering and conventional productivity system design, and increasingly relevant to knowledge workers operating across multiple professional domains simultaneously.
Read original article →