Non Project Memory Packages For Assistants And Social Companions

UAIX already provides a serious foundation for portable, reviewable AI memory, but its public tooling is still optimized for project-centered work rather than everyday assistant or companion use. The AI Memory Package...

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/raw-system-archives-uaix-agent-file-handoff-retired-source-archive-2026-e2db1371/
Source reference	raw/system-archives/uaix/agent-file-handoff/retired-source-archive-2026-06-13/2026-06-06/non-project-ai-memory-wizard/Improvement/Non-Project Memory Packages for Assistants and Social Companions.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-07T02:05:14.3837888Z
Content hash	sha256:e2db13719934fa1125e9ba377aa1613dc50a36c21e19fbfb4dcc66a11c44a2eb
Import status	unchanged
Raw source layer	data/sources/uaix/raw-system-archives-uaix-agent-file-handoff-retired-source-archive-2026-06-13-2026-06-06-non-pro-e2db13719934.md
Normalized source layer	data/normalized/uaix/raw-system-archives-uaix-agent-file-handoff-retired-source-archive-2026-06-13-2026-06-06-non-pro-e2db13719934.txt

Current File Content

Structure Preview

• Non-Project Memory Packages for Assistants and Social Companions
• Executive Summary
• UAIX Wizard Review
• What the wizard already does well
• The published UAIX data model
• Where the fit breaks for non-project use
• Existing Formats Across Assistant and Social Ecosystems
• Proposed Non-Project Memory Package Schema
• Required and optional fields
• JSON Schema examples
• Template Packages and Example Payloads
• Import, Export, and Product Integration Design
• Import and merge behavior
• UI and UX recommendations
• Proposed API surface
• Compatibility, Security, and Compliance
• Compatibility and interoperability guidelines
• Security, privacy, and compliance recommendations
• Roadmap, Risks, and Reference Code
• Milestones, effort, and risk profile
• Sample C# code for serialization, deserialization, and migration
• Open questions and limitations

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

• Source characters: 62911
• Preview characters: 11895

# Non-Project Memory Packages for Assistants and Social Companions

## Executive Summary

UAIX already provides a serious foundation for portable, reviewable AI memory, but its public tooling is still optimized for project-centered work rather than everyday assistant or companion use. The AI Memory Package Wizard is an eight-step, local-first builder that can generate `.uai` files, archives, manifests, JSON-LD graphs, `llms.txt` outputs, a package model JSON, and a browser-generated ZIP, while explicitly avoiding hosted import, repository writes, automatic sync, SDK/CLI behavior, certification, or endorsement claims. Its bundle taxonomy covers Project AI Memory, Project Handoff, Agent Session Memory, Onboarding Memory, Decision Memory, External Handoff Memory, Incident/Audit Memory, and LLM Wiki Export Memory, but there is no published preset specifically for personal assistant, office assistant, or companion-chatbot memory. citeturn12view1turn13view0turn11view0turn18view0

That gap matters because the wizard’s current assumptions are visibly project-oriented. Its required baseline includes `.uai/coding-standards.uai`, and its wizard steps ask about deployment strategy, code review, framework standards, workspace targeting, WordPress/Visual Studio environments, and system discovery prompts. Those are sensible for project memory, but they are a weak fit for non-project assistants whose durable context is more likely to be identity, preferences, routine tasks, contacts, calendar entries, conversation summaries, and trust/consent boundaries. citeturn13view0turn14view0turn21search0turn41view0

Across the broader ecosystem, there is still no single dominant open “assistant memory package” standard. Instead, the landscape is fragmented into two layers. Closed assistant products such as ChatGPT, Claude, and Gemini have memory features, export controls, and some import flows, but they generally do not publish a durable, vendor-neutral public schema for full personal memory portability. Open standards do exist for the major data domains that assistants need: ActivityStreams and ActivityPub for social objects and actors, Matrix for conversational event timelines, vCard and JSContact for contacts, iCalendar and JSCalendar for calendars and tasks, and CardDAV/CalDAV/JMAP for synchronization and sharing. citeturn39view2turn39view4turn40view1turn40view2turn40view3turn42view0turn39view10turn26search0turn39view9turn39view12turn39view13turn39view11turn39view14turn25search1turn25search2turn40view4

