admin

Pin a memory as a standing rule

Make a memory a standing rule. Every run in its scope carries up to 10 pinned memories, protected rules first and then newest unprotected pins, whatever the run asks. Protected rules count against this limit. A pin protects the memory from Curator decay, prune, and consolidation. A personal memory stands only in a run that answers its owner in the owner's own chat-platform direct message. A meeting memory keeps that protection but reaches a run only through ordinary recall.

post/v1/admin/memory-items/{item_id}/pin

Request

  • Base URL: https://api.patricia.app (the document declares no server; this is the origin it was published from)
  • URL: https://api.patricia.app/v1/admin/memory-items/{item_id}/pin
  • Auth: HTTP bearer

Path parameters

item_idstring uuid required

Response

Successful Response

idstring uuid required
tenant_idstring uuid required
scope_code'tenant' | 'group' | 'conversation' | 'actor' required
scope_refstring nullable
kind_code'fact' | 'preference' | 'entity' | 'event' | 'lesson' | 'summary' required
contentstring required
saliencenumber required
hit_countinteger required
last_used_atstring date-time nullable
expires_atstring date-time nullable
pruned_atstring date-time nullable
pinnedboolean required
protectedboolean
sourcestring required
created_atstring date-time required
updated_atstring date-time required

Changes

No recorded changes to this operation across all 1 revision of this API.