# The Sovereign Workshop: Introducing simulacrum

- Author: @gurupanguji
- Date: 2026-03-07
- URL: https://gurupanguji.com/blog/2026/03/07/the-sovereign-workshop-introducing-simulacrum/
- Categories: essay, ai
- Tags: ai, anthropic, claude, codex, coding, gemini, google, internet, lifehack, llm, model, openai, philosophy, productivity, technology

---


<!-- wp:paragraph -->
<p>There is a specific comfort in a couch that has already memorized the shape of your back. You don't adjust; you just sit. For the last two weeks, my terminal has started to feel like that familiar seat. I am finally seeing a strong signal: when you move your memory out of the model's black box and into your own local files, every session leads to additional value.</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>I've templatized my solution and call it <a href="https://github.com/gurupanguji/simulacrum">gurupanguji/simulacrum</a>. It is a clean, open-source template for LLM-independent personal context management. I am releasing it today on GitHub.</p>
<!-- /wp:paragraph -->

<!-- wp:heading {"level":3} -->
<h3 class="wp-block-heading">The Prompt-to-Project Leap</h3>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>The creation of <code>simulacrum</code> itself was the "meta" proof of the protocol. I had the idea for a clean, open-source version of my context-management system at 10:00 AM. By 10:15 AM, the entire repository was live on GitHub, fully formed with protocols, placeholders, and a personal-context skill. This wasn't a feat of typing speed. It was the result of a system that finally stopped treating me like a stranger. My agents knew the "earned frame" of my life: my skepticism, my preference for short sentences, and my mandatory branching workflow. The time it took from idea to generation was the length of a single prompt.</p>
<!-- /wp:paragraph -->

<!-- wp:heading {"level":3} -->
<h3 class="wp-block-heading">Ending Agent Amnesia</h3>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>Model amnesia is the tax we pay for fragmented context. I often start a task in Gemini and hit a token limit or a reasoning wall. I switch to Codex or Claude to finish the work, but the new agent is a stranger. We are currently living through a period of "Agent Amnesia" where we switch models and lose the last hour of our lives.</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>I need a system that defaults to remembering who I am and the work I've done. <code>simulacrum</code> not only continues the context because of its compounding philosophy, but also ensures my context stays mine, independent of whichever model is currently holding the pen.</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>The architecture is minimal: a simple scaffolding that guides agents to write relevant context into shared files across models.</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>I am not sure if this setup will stay relevant as models evolve. But even if the companies themselves aren't motivated to preserve my context, <code>simulacrum</code> ensures it stays mine.</p>
<!-- /wp:paragraph -->

<!-- wp:heading {"level":3} -->
<h3 class="wp-block-heading">The Runway Stack</h3>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>I treat my environment as a "runway stack." Each layer is designed to remove drag. I use Ghostty for a jitter-free terminal. I use a minimal <code>zsh</code> setup. The core architecture is a hidden <code>~/.agents</code> directory. This is the digital nervous system of my workshop.</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>It contains three primary components:</p>
<!-- /wp:paragraph -->

<!-- wp:list {"ordered":true} -->
<ol class="wp-block-list"><!-- wp:list-item -->
<li><strong>The Personal Directory</strong>: Markdown files that store the grit of my actual process in <code>personal/</code>.</li>
<!-- /wp:list-item -->

<!-- wp:list-item -->
<li><strong>Specialized Skills</strong>: Functional primitives that reside in <code>skills/</code>.</li>
<!-- /wp:list-item -->

<!-- wp:list-item -->
<li><strong>The Compounding Protocol</strong>: A mandate that forces the agent to synthesize what it learned and propose updates to the core files.</li>
<!-- /wp:list-item --></ol>
<!-- /wp:list -->

<!-- wp:paragraph -->
<p>By symlinking these files into the configuration folders of tools like Codex and Gemini, I create a shared memory. If I update a preference on my laptop, a <code>git pull</code> on my desktop ensures my agents are perfectly calibrated within seconds.</p>
<!-- /wp:paragraph -->

<!-- wp:heading {"level":3} -->
<h3 class="wp-block-heading">Sovereignty and Scale</h3>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>The value of <code>simulacrum</code> is independence. You are no longer beholden to the memory features of a specific provider. This local-first approach ensures your context is portable and private.</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>This architecture also allows for easy integration with exciting developments like <em>openclaw</em> and <em>nanoclaw</em>. Whether you are using a heavy-duty CLI or a lightweight agentic script, the source of truth remains the same. You are building a cognitive auxiliary that grows with you rather than resetting every morning.</p>
<!-- /wp:paragraph -->

<!-- wp:heading {"level":3} -->
<h3 class="wp-block-heading">Open Source and Contributions</h3>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>This is the first step. I am making the <code>simulacrum</code> template public to see what others build when they stop repeating themselves. Hopefully it's as useful to you as it is to me.</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>You can find the repository here: <a href="https://github.com/gurupanguji/simulacrum">gurupanguji/simulacrum</a></p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>I invite you to try it, star the repo if you find it useful, and contribute your own skill templates. We are building the primordial primitives of a duct-taped life, one session at a time.</p>
<!-- /wp:paragraph -->