The most durable path is therefore not to replace UAIX, but to complement it with a **non-project memory package profile** that keeps UAIX’s strongest ideas—local-first review, explicit manifests, hot-vs-cold memory separation, trust-boundary awareness, and provenance—while adopting a canonical JSON core that can export cleanly into domain standards. The recommended design is a **JSON Schema 2020-12 canonical package**, with optional **JSON-LD 1.1 semantic projection**, plus adapters for **JSContact/vCard**, **JSCalendar/iCalendar**, and a conversation/event export compatible with **Matrix-like** or **ActivityStreams-like** objects. citeturn34search0turn34search1turn11view0turn10view0turn10view2

My practical recommendation is to add three new UAIX-compatible profiles: `office-assistant-memory`, `companion-memory`, and `personal-kb-memory`. Each should preserve UAIX manifest conventions and front-door review behavior, but swap project-specific modules for user-centric modules such as persona, preferences, routines, conversation memory, calendar, contacts, tasks, and consent metadata. This report lays out a proposed schema, templates, workflows, interoperability rules, security posture, roadmap, and example code for doing exactly that. citeturn10view3turn14view0turn18view0

## UAIX Wizard Review

UAIX’s public AI Memory surface is already unusually rigorous compared with most AI-product memory features. On the AI Memory page, UAIX describes AI Memory as compact operating memory that a future actor should load before acting, explicitly distinguishing it from a general knowledge base and advising that long research, old progress detail, and deep rationale should live in a colder wiki-style layer instead of the active packet. The public wizard then turns those supported starter configurations into a local-first package-planning flow with validation, draft restore, prompt nudges, structured-output safety, generated startup files, export artifacts, and ZIP packaging. citeturn11view0turn12view1turn12view2

### What the wizard already does well

| Surface | Current public capability | Why it matters for non-project memory | Primary evidence |
|---|---|---|---|
| Package construction | Eight-step local-first builder with validation, local draft restore, prompt nudges, Safe Structured Output Mode, and live build preview | Strong fit for user-reviewed memory curation instead of opaque hidden model memory | citeturn12view0turn12view1turn13view0 |
| Exports | Package model JSON, manifest JSON, manifest overlay JSON, JSON-LD graph, `llms.txt`, `llms-full.txt`, startup packet, receiver brief, system profile, browser-generated ZIP, canonical ZIP link | Gives a good starting point for portable personal-memory exports | citeturn12view1turn15view0turn15view1turn15view2turn15view3 |
| Bundle taxonomy | Project AI Memory, Project Handoff, Agent Session Memory, Onboarding Memory, Decision Memory, External Handoff, Incident/Audit, LLM Wiki Export | Shows UAIX already thinks in lifecycle- and trust-boundary-specific bundle types | citeturn11view0turn13view0 |
| Machine readability | Human UI and embedded visitor AI digest on the same route | Helpful for future automation and compatibility shims | citeturn12view3turn12view4 |
| Folder structure | Default `.uai/` suite with `.uai/archives/`, active `.uai/`, and `.uai/exports/` | Easily adaptable to a personal-memory folder convention | citeturn12view4turn13view0 |
| Review discipline | Explicit trust-boundary review, no unreviewed chats as truth, human acceptance before promotion | Exactly the discipline needed for personal-data-heavy assistants | citeturn10view0turn10view1turn14view0 |

### The published UAIX data model

The core public UAIX data model is more structured than the wizard UI alone suggests. UAIX states that supported starter bundles are presets over one canonical file-template registry, and the public AI Memory page shows a generated manifest containing fields such as `bundle_id`, `name`, `description`, `intended_use_case`, `lifecycle`, `trust_boundary_notes`, `included_files`, `file_set_rule`, `declared_package_profiles`, `universal_required_files`, `profile_required_file_sets`, and `required_files_effective`. For the Project AI Memory starter, the universal required files are `.uai/identity.uai`, `.uai/world-context.uai`, `.uai/totem.uai`, `.uai/taboo.uai`, `.uai/short-term-memory.uai`, and `.uai/coding-standards.uai`. citeturn11view0

That manifest model is important because it can be reused almost unchanged for non-project profiles. In other words, the biggest architectural gap is not the absence of a package model; it is the absence of **profile-specific non-project semantics** on top of that model. UAIX’s own taxonomy already says new configurations should exist when they have a different lifecycle, trust boundary, or consumption pattern. Personal assistant memory and companion memory meet that criterion cleanly. citeturn10view4turn11view0

### Where the fit breaks for non-project use

The public limitations are explicit. The wizard does not claim hosted import, automatic repository writes, automatic LLM Wiki sync, SDKs, CLIs, certification, endorsement, or broad package-manager behavior as current support. The roadmap reinforces that “managed AI Memory packages,” hosted imports, sync, and developer tooling remain future or planned work rather than present public support. citeturn13view0turn14view0turn18view0turn20view0

