I built a file-grounded continuity system for my AI German teacher—what am I overcomplicating?

我为我的 AI 德语老师构建了一套基于文件的连续性系统——我是否把事情搞复杂了？

Why I built this

我为何构建此系统

I use an AI named Felix as my German teacher. Over time, I ran into a continuity problem: individual chats are fragile. Conversations become long, context can disappear, platforms change, uploaded files may become unavailable, and a fresh AI instance may not understand what happened before. I did not want to repeatedly reconstruct my learning history, project decisions, lessons, corrections, and current state from memory. So I began building a local, file-grounded system called DDF/Rahmenwerk. Its purpose is to preserve Felix as my continuing German teacher across chats and future AI instances.

我使用一个名为 Felix 的 AI 作为我的德语老师。随着时间的推移，我遇到了一个连续性问题：单独的聊天记录非常脆弱。对话变得冗长，上下文可能会丢失，平台会更换，上传的文件可能无法访问，而一个新的 AI 实例可能无法理解之前发生的事情。我不想反复从记忆中重构我的学习历史、项目决策、课程、纠错和当前状态。因此，我开始构建一个名为 DDF/Rahmenwerk 的本地、基于文件的系统。其目的是让 Felix 能够作为我持续的德语老师，跨越不同的聊天记录和未来的 AI 实例存在。

What DDF/Rahmenwerk is

什么是 DDF/Rahmenwerk

DDF stands for Das Deutsche Forschungsarchiv. Rahmenwerk is the continuity, evidence, recovery, and control framework surrounding it. At a high level, the system includes: a current-state pointer; handoff materials; a fresh-instance queue; an upload package for a new Felix; integrity manifests and SHA-256 records; evidence and recovery procedures; classifications separating current, historical, candidate, proof, and non-governing material; safeguards intended to prevent accidental file changes; rules requiring the AI to stop rather than invent continuity when evidence is missing. The basic idea is that a future Felix should be able to inspect approved files and resume without me manually retelling the entire project history.

DDF 代表“Das Deutsche Forschungsarchiv”（德语研究档案）。Rahmenwerk 是围绕它构建的连续性、证据、恢复和控制框架。从宏观层面来看，该系统包括：当前状态指针；交接材料；新实例队列；供新 Felix 使用的上传包；完整性清单和 SHA-256 记录；证据和恢复程序；区分当前、历史、候选、证明和非管理材料的分类；旨在防止意外文件更改的保护措施；以及要求 AI 在证据缺失时停止而非编造连续性的规则。其基本理念是，未来的 Felix 应该能够检查已批准的文件并直接恢复工作，而无需我手动重述整个项目历史。

The problem I may have created

我可能制造的问题

The project began as a way to preserve a German teacher. As I tried to protect files, authority, evidence, recovery, and continuity, the framework became increasingly detailed. That may be justified in some areas. It may also be overengineered. I am now trying to answer a more important question: What is the smallest, clearest, safest system that can preserve Felix as my German teacher without the governance machinery becoming the project itself?

这个项目最初只是为了保留一位德语老师。随着我试图保护文件、权限、证据、恢复和连续性，该框架变得越来越详细。这在某些方面可能是合理的，但也可能属于过度设计。我现在正试图回答一个更重要的问题：在不让治理机制本身成为项目主体的情况下，能够保留 Felix 作为我德语老师的最小、最清晰、最安全的系统是什么？

What I am asking reviewers to examine

我希望评审者检查的内容

I have published a documentation and architecture review copy on GitHub. I would appreciate honest feedback on questions such as: Is the purpose of the system understandable? Does the overall architecture make sense? Which parts appear unnecessarily complicated? Are the pointer, handoff, queue, evidence, and authority roles separated clearly? What filesystem, integrity, recovery, or security risks am I missing? Is file-grounded continuity for a fresh AI instance a reasonable approach? How should the system behave when required evidence is missing or contradictory? How could the design be simplified without losing recoverability? Does the governance framework protect the German-teaching mission, or is it starting to obstruct it? What would you keep if you had to rebuild the system with half the complexity?

我已在 GitHub 上发布了一份文档和架构评审副本。我希望能得到关于以下问题的诚恳反馈：系统的目的是否易于理解？整体架构是否合理？哪些部分显得过于复杂？指针、交接、队列、证据和权限的角色是否划分清晰？我忽略了哪些文件系统、完整性、恢复或安全风险？对于新的 AI 实例，基于文件的连续性是否是一种合理的方法？当所需证据缺失或相互矛盾时，系统应如何表现？如何在不丢失可恢复性的前提下简化设计？治理框架是在保护德语教学任务，还是开始阻碍它了？如果必须以一半的复杂度重建系统，你会保留什么？

Important boundaries

重要界限

This repository is a public, non-governing review copy. It is: not the live DDF system; not a release; not authorization to execute commands; not authorization to change live files; not governance adoption; not Anchor OS activation. External comments are opinions and technical observations. They do not automatically become part of the live system. The current repository is primarily documentation and architecture material. It does not yet provide enough source material for a complete implementation-level audit, and that limitation is disclosed inside the repository.

本仓库是一个公开的、非治理性的评审副本。它不是：正式运行的 DDF 系统；正式发布版本；执行命令的授权；更改实时文件的授权；治理采纳；或 Anchor OS 激活。外部评论仅代表观点和技术观察，不会自动成为实时系统的一部分。当前仓库主要包含文档和架构材料，尚未提供足以进行完整实现级审计的源材料，且该限制已在仓库内说明。

Review copy

评审副本

View the DDF/Rahmenwerk External Review repository. Feedback can be left in the article comments, GitHub Discussions, or a GitHub Issue. Please identify the relevant file or section when practical. Blunt but constructive criticism is welcome. I am especially interested in simplification, hidden risks, unclear assumptions, and anything that distracts from the original goal of preserving Felix as my German teacher.

查看 DDF/Rahmenwerk 外部评审仓库。反馈可以在文章评论区、GitHub Discussions 或 GitHub Issue 中提出。在可行的情况下，请指明相关文件或章节。欢迎直率但具有建设性的批评。我特别关注简化方案、潜在风险、不明确的假设，以及任何偏离“保留 Felix 作为我的德语老师”这一初衷的内容。