Concept
The four loops, the forgetting policy and the morning page.
The problem
A local AI answers a question and then forgets. A cloud AI remembers, but the memory belongs to the cloud: the person cannot see it, check it, or delete it. A memory that only grows fills with noise, keeps wrong facts, and is hard to correct.
The four loops
flowchart TD
A[Capture: text, photo, voice, page] --> B[Understand: read, hear, describe]
B --> C[(Tape: what arrived, append-only)]
C --> D[Extract: people, places, plans, decisions]
D --> E[(Memory: facts with sources and time)]
E --> F[Answer with citations]
E --> G[Overnight tidy: merge, contradict, fade]
G --> E
G --> H[Morning page: screen, audio, print]
- Capture. One inbox for typed and pasted text, photos, screenshots, voice notes, audio files and documents. Capture always succeeds instantly, even when understanding has to wait.
- Consolidate. When the computer is idle and on power, Nocturne turns new items into facts, merges duplicates, surfaces contradictions, and lowers the strength of what is not reinforced. A laptop that sleeps at night catches up on the next wake. That catch-up is the one deliberate exception to the rule against tidying on battery: it keeps running above 40 per cent charge, and below that it waits for power unless the person asks.
- Serve. A question gets a short answer built from a small, cited package of facts, never the whole archive. Every claim links to the original it came from.
- Publish. The morning page has four parts: what changed, what needs you, what was let go, and one question.
The forgetting policy
| Signal | Action | What the page says |
|---|---|---|
| Reinforced or repeated | Keep, raise confidence | kept |
| Contradicted | Keep both with valid time, ask | needs you |
| Unreferenced for 30 days | Lower confidence | fading |
| Unreferenced for 90 days | Archive, do not delete | let go |
| The person says forget | Delete with cascade | gone |
| Untrusted source | Quarantine, no promotion | unconfirmed |
Archiving is reversible; forgetting is explicit. Future-dated facts do not fade before their date, and health, allergy and medication facts are kept forever by default. Answering the daily question is a reinforcement signal, so the page trains the memory without a settings screen.
Why this shape
Memory alone is a crowded category, and so is background consolidation. What no product closes is the loop from local multimodal capture to a daily artifact with a deliberate, visible forgetting policy. The page is the product; the memory is the engine.