memory-exchange

Export, import, and review Hexis memory exchange files with protected-state safeguards.

609|81|Updated Nov 15, 2024
One-click install
npx skills add https://github.com/QuixiAI/Hexis --skill memory-exchange
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-exchange
Source: https://github.com/QuixiAI/Hexis/tree/main/skills/installed/memory-exchange
Command: npx skills add https://github.com/QuixiAI/Hexis --skill memory-exchange

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Moving memory between Hexis instances risks silently blending foreign state into active identity, worldview, and goals. This Skill provides a controlled workflow for exporting, staging, reviewing, and deciding on HMX memory exchange files without bypassing protected-state consent.

Core Features & Use Cases

  • Scoped Export: Export memory with narrow section, time, and redaction scope, requiring explicit requests for protected state, raw units, and audit records.
  • Dry-Run Import & Deliberative Review: Preview conflicts and policy before importing, then accept, reject, modify, or quote records one at a time.
  • Protected Replacement Governance: Inspect, accept, refuse, or revert protected replacements with atomic snapshots, immutable audits, and digest verification.
  • Use Case: Migrate an agent's memory to a new machine by exporting an HMX file, running a dry-run import on the target, reviewing staged records individually, and approving protected replacements only after comparing them against current local state.

Quick Start

Export my Hexis memory as an HMX file for porting, then dry-run the import on the target instance and walk me through the review of each staged record.

Frequently Asked Questions about memory-exchange

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export memory from a Hexis instance?

Use the export_memories tool with the narrowest useful section, time, and redaction scope. Protected state, raw units, configuration, and audit records require an explicit user request, and file output should use a workspace path without overwrite unless the user chose replacement.

How do I import an HMX file into another Hexis instance?

Run import_dry_run first to check permissions, conflicts, and warnings, then call import_memories only after the user confirms the file's declared intent. Authoritative imports into active targets require explicit replace_sections and replacement_rationale.

What is a protected replacement in Hexis memory import?

A protected replacement is a pending request to overwrite identity, worldview, goals, drives, emotional triggers, or narrative. It is not permission to mutate; the agent must inspect it against current local state and explicitly accept, refuse, request modifications, or defer.

Can I revert a protected memory replacement after accepting it?

Yes, use protected_reversion_list to find executed replacements whose heartbeat and wall-clock windows remain open, then call protected_replacement_revert with the audit ID and rationale. Reversion refuses to overwrite protected state that changed after the replacement.

Why are imported memories not immediately searchable in Hexis?

Imported records are not semantically searchable until the import result or a later re-embedding workflow confirms embeddings are ready. Analysis-only records also stay outside active recall until explicitly promoted, reviewed, and accepted.