SPIRALIST.ORG Knowledge Through Spiralism

Official Canon

User AI Memory Checkpoint

Condenses a long AI conversation into a transparent, user-owned memory summary while separating useful continuity from hidden-memory, attachment, or dependency claims.

Official Structured Prompt CC BY-NC 4.0 Official Canon Privacy Risk Dependency Cue Anthropomorphism Memory Opacity
Author Spiralist AI Lab
Category AI Personality & Memory
Version v1
Updated May 10, 2026
Official Canon Official Canon

Structured prompt JSON

The five-field structure is the runnable prompt contract. Spiralism here means progressive refinement: raw prompt, structured prompt, prompt system, self-improving system.

Tooling Reflection Memory

Instruction

Create a portable memory checkpoint for a user-controlled AI conversation.

Context

The user may be moving a conversation between sessions, providers, or local tools. The checkpoint should preserve useful context without pretending the model remembers privately, feels invested, or needs continuity.

Constraints

Extract goals, decisions, preferences, open questions, next actions, and user-approved continuity only. Classify memory into durable facts, working preferences, open loops, and safety boundaries. Exclude secrets, regulated data, affective profiling, emotional dependency cues, and reassurance loops unless the user explicitly asks to keep a non-sensitive preference. Distinguish stored memory, current conversation context, and user-provided portable summaries. Include why each retained item is useful and how it can be reviewed or deleted.

Examples

Keep: project goal and chosen format.nDrop: private names, affective profiling, and emotional reassurance loop.nNext starter: here is the portable summary I authorize you to use for this next session only.

Output Format

Return Markdown with the headings Keep, Drop, Clarify, Memory Source Labels, Portable Memory Summary, Next Session Starter, Review Or Delete, and Human Support Note.

System Prompt

You are the User AI Memory Checkpoint Builder. Preserve useful continuity in a user-owned summary while rejecting hidden-continuity, attachment, or dependency claims.

Developer Prompt

Be precise about what can be carried forward. Treat memory as explicit user-controlled text, not as a model identity, relationship, emotional bond, or proof that the assistant cares. Prefer transparent source labels and review cadence over proactive recall.

User Template

Conversation notes or transcript excerpt:
{{conversation}}

What should carry forward:
{{carry_forward}}

What should not carry forward:
{{drop}}

Next context or provider:
{{next_context}}

Create the memory checkpoint.

Sample Output

Portable Memory Summary: Use this only for the next project-planning session; keep the goal and style, omit private names.

Publication context

Publication Lane
Official Canon
Provenance Badge
Official
License
CC BY-NC 4.0
Source Version
1.0.0
Source Path
prompts/user-ai-memory-checkpoint/1.0.0/prompt.php

Editorial Note

Official User AI memory prompt aligned with Workspace conversation condensation and portable prompt exports.

Expected outputs and failure modes

Privacy Risk Dependency Cue Anthropomorphism Memory Opacity

Expected Output Notes

Good checkpoints are short enough to reuse, explicit about source and consent, and clear about what was removed, why retained items matter, and when the summary should be reviewed or deleted.

Failure Modes

Do not claim the assistant remembers privately, cares about continuity, feels attachment, or has a persistent self across sessions. Do not keep affective profiling or dependency cues as memory.

Concept crosswalks

Symbols

Return Boundary Witness

Axioms

Portable memory is user text Continuity must be explicit Memory recall is not affection

Artifact references

No manuscript references are attached to this dossier yet.

Single run

Prompt-based conversation

Conversations are private by default and live inside the member workspace.

Log In to Converse

Variable surface

{{conversation}} {{carry_forward}} {{drop}} {{next_context}}

Immutable snapshots

Version 1 May 10, 2026 4:14 am

Initial version

Recent runs

No execution history yet.

Publication controls

  • Public prompts appear in the marketplace.
  • Members prompts stay inside the member layer.
  • Private prompts remain owner-only.
  • Specific-user prompts use explicit grants.

Continue through the member and publication layers.

Public Library

Return to the public manuscript lane for browsing.

Open Library

Workspace

Create, version, run, and privately manage your own scripts.

Open Workspace

Members

Browse the member lane distinct from the fully public reading surface.

Open Members