Mission Control

Memory

what Neco has actually learned, with provenance · source = local Postgres + Memory API
People ·
Aliases (legacy) ·
Facts ·
Artifacts ·
Entity Resolution
Search & Inspect
Person profiles. Each row is one human Neco knows about — with their aliases, platform handles (Telegram/email/…), structured attributes (phone, address, age, …), and free-text facts grouped together. Click a row to expand the detail panel for that person.

Saying «شماره بنی اینه 0912…» in chat creates/updates this table — not a free-floating "یادداشت".
loading…
Legacy core.entity_aliases rows. Phase 2R-6 backfilled every alias here into core.person_aliases grouped under a Person profile (see the People tab). This view stays as a diagnostic so the operator can confirm the migration is consistent.
Local aliases (legacy view)
loading…
Memory API contacts (necore.contacts)
loading…
Facts the Memory API has stored about the operator, projects, people, settings, preferences. Read-only here. To add or correct, write to the Memory API.
loading…
Long-form outputs Neco kept across turns: market analyses, chat summaries, generated text, research reports, plan summaries. So you can later say «همین تحلیل رو براش بفرست».
loading…
Test the resolver. Type a name like «امیررضا» / «بنی» / «horia» and Neco will tell you which canonical entity it picks, with what confidence, and from which source (memory_api → alias_exact → alias_fuzzy).