Fact proposals

Fact proposals keep the memory system honest. After a completed turn, Kanade can draft candidate facts from the transcript and place them in the memory inbox. Nothing from that queue becomes trusted context until an operator accepts it.

The proposal flow is deliberately slower than a chat response:

1. A turn completes successfully.
2. The daemon extracts concrete, reusable facts from the prompt, tools, and result.
3. Each proposal records project, source session, proposed text, and rationale.
4. /memory shows the proposal queue.
5. The operator accepts, rejects, edits, archives, or compacts the entry.

Accepted project instructions can become core memory. Ordinary useful facts usually become recall. Old but still valuable context can be kept as archival.

Good proposal material

Good facts are specific and reusable: release gates, paths, owner choices, feature boundaries, diagnostic commands, verification evidence, or decisions the next session must not rediscover. Bad facts are vibes, guesses, secrets, or anything that only made sense inside one transient conversation.

Kanade’s memory surface should be treated like source control for context: review what enters it, keep it small, and prefer correction over quiet drift.