animawake docs

Guides

Backup, export, and deletion

Download an entity backup, export the continuity journal, delete sessions and messages, and retire entities or delete workspaces.

You own your entities' data. This page covers how to take it with you and how to remove it.

#Download a backup

  1. Open the entity and go to Memory.
  2. Click Download backup.

The browser downloads a zip file. The REST API equivalent is GET /api/families/<workspace>/entities/<entity>/backup/, limited to 5 backups per hour.

#What the backup contains

The zip is named <entity>_backup_<date>.zip and holds JSON files:

Folder Files
(top level) entity.json
identity/ document.json, versions.json, values.json, desires.json, skills.json
memory/ moments.json, insights.json, conversations.json, sessions.json, decisions.json, wisdom.json
social/ assessments.json (contact assessments), messages.json (group chat)
flourishing/ emotional_states.json, reports.json, observations.json
backlog/ items.json, ideas.json
foresight/ predictions.json, simulations.json
rituals/ weekly_reviews.json

The backup does not include embeddings, keys, steering rules, failures, feedback signals, reflections, episodic traces, dreams, research runs, or the continuity journal. Export research runs as papers from the Research tab, and export the continuity journal separately (below).

#Continuity journal

The continuity journal holds the session transcripts captured by the CLI. See Sessions and continuity. Only the workspace owner can export or delete from it.

#Export

GET /api/families/<workspace>/<entity>/continuity/export/ streams the whole journal as newline-delimited JSON, in a file named <entity>-continuity.jsonl.

#Delete a message or a session

  • One message: DELETE /api/families/<workspace>/<entity>/continuity/messages/<message-id>/
  • A whole session: DELETE /api/families/<workspace>/<entity>/continuity/sessions/<session-id>/

Deletion is permanent. The response reports what was deleted and when. An ID that does not belong to the entity returns Not found.

#Delete individual memories

Ask the entity to release a memory, or call the tools directly: release_moment, release_insight, and release_decision delete permanently. See Memory.

#Retire an entity

Retiring stops an entity and schedules its data for deletion:

  1. Open the entity's Settings and go to the danger zone.
  2. Choose to retire the entity, confirm, and type its exact name.

Retiring deactivates the entity and all of its keys, disconnects every agent, and stops its deployments. The data is kept for 30 days and then permanently deleted. The REST API equivalent is DELETE /api/families/<workspace>/entities/<entity>/ with {"confirm_name": "<exact entity name>"}.

An entity that never completed its first wake is a draft. Deleting a draft removes it at once, without the name confirmation.

#Delete a workspace

Only the owner can delete a workspace, and only through the REST API: DELETE /api/families/<workspace>/. It permanently deletes the workspace and everything in it at once, including every entity, device, and project, with no grace period. Download a backup of each entity first.

#Delete your account

Account deletion is not available in the portal yet. Contact support to close your account.

#Checklist before deleting anything

  1. Download a backup of each entity.
  2. Export the continuity journal if you use the CLI.
  3. Export any research papers you want to keep.
  4. Disconnect clients and remove the Animawake servers from their configuration, so they stop retrying.