This repository was archived by the owner on Aug 20, 2026. It is now read-only.
Repository navigation
Stop sending every session to the superseded plan - #2
Merged
Merged
Conversation
CLAUDE.md told anyone designing here to first read `docs/plan.md` in the admin repo. That file became `docs/archive/plan.md` on 2026-08-07, and its index entry now says "do not plan from it": 31KB of CouchDB, git remotes and per-workspace vault storage, none of which is the plan. The instruction kept resolving, kept being followed, and kept handing out the architecture we replaced. So this file describes this package and nothing else. No pointer into the private repo, no hosted roadmap, no CouchDB in principle 1. Two rules take their place: do not design this package around the hosted layer, and do not put anything private in a repo meant to go public at v0.1.0. README loses the same stale sentence -- there are no git remotes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7TgsCgsXW9g75gGDpYCy8
OKF appears nowhere in this package. Not in CLAUDE.md, not in knowledge.py, not in a docstring. Meanwhile the vault this is built for keeps an OKF frontmatter discipline precisely so an AI can ask for the notes whose `type` is `meeting` instead of grepping for the word, and property search is how that question gets asked. The only thing the docs said about property search was that it exists because we do not evaluate Dataview. True, and it reads as a consolation prize, which is how a load-bearing surface gets treated as a corner of the API by someone deciding what to optimise. Named now, with what it is: an open Google Cloud spec, v0.1 dated 2026-06-12, one hard rule -- parseable frontmatter with a non-empty `type` -- and five optional keys worth being good at. We do not implement it and we do not validate it. What we owe it is that querying those keys is fast, paginated and honest about what it missed. Per ADR-0018 the bullet says where those facts came from, because they came from the announcement rather than the normative spec. The first draft of this commit cited a github.com URL that does not exist. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7TgsCgsXW9g75gGDpYCy8
Design principle 1 said the vault is the boss and, as evidence, that we keep no copy. True of this package. False as a universal, because a VaultProvider backed by a remote store has to keep a local one, and the private package's whole reading path is exactly that. Two documents, both read as ground truth, disagreeing on whether caching is allowed. Rewritten so the rule says what it actually protects: this package owns no database of content and holds no copy of its own, and what it forbids is becoming the system of record -- a store of note content Obsidian gets no vote in. A backend that keeps a local copy of a remote store still honours it, as long as plain markdown on disk is what the tools read. The invariant is unchanged. Only the evidence offered for it was wrong. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7TgsCgsXW9g75gGDpYCy8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
CLAUDE.mdtold anyone designing here to first readdocs/plan.mdin the admin repo. That file becamedocs/archive/plan.mdon 2026-08-07, and its index entry now says do not plan from it: 31KB of CouchDB, git remotes and per-workspace vault storage, none of which is the plan any more. The instruction kept resolving, kept being followed, and kept handing out the architecture we replaced.The same file also named "CouchDB sync, git remotes, Stripe, Hetzner" as what was coming, and design principle 1 called CouchDB and git the hosted transports. All true in July, none true now.
What changed
CLAUDE.mddescribes this package and nothing else. No pointer into the private repo, no hosted roadmap, no CouchDB. Two rules take their place:Design principle 1 keeps its point (markdown on disk is the source of truth, anything that syncs is a transport projecting onto it) without naming a specific transport that no longer exists.
README.mdloses the same stale sentence. There are no git remotes.Everything else is unchanged: the seven design principles, the architecture facts, the open-core extension contract, the conventions.
Verification
Documentation only, no Python touched. Every relative link in the repo resolves (checked with the link checker added on the admin side, which is where the original broken pointer lived).
Generated by Claude Code