Everything the pilot gained after the first tag: the design note that explains where it is going, and the parts a stranger needs in order to use or contribute to it.
New
docs/bitemporal.md— the design note for bi-temporal edges. When you materialize the graph instead of parsing it at query time, give every edge a validity window (valid_from/valid_to/observed_at) so a rebuild closes superseded facts instead of deleting them: history is kept, recall prefers the present,as_ofqueries can reconstruct the past. The day-1 A/B result — context size ~unchanged, candidates ~60% fresher by mean age — is written up with its caveat: one day, one corpus, longitudinal effect, not a benchmark.- A roadmap in the README with Now/Next, and the two known defects named as open issues rather than footnotes.
AGENTS.md— for the reader who is an agent: it is a pilot, and the absent parts are deliberate.FOR-ROBOTS.md,CITATION.cff, per-claim attribution in the README (which claim is backed by what), the contributor deal (no CLA, you keep your copyright, 48h answer), and changelog categories for these auto-generated notes.
Known defects, still open
- #1 — the indexer ingests
.stversionsbackups, sync-conflict copies and.obsidianjunk as if they were notes: five files where there is one. - #2 — no tests at all, on 677 lines.
Both are scoped and free to take. Until #2 exists, pilot is the only word this repo is entitled to, and the README says so.
What's next
A smoke test that runs without downloading a model, ignore rules for the indexer, then v0.2 — a public benchmark with a synthetic mini-vault, ~200 hand-labeled queries stratified by type, and a full ablation matrix. The interesting question is not "does graph help" but for which query classes. That line is a plan, not a result.
From here on every noticeable change ships as its own release, so this feed — not the commit graph — is where you can see whether "pilot" has stopped being the right word.
Full Changelog: v0.1.0...v0.1.1