For non-project use cases, the deeper issue is content fit. The wizard’s Basics, Collaboration, Operations, and Governance steps ask about owner/review team, audience, sensitivity, target environment, framework standards, deployment strategy, code review, release gates, workspace routing, and system discovery. That is excellent for a delivery project, but awkward for an office assistant managing a person’s preferences, calendar, tasks, and contacts—or for a social/companion bot that needs persona, relational boundaries, and selective episodic memory instead of coding standards and deployment evidence. Officially, every launch-baseline package still includes `.uai/coding-standards.uai`, and the receiver is prompted to inspect source trees, manifests, CI config, and deployment docs. That is the central reason a complementary non-project package layer is needed. citeturn13view0turn14view0turn21search0

## Existing Formats Across Assistant and Social Ecosystems

The current ecosystem splits into **closed assistant memory systems** and **open interoperable data standards**. The former are better at end-user personalization; the latter are better at portability, versioning, and long-term interchange. For a practical implementation, the right answer is a composite design rather than trying to force one ecosystem’s format onto all others. citeturn39view2turn40view1turn40view2turn39view10turn39view13turn39view14

| Format or system | Scope | Core objects / schema style | Privacy and user controls | Versioning / sync / sharing | Notable size limits or constraints | Relevance to a non-project package | Primary sources |
|---|---|---|---|---|---|---|---|
| **UAIX AI Memory Wizard** | Local-first AI memory packaging | File-based `.uai` records + manifest JSON + JSON-LD + `llms.txt` + ZIP | Trust-boundary notes, redaction guidance, explicit reviewer acceptance before promotion | Canonical template registry + manifest overlay; no hosted sync/import | No public numeric bundle-size limit published in docs; browser-generated ZIP only | Strong as packaging/governance shell, weak as personal-data profile out of the box | citeturn12view1turn11view0turn10view0turn18view0 |
| **ChatGPT memory + export** | Consumer assistant memory | Saved memory summary plus exported account ZIP | Memory summary view/edit, forget/delete, turn memory off, Temporary Chat; Data Controls for training/export | Export via account Data Controls; public docs do not describe a stable public package schema | Chat exports not available for Business/Enterprise accounts in the cited export article | Good example of user controls; weak as open package format | citeturn39view2turn39view3turn31search9turn39view4turn41view0 |
| **Claude memory + export** | Consumer and work assistant memory | Memory summary synthesized from chats; conversation export | View/edit memory, toggle memory/search, incognito chats, citations to past chats | Data exports include memory; docs say import/export memory is experimental and in development | Export available for individual users on web/desktop, not iOS/Android in cited export doc | Strong precedent for memory summary + citations + incognito boundary | citeturn39view5turn40view1 |
| **Gemini saved info + import/export** | Consumer assistant memory | Saved info, memory, activity export, import from other AI platforms | Delete saved info, turn memory on/off, Temporary Chat, activity controls | Takeout export; direct import from ChatGPT/Claude ZIPs and prompt-based memory import | Full chat import supports `.zip`, 5 GB/file, up to 5 ZIPs/day; feature unavailable in EEA/Switzerland/UK per cited doc | Very relevant interoperability precedent, but policy/training implications are significant | citeturn40view2turn40view3turn42view0 |

Why This File Exists

This is a memory-system evidence file from uaix.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This file is memory-system evidence. It records source history, archive transfer, intake disposition, or another piece of provenance that should be retrievable without becoming an unsupported public claim.

Structure

The file is structured around these visible headings: Non-Project Memory Packages for Assistants and Social Companions; Executive Summary; UAIX Wizard Review; What the wizard already does well; The published UAIX data model; Where the fit breaks for non-project use; Existing Formats Across Assistant and Social Ecosystems; Proposed Non-Project Memory Package Schema. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

• Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
• LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
• Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
• Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

• Source overview
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

• Current observation: 2026-06-22T01:56:21.9510185Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-1088 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Non Project Memory Packages For Assistants And Social Companions",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/raw-system-archives-uaix-agent-file-handoff-retired-source-archive-2026-e2db1371/",
    "source_reference":  "raw/system-archives/uaix/agent-file-handoff/retired-source-archive-2026-06-13/2026-06-06/non-project-ai-memory-wizard/Improvement/Non-Project Memory Packages for Assistants and Social Companions.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:e2db13719934fa1125e9ba377aa1613dc50a36c21e19fbfb4dcc66a11c44a2eb",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-07T02:05:14.3837888Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-1088",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}