Evolve Nagato from a response surface into a transparent, game-scoped companion: stable visual Recall, inspectable model/tool traces, compact agent-owned drawers, and a provenance-preserving local game knowledge library.
Each workstream has schemas, UX, test seams and acceptance criteria.
21 generative + 1 Nomic embedding model at the live local endpoint.
Start with usability/provenance, then ingestion and retrieval.
Product principles
Raw first
Persist immutable raw provider and tool outputs. Normalized cards and local-model explanations are derived views with explicit provenance.
Agent-owned mutation
Drawer + buttons compose editable prompts into Chat; validated actions perform mutations. Filters never mutate records.
Game-scoped privacy
Every screenshot, trace, document, chunk and embedding belongs to normalized game_id. Local files require explicit roots and previews.
Honest reasoning UX
Show reasoning only when the provider emits a supported reasoning channel. Never label status prose or reconstructed summaries as raw chain-of-thought.
Recommended order
Key architectural decision
Do not bolt RAG, raw tool output, and Recall metadata into the JSON GameStore. Keep campaign records there for now, but add durable SQLite stores for traces and source artifacts, then expose narrow bridge commands to the UWP. The widget remains a renderer and intent composer.
Pages
Recall evidence
Selection stability, raw VLM, OCR, review and carousel provenance.
Reasoning & tools
Live fading tail, expansion, historical trace inspection and raw output.
Drawer UX
Filter + plus compression and icon swap.
Source ledger
Capture every GTC/tool source with versions and provenance.
Game ingestion
Walkthroughs, wikis, PDFs and install Extras onboarding.
Retrieval/RAG
FTS5 + Nomic embeddings + optional reranking.
Visual concepts
Faithful current/proposed shell renders, trace variants and interactive Recall tabs.
Live evaluation
Torment benchmark from 33 actual manual/chat turns, plus future game cohorts.
Implementation roadmap
TDD slices, file map, dependencies and release gates.