How the setup works, and where it stops for you.

The deliverable is an operating environment that gets more useful with use: context compounds, recurring work becomes a named workflow, and verified improvements propagate forward into new builds. The same operating pattern runs in our ChatGPT workspace and in Claude + Cowork client builds. The exact files, connectors, and interface follow the platform and the work.

Each build starts from the current Sidekick foundation and is populated with your context, boundaries, and highest-value workflows. The core is file-first, inspectable, and portable. Your business context stays in a workspace you can read, own, and move; live connectors are added where they make the work more useful.

Shown here: a Claude build. A ChatGPT or Copilot build holds the same parts in that tool’s own format; chapter 05 shows how.

A few root files carry the day-one load: Start_Here.md (how to start a session and your named first win, no placeholders), Your_Workflows.md (your priority workflows with copy-paste prompts), and Starter_Prompts.txt (the routing table that makes triggering reliable). A reader who opens the folder cold finds an entry point, a map, and no internal build artifacts.

Most people run their AI memory like a junk drawer: everything goes in, nothing comes out, and eventually you are afraid to open it. The fix is a handful of boring disciplines, none of which need a better model. In a Claude Code implementation, CLAUDE.md is the project instruction layer loaded into sessions, so it can carry the identity, routing, memory, and safety rules that must always hold. Other environments use an equivalent instruction layer. [R4]

Give the workspace an index. A simple map of every file and what it holds lets the model look up the one relevant, current thing and read just that. With no index, it rereads the entire filing cabinet to answer one question, fills its working memory (the context window) with noise, and forgets the answer. People read that as the model getting forgetful. What is really happening is it has more memory than it can sort, so it holds all of it at once and weights none of it. The index is also where relevance and recency get decided. For most people hitting the “it cannot remember anything” wall, this is the highest-impact fix almost nobody has in place.

Rewrite the state, do not append to it. The current-state file is rewritten at the end of each session so it always reflects what is true now, instead of stacking session recaps until it contradicts itself. This single discipline kills most of the instruction-pileup decay on its own.

Route memory by type. What is true now (priorities, business, people) lives in one place. What happened when (decisions, meeting notes) lives in another. How things get done (standing rules, workflows) lives in a third. Every “remember this” is sorted to the right type before it is written, so the assistant can actually find it later.

Keep long work resumable. A substantial job gets a compact control surface with its objective, completed milestones, evidence, failed paths, approval boundaries, and exact next action. If a conversation is interrupted, the system resumes from the record instead of reconstructing the job from chat history.

A skill is a saved specification that wraps a recurring piece of judgment: what to read, what to produce, what never to do. A core set is active from day one, and a deeper library opens up as your usage matures. Every skill carries explicit trigger phrases, because manual triggering is the reliable path on this platform (more on that under honest boundaries).

For substantial work, orchestration sits above the individual skills. It locks the outcome, chooses the specialists, preserves state, and checks each handoff before the next phase begins. Work with real branches can use a small work graph so independent parts run safely and rejoin at one verified result. Simple work stays simple.