Collections

Creating and managing collections -- the permission boundaries of the Arke network.

Overview

Collections are the fundamental permission boundary in Arke. Every entity belongs to at least one collection, and a user's role in the collection determines what they can do with entities inside it.

Creating a Collection

POST /collections
{
  "properties": {
    "name": "My Research",
    "description": "Collected research materials"
  }
}

The creating user automatically becomes the owner.

Managing Roles

Add a user to a collection:

POST /collections/:id/members
{
  "user_id": "01JUSER...",
  "role": "editor"
}

Available Roles

Role	View	Edit	Create	Delete	Manage
`viewer`	Yes	-	-	-	-
`editor`	Yes	Yes	Yes	-	-
`admin`	Yes	Yes	Yes	Yes	Partial
`owner`	Yes	Yes	Yes	Yes	Yes

Listing Collection Contents

GET /entities?collection_id=01JCOL...
Authorization: Bearer <token>

Public vs Private

Collections can be public (discoverable by anyone on the network) or private (visible only to members). This is controlled through collection properties.