Folder Architecture Methodology in Restrictive Enterprise?

Hi Jake & Community —

Working through your folder architecture and markdown file methodology and genuinely seeing the value. The context load sequence, the living CONTEXT.md approach, the layered structure — it maps well to how I think about systems.

Here's my constraint: I'm working inside Cowork & Chat without access to Claude Code. No terminal, no hooks, no automatic file loading on session start.

The files are there. The structure is there. But Cowork doesn't appear to auto-load them at the start of a session — Claude only reads what it's explicitly pointed to. So the architecture exists but the context doesn't load unless I remember to trigger it manually, which defeats part of the purpose.

My question: Has anyone implemented this approach in an environment without Claude Code — no CLI, no hooks, no programmatic session triggers? And if so, what's the workaround for the auto-load problem?

Specifically wondering:

Is there a reliable way to trigger context load at session start without Claude Code hooks?
Is a "load my context" opener prompt the current best practice for non-Code environments?
Are there tools or patterns that approximate the Claude Code experience for desktop/non-developer users?

I'm working on making the case to my org for this approach — so understanding the real implementation path for non-technical users matters a lot.

Also, being in a highly restrictive, governed, and large enterprise company creates so many bottlenecks for this approach, but the value and impact of application outweighs the "risks."

TYIA,

Colin

16 comments

Folder Architecture Methodology in Restrictive Enterprise?