mirror of
https://github.com/trustgraph-ai/trustgraph.git
synced 2026-04-25 00:16:23 +02:00
Introduces `workspace` as the isolation boundary for config, flows,
library, and knowledge data. Removes `user` as a schema-level field
throughout the code, API specs, and tests; workspace provides the
same separation more cleanly at the trusted flow.workspace layer
rather than through client-supplied message fields.
Design
------
- IAM tech spec (docs/tech-specs/iam.md) documents current state,
proposed auth/access model, and migration direction.
- Data ownership model (docs/tech-specs/data-ownership-model.md)
captures the workspace/collection/flow hierarchy.
Schema + messaging
------------------
- Drop `user` field from AgentRequest/Step, GraphRagQuery,
DocumentRagQuery, Triples/Graph/Document/Row EmbeddingsRequest,
Sparql/Rows/Structured QueryRequest, ToolServiceRequest.
- Keep collection/workspace routing via flow.workspace at the
service layer.
- Translators updated to not serialise/deserialise user.
API specs
---------
- OpenAPI schemas and path examples cleaned of user fields.
- Websocket async-api messages updated.
- Removed the unused parameters/User.yaml.
Services + base
---------------
- Librarian, collection manager, knowledge, config: all operations
scoped by workspace. Config client API takes workspace as first
positional arg.
- `flow.workspace` set at flow start time by the infrastructure;
no longer pass-through from clients.
- Tool service drops user-personalisation passthrough.
CLI + SDK
---------
- tg-init-workspace and workspace-aware import/export.
- All tg-* commands drop user args; accept --workspace.
- Python API/SDK (flow, socket_client, async_*, explainability,
library) drop user kwargs from every method signature.
MCP server
----------
- All tool endpoints drop user parameters; socket_manager no longer
keyed per user.
Flow service
------------
- Closure-based topic cleanup on flow stop: only delete topics
whose blueprint template was parameterised AND no remaining
live flow (across all workspaces) still resolves to that topic.
Three scopes fall out naturally from template analysis:
* {id} -> per-flow, deleted on stop
* {blueprint} -> per-blueprint, kept while any flow of the
same blueprint exists
* {workspace} -> per-workspace, kept while any flow in the
workspace exists
* literal -> global, never deleted (e.g. tg.request.librarian)
Fixes a bug where stopping a flow silently destroyed the global
librarian exchange, wedging all library operations until manual
restart.
RabbitMQ backend
----------------
- heartbeat=60, blocked_connection_timeout=300. Catches silently
dead connections (broker restart, orphaned channels, network
partitions) within ~2 heartbeat windows, so the consumer
reconnects and re-binds its queue rather than sitting forever
on a zombie connection.
Tests
-----
- Full test refresh: unit, integration, contract, provenance.
- Dropped user-field assertions and constructor kwargs across
~100 test files.
- Renamed user-collection isolation tests to workspace-collection.
53 lines
1.4 KiB
YAML
53 lines
1.4 KiB
YAML
type: object
|
|
description: |
|
|
Collection management request.
|
|
|
|
Operations: list-collections, update-collection, delete-collection
|
|
required:
|
|
- operation
|
|
properties:
|
|
operation:
|
|
type: string
|
|
enum:
|
|
- list-collections
|
|
- update-collection
|
|
- delete-collection
|
|
description: |
|
|
Collection operation:
|
|
- `list-collections`: List collections in workspace
|
|
- `update-collection`: Create or update collection metadata
|
|
- `delete-collection`: Delete collection
|
|
collection:
|
|
type: string
|
|
description: Collection identifier (for update, delete)
|
|
example: research
|
|
timestamp:
|
|
type: string
|
|
description: ISO timestamp
|
|
format: date-time
|
|
example: "2024-01-15T10:30:00Z"
|
|
name:
|
|
type: string
|
|
description: Human-readable collection name (for update)
|
|
example: Research Papers
|
|
description:
|
|
type: string
|
|
description: Collection description (for update)
|
|
example: Academic research papers on AI and ML
|
|
tags:
|
|
type: array
|
|
description: Collection tags for organization (for update)
|
|
items:
|
|
type: string
|
|
example: ["research", "AI", "academic"]
|
|
tag-filter:
|
|
type: array
|
|
description: Filter collections by tags (for list)
|
|
items:
|
|
type: string
|
|
example: ["research"]
|
|
limit:
|
|
type: integer
|
|
description: Maximum number of results (for list)
|
|
default: 0
|
|
example: 100
|