List current Artifact heads
List current heads for one readable Artifact family.
Authorization
BearerAuth Bearer credential resolved to an opaque authenticated Principal by the Server deployment.
In: header
Path Parameters
.*\S.*1 <= length <= 256Value in
- "memory"
- "atomic-memory"
- "experience"
- "skill"
- "handoff"
- "profile"
- "prompt"
- "topic-memory"
Query Parameters
1 <= items <= 16Value in
- "all"
- "any"
1 <= value <= 100501 <= length <= 4096Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/scopes/string/artifacts/memory"{ "items": [ { "scope_id": "string", "family": "memory", "artifact_id": "string", "revision": 1, "sources": [ { "source_type": "string", "source_id": "string" } ], "artifacts": [ { "family": "string", "artifact_id": "string", "revision": 1 } ], "content_digest": "string", "title": "string", "summary": "string", "published_at": "2019-08-24T14:15:22Z", "source_count": 0, "created_at": "2019-08-24T14:15:22Z", "created_by": { "type": "user", "id": "string", "description": "string" }, "restored_from_revision": 1, "reason": "string" } ], "next_cursor": "string"}Create an Artifact POST
Dispatch the family-specific creation command through the owning Family writer and atomically create revision one, its derived Family state, and its system provenance Source. Handoff is the Scope singleton: Create returns 409 when it already exists and callers must use Replace to update it. Creating a Prompt requires scope.admin because its configuration affects the whole Scope; other families require scope.contribute. Topic Memory accepts complete title, summary, and detail text without semantic generation; its active head, chunks, and configured retrieval indexes are committed atomically.
Resolve a stable Artifact handle GET
Resolve one scope-local handle to the exact immutable Artifact revision it names.

