Local first
The user's files should remain the canonical truth. Hosted services may help later; they should not replace ownership.
Local-first memory
Notes should become intentional memory without becoming a trap.
The user's files should remain the canonical truth. Hosted services may help later; they should not replace ownership.
Markdown plus clear metadata should stay readable, linkable, reviewable, and useful without hiding memory in a captive system.
AI tools should meet explicit contracts and receive bounded context, not whole-vault access by default.
First product boundary
The first work is to prove a local-first notes service over open Markdown files, with a minimal browser surface and the same API available to browser, CLI, AI, and future native clients.
Markdown files as canonical truth. Local API as shared access layer. Minimal browser UI as proof surface. AI tools as ordinary clients. Sync and publishing as future seams.
Memory with boundaries
Not every agent needs the whole workspace. Inoteus is exploring human-readable leases that name what context may be used, by whom, for how long, and with what audit trail.
Ritual without surveillance
The older Inoteus impulse remains: connection, expression, awareness, shared intelligence, and ritual over algorithm. The rebirth gives that impulse a practical local-first body.
Current status
Inoteus is in rebirth. There is no public signup, hosted sync service, or download announced here yet. The public direction is being shaped around local files, local API, links, search, explicit auth, verification, and bounded AI context.