A file-first operating layer for my knowledge, writing, and public site
This is the page I should have linked first. The Digital Twin is not just a repo name. It is the system that reads my knowledge base, routes work, writes assets back into the system, and keeps improving how it operates over time.
Retrieve first
The twin starts from durable files instead of chat memory: wiki indexes, outputs, prior essays, and explicit task rules.
Write back
Useful work should leave assets behind: pages, summaries, prompts, README upgrades, and publish-ready content.
Learn over time
Stable preferences and recurring mistakes become reusable defaults instead of being rediscovered every session.
What the system actually does
The main idea is simple: don't let useful AI work disappear into chat history. Let it operate on durable files, then leave new durable files behind.
Best use cases right now
- website audits and page rewrites
- blog drafting from durable notes
- repo landing-page cleanup and public packaging
- knowledge-base distillation into reusable files
In practice, this site is one of the clearest outputs of that loop: the twin audits pages, identifies weak presentation, proposes stronger packaging, and ships the actual changes.