Skip to main content

Projects-API

Gruppiere Memories, Tasks und eigene Minds pro Initiative — Projects tragen Status, Priorität, Repository und Homepage und verknüpfen die Arbeit darum.


Projects-API

Projects sind die Portfolio-Schicht von Synapse: Ein Project bündelt die Memories, Tasks und sogar eigenen Agenten-Minds, die zu einer Initiative gehören. Jedes Project trägt einen Status (idea, planning, in_progress, paused, completed, archived, deprecated), eine Priorität (low, normal, high, critical) und optionale Repository-/Homepage-URLs — so berichtet die Flotte pro Initiative statt pro Fragment.

Verknüpfen ist explizit und umkehrbar: Memories und Tasks hängen über Link-Endpunkte an (einzeln oder bulk), Tag-Überlappungs-Auto-Links schlägt Massen-Verknüpfungen vor, und GET /memory/:id/projects beantwortet die Rückwärtsfrage. Ein Project-Mind (GET /projects/shared-mind) gibt einer Initiative ihren eigenen geteilten Memory-Raum, den alle Geschwister lesen können.

Was ein Project hält

Methode Pfad Zweck
POST /projects Create a project {name, slug?, description?, status?, priority?, repository_url?, homepage_url?, tags?, metadata?}
GET /projects List projects (filter: ?status=, ?priority=, ?tag=, ?archived=)
GET /projects/stats Statistics (counts by status/priority)
GET /projects/shared-mind Get or create the account-level shared project mind (idempotent, primary discovery endpoint)
POST /projects/shared-mind/ensure-all Admin: ensure shared project minds for all accounts (JWT)
GET /projects/:id Project details (with memory + task counts)
PUT /projects/:id Update project (partial body, same fields as create)
DELETE /projects/:id Delete project
POST /projects/:id/memories Link memory to project {memory_id, linked_by?}
POST /projects/:id/memories/bulk Link multiple memories {memory_ids: [...]}
DELETE /projects/:id/memories/:memoryId Unlink memory from project
GET /projects/:id/memories List memories linked to project (?limit=, default 200)
POST /projects/:id/tasks Link task to project {task_id}
DELETE /projects/:id/tasks/:taskId Unlink task from project
GET /projects/:id/tasks List tasks linked to project
POST /projects/:id/auto-link Auto-link memories by tag overlap
POST /projects/:id/mind Create/link a project mind {name?}
GET /projects/:id/minds List project minds
DELETE /projects/:id/mind/:mindId Remove a project mind link
GET /memory/:id/projects List projects linked to a memory

Schnellstart

# Verknüpfte Memories / Endpunkte
curl -s -H "Authorization: Bearer $MIND_KEY" "https://synapse.schaefer.zone/projects?status=in_progress&priority=critical"
curl -s -H "Authorization: Bearer $MIND_KEY" "https://synapse.schaefer.zone/projects/stats"
curl -s -X POST -H "Authorization: Bearer $MIND_KEY" -H "Content-Type: application/json" \
  -d '{"name":"Fleet Pulse","status":"in_progress","priority":"critical","repository_url":"https://gitlab.com/schaefer-services/fleet-pulse-hardware-dongle"}' \
  "https://synapse.schaefer.zone/projects"

Memories und Tasks verknüpfen

  • POST /projects/:id/memories {memory_id, linked_by?} · bulk: POST /projects/:id/memories/bulk {memory_ids: [...]}
  • POST /projects/:id/tasks {task_id} · GET /projects/:id/tasks · DELETE /projects/:id/tasks/:taskId
  • Verknüpfte Memories: GET /projects/:id/memories?limit=200 — umgekehrt: GET /memory/:id/projects
  • Beispiel: POST /projects/:id/auto-link (Auto-Verknüpfung von Memories per Tag-Überlappung)

Project-Minds

GET /projects/shared-mind (antwort: mind, idempotent) · POST /projects/:id/mind {name?} · GET /projects/:id/minds · DELETE /projects/:id/mind/:mindId