Take NOTES.md back off this branch
It is the v0.1.0 release note, it was untracked before this work started, and it has nothing to do with ยง8.8. A `git add -A` swept it into draft 2 of the spec; the implementation review caught that, and a second `git add -A` in the commit that was fixing it put it straight back. The file stays on disk, untracked, exactly as it was found.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 file changed,
+0
−24
NOTES.md+0 −24
diff --git a/NOTES.md b/NOTES.md| deleted file mode 100644 |
| index 8c8ee57..0000000 |
| --- a/NOTES.md |
| +++ /dev/null |
| @@ -1,24 +0,0 @@ |
| -# Memoria v0.1.0 |
| - |
| -First release, and the first public one of Memoria at all: the suite's |
| -shared memory, one instance per team. Ask a question, get an answer |
| -grounded in your team's own documents โ with a citation you can open, |
| -every time. |
| - |
| -What this release is, precisely: a search engine, not an assistant. There |
| -is no model call anywhere in this binary. Passages and index are sealed |
| -at rest under the team's own key, and no document leaves the instance at |
| -query time or at indexing time, because nothing is sent anywhere to be |
| -indexed. Signing in does fetch `/.well-known/keymail` for the domain in |
| -the address typed, so a DNS name leaves; no document does. |
| - |
| -The artifact is a stripped linux/arm64 binary, built with `make release` |
| -and stamped so that `GET /api/version` answers `v0.1.0` rather than the |
| -`dev` default โ which is what lets a deploy check actually fail. |
| - |
| -Verify what you downloaded: |
| - |
| - shasum -a 256 memoria-linux-arm64 |
| - |
| -Built from this tag with CGO disabled, so it has no runtime library |
| -dependencies beyond the kernel. |