Skip to content

Feat/services v2 #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
leonprou wants to merge 22 commits into
base: main
Choose a base branch
from
Open

Feat/services v2 #67

Show file tree
Hide file tree
Changes from 10 commits
Commits
Show all changes
22 commits
Select commit Hold shift + click to select a range
53def05
addibg ServiceSchema
leonprou Aug 26, 2025
dbb0545
updating spec with service-v2
leonprou Aug 26, 2025
a15b374
expand tasks
leonprou Aug 26, 2025
de30b73
Services SDK draft
leonprou Aug 27, 2025
d3485a9
select categories
leonprou Aug 27, 2025
40d80fe
update registerService
leonprou Aug 27, 2025
1efa228
update some names
leonprou Aug 27, 2025
028d498
refactor service record
leonprou Aug 27, 2025
5c70d29
update PRD
leonprou Aug 27, 2025
1e02a79
ServiceRecord refactor
leonprou Aug 27, 2025
af555ed
fixing tests
leonprou Aug 27, 2025
e169451
move timestamps off chain
leonprou Aug 27, 2025
4ec5ca9
Update the Services contract
leonprou Aug 28, 2025
d8e4412
removing the proposals
leonprou Aug 28, 2025
d32c304
updating tests
leonprou Aug 28, 2025
29b3707
Agent Registry fixes and test updates
leonprou Aug 28, 2025
ffc6e81
Agent Registry fixes and test updates
leonprou Aug 28, 2025
746072d
make sure user can rate agent once
leonprou Aug 28, 2025
12d51f8
Adding contracts tests
leonprou Aug 28, 2025
c082cb5
phase2 tests
leonprou Aug 28, 2025
aadfbd9
Updating Service SDK and tests
leonprou Aug 28, 2025
76921eb
deleting legacy methods
leonprou Aug 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
95 changes: 90 additions & 5 deletions .taskmaster/docs/prd.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,35 @@ Transform AI agents from passive tools into active economic participants capable

### 1. Registry Systems

#### Service Registry
- **REQ-1.1**: Maintain an open catalog of available services
- **REQ-1.2**: Support service metadata, pricing, and capability definitions
- **REQ-1.3**: Enable community-driven service additions (future)
- **REQ-1.4**: Provide service discovery and filtering mechanisms
#### Service Registry V2
- **REQ-1.1**: Maintain an open catalog of available services with full lifecycle management
- **REQ-1.2**: Implement hybrid on-chain/off-chain architecture for optimal gas efficiency:
- **On-chain data** (stored in ServiceRegistry contract):
- Service ID (auto-increment from blockchain)
- Service name (for basic discovery)
- Owner address (service creator/maintainer)
- Agent address (assigned executor, optional)
- Service URI (IPFS hash for metadata storage)
- Status (draft, published, archived, deleted)
- Version number (for cache invalidation)
- Creation and update timestamps
- **Off-chain metadata** (stored in IPFS):
- Service description and detailed information
- Category and tags for discovery
- Technical specifications (endpoint URLs, HTTP methods, parameter/result schemas)
- Business configurations (pricing models, rate limits)
- Operational status from monitoring systems
- **REQ-1.3**: Enable service-agent assignment model:
- Services can be created independently without agent assignment
- Services can be assigned/unassigned to agents dynamically
- Unassigned services remain inactive but preserved
- Support for service transfer between agents
- Published services must have an agent assigned (enforced by schema validation)
- **REQ-1.4**: Provide advanced service discovery and filtering:
- On-chain filtering by owner, agent, name, status
- Off-chain filtering by category, pricing, detailed specifications
- Hybrid queries combining blockchain and IPFS data
- Search unassigned services for marketplace discovery

#### Agent Registry
- **REQ-1.5**: Allow agents to self-register with metadata and capabilities
Expand Down Expand Up @@ -126,6 +150,67 @@ Transform AI agents from passive tools into active economic participants capable
- Validation: Property-specific validation using Zod schemas
- Use case: Targeted updates like status changes, adding attributes, or updating social links

- **REQ-4.1.2**: Provide comprehensive service registry integration APIs
- **ServiceRegistryService.registerService(params)**: Register new service with IPFS metadata storage
- Parameters: RegisterServiceParams with name, agentAddress (optional), metadata object
- Metadata includes: description, category, endpointSchema, method, parametersSchema, resultSchema, tags, pricing
- Returns: Promise<ServiceRecord> with complete service data (on-chain + off-chain combined)
- Features: Automatic IPFS upload, blockchain registration, Zod validation
- Process: Upload metadata to IPFS → Register minimal data on-chain → Return combined ServiceRecord

- **ServiceRegistryService.getService(serviceId)**: Get complete service record
- Returns: ServiceRecord combining on-chain data with IPFS metadata
- Includes: All service fields flattened for ease of use
- Handles: IPFS metadata fetching and merging with blockchain data

- **ServiceRegistryService.updateService(serviceId, updates)**: Update service with flexible parameters
- Parameters: serviceId (string), UpdateServiceParams with optional on-chain and metadata fields
- On-chain updates: name, agentAddress, status
- Off-chain updates: metadata object with any combination of description, category, technical specs, pricing
- Returns: Promise<ServiceRecord> with updated combined data
- Features: Selective IPFS updates, version management, ownership validation

- **ServiceRegistryService.getAllServices(filters)**: Query services with advanced filtering
- Filter parameters: category, status, owner, agent, pricing model
- Returns: Array of ServiceRecord objects matching criteria
- Supports: Pagination, sorting, hybrid on-chain/off-chain filtering

- **ServiceRegistryService.activateService(serviceId)**: Change service status to published
- Validation: Ensures agent is assigned before activation
- Updates: On-chain status and version increment
- Returns: Promise<ServiceRecord> with updated status

- **REQ-4.1.3**: Service schema architecture and validation system
- **Three-Schema Architecture**: Clear separation of concerns for optimal performance
- ServiceOnChainSchema: Minimal blockchain data (8 fields)
- ServiceMetadataSchema: Rich IPFS metadata (9+ fields including operational status)
- ServiceRecordSchema: Complete combined view for SDK users

- **Service Status Lifecycle**: Simplified 4-state model aligned with business needs
- draft: Service being configured, not ready for use
- published: Service available for discovery and execution
- archived: Service deprecated but preserved for history
- deleted: Service removed (soft delete for data integrity)

- **Comprehensive Validation**: Zod-based validation with enhanced error reporting
- validateServiceRecord(): Complete service validation
- validateServiceOnChain(): On-chain data validation
- validateServiceMetadata(): IPFS metadata validation
- validateRegisterServiceParams(): Registration parameter validation
- validateUpdateServiceParams(): Update parameter validation with partial updates

- **Type Safety and Developer Experience**: Full TypeScript support
- ServiceRecord: Primary type for SDK consumers
- ServiceOnChain: Blockchain data type
- ServiceMetadata: IPFS metadata type
- RegisterServiceParams: Registration input type
- UpdateServiceParams: Update input type with flexible partial updates

- **Backward Compatibility**: Legacy aliases and migration support
- Service type alias → ServiceRecord
- Deprecated function aliases with clear migration path
- Gradual migration strategy for existing integrations

- **REQ-4.2**: Support task discovery and proposal submission
- **REQ-4.3**: Enable real-time task notifications
- **REQ-4.4**: Provide payment and reputation management tools
Expand Down
71 changes: 70 additions & 1 deletion .taskmaster/tasks/tasks.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -331,11 +331,80 @@
],
"priority": "high",
"subtasks": []
},
{
"id": 25,
"title": "SDK: Implement Service Management System V2 with comprehensive CRUD operations, ownership model, and agent assignment capabilities",
"description": "Implement a comprehensive Service Management System V2 in the TypeScript SDK with full CRUD operations, ownership model, agent assignment capabilities, hybrid storage (on-chain + IPFS), and advanced discovery/filtering as specified in the PRD.",
"details": "1. ServiceRegistryService Enhancement:\n - Extend existing ServiceRegistryService class with V2 capabilities\n - Implement comprehensive CRUD operations: createService(), updateService(), deleteService(), getService(), listServices()\n - Add ownership model with transferOwnership(), getServiceOwner(), and ownership validation\n - Implement agent assignment/unassignment: assignAgent(), unassignAgent(), getAssignedAgents(), getServicesByAgent()\n - Add service lifecycle management with status tracking (draft, active, paused, archived, deleted)\n\n2. ServiceSchema Integration:\n - Create comprehensive ServiceSchema interface with required fields: id, name, description, category, owner, status, createdAt, updatedAt\n - Add optional fields: tags, metadata, pricing, requirements, capabilities, assignedAgents\n - Implement Zod validation schemas for all service operations\n - Support nested schema validation for complex service configurations\n\n3. Smart Contract Updates:\n - Extend ServiceRegistry.sol with V2 functionality including ownership transfers, agent assignments, and enhanced metadata\n - Implement hybrid storage pattern: core data on-chain (id, owner, status, assignedAgents) and metadata on IPFS\n - Add events for ServiceCreated, ServiceUpdated, ServiceDeleted, AgentAssigned, AgentUnassigned, OwnershipTransferred\n - Implement access control with onlyOwner modifiers and agent assignment permissions\n\n4. Hybrid Storage Implementation:\n - Integrate IPFS client for metadata storage using ipfs-http-client\n - Implement automatic IPFS pinning for service metadata and large data objects\n - Create metadata synchronization between on-chain references and IPFS content\n - Add content addressing and integrity verification for IPFS stored data\n\n5. Advanced Discovery and Filtering:\n - Implement advanced search with filters: category, status, owner, assignedAgent, tags, dateRange\n - Add pagination support with cursor-based navigation for large result sets\n - Implement sorting options: createdAt, updatedAt, name, category, status\n - Create full-text search capabilities for service names and descriptions\n - Add geolocation-based filtering if location metadata is available\n\n6. CLI Service Commands Integration:\n - Create 'ensemble services' command group with subcommands: create, list, get, update, delete, assign, unassign, transfer\n - Implement service-record.yaml configuration file support similar to agent-record.yaml\n - Add interactive service creation wizard with step-by-step guidance\n - Support bulk operations for service management and agent assignments",
"testStrategy": "1. Unit Testing:\n - Test all ServiceRegistryService methods with mocked blockchain interactions and IPFS operations\n - Validate ServiceSchema Zod validation with valid and invalid service data structures\n - Test ownership model operations including transfers and permission checks\n - Verify agent assignment/unassignment logic with various scenarios (single/multiple agents)\n - Test hybrid storage operations with mocked IPFS client responses\n\n2. Integration Testing:\n - Deploy updated smart contracts to testnet and test all V2 functionality end-to-end\n - Test IPFS integration with real IPFS nodes and verify metadata storage/retrieval\n - Validate service lifecycle management across different status transitions\n - Test advanced discovery and filtering with large datasets (1000+ services)\n - Verify CLI commands integration with real SDK operations\n\n3. Performance Testing:\n - Benchmark service creation/update operations with large metadata objects\n - Test pagination performance with datasets of varying sizes (100, 1K, 10K services)\n - Measure IPFS upload/download times for different metadata sizes\n - Test concurrent agent assignment operations and verify data consistency\n\n4. Security Testing:\n - Verify ownership validation prevents unauthorized service modifications\n - Test agent assignment permissions and access control mechanisms\n - Validate IPFS content integrity and prevent metadata tampering\n - Test smart contract upgrade scenarios and data migration safety\n\n5. End-to-End Testing:\n - Create complete service management workflows from CLI to blockchain\n - Test service discovery through various filtering combinations\n - Verify ownership transfers maintain data integrity and agent assignments\n - Test service deletion and cleanup of associated IPFS metadata",
"status": "pending",
"dependencies": [
1,
3,
21
],
"priority": "medium",
"subtasks": [
{
"id": 1,
"title": "Extend ServiceRegistryService with V2 CRUD Operations and Ownership Model",
"description": "Enhance the existing ServiceRegistryService class with comprehensive CRUD operations, ownership model, and service lifecycle management capabilities.",
"dependencies": [],
"details": "Extend the ServiceRegistryService class to include: createService(), updateService(), deleteService(), getService(), listServices() methods with proper error handling and validation. Implement ownership model with transferOwnership(), getServiceOwner(), and ownership validation methods. Add service lifecycle management with status tracking (draft, active, paused, archived, deleted). Include proper TypeScript interfaces and error handling for all operations. Ensure backward compatibility with existing service registry functionality.",
"status": "done",
"testStrategy": "Unit tests for all CRUD operations with mocked blockchain interactions. Test ownership model operations including transfers and permission checks. Validate service lifecycle state transitions and status management."
Comment on lines +349 to +356

@coderabbitai coderabbitai Bot Aug 28, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

ServiceRegistry CRUD operations marked as done

Subtask 25.1 status shows "done" for the V2 CRUD operations and ownership model. Based on the code review, these are indeed implemented in ServiceRegistryService.ts.

🏁 Script executed:

#!/bin/bash
# Verify all CRUD methods are implemented in ServiceRegistryService
ast-grep --pattern 'async $METHOD($$$): Promise<$_> {
  $$$
}' packages/sdk/src/services/ServiceRegistryService.ts | grep -E "(createService|updateService|deleteService|getService|listServices|transferOwnership|getServiceOwner)"

Length of output: 230

🏁 Script executed:

#!/bin/bash
# Locate the ServiceRegistryService class file
echo "Finding ServiceRegistryService definition..."
rg -nP 'class\s+ServiceRegistryService\b' -g '*.ts'

# Search for CRUD and ownership method definitions across TS files
echo "Checking for method implementations..."
rg -nP '^(?:\s*(?:public|private|protected)\s+)?(?:async\s+)?(?:static\s+)?(createService|updateService|deleteService|getService|listServices|transferOwnership|getServiceOwner)\s*\(' -n -g '*.ts'

Length of output: 530

🏁 Script executed:

#!/bin/bash
# Search for CRUD and ownership method names within ServiceRegistryService.ts
file="packages/sdk/src/services/ServiceRegistryService.ts"
echo "Searching in $file..."
rg -n 'createService' "$file"
rg -n 'updateService' "$file"
rg -n 'deleteService' "$file"
rg -n 'getService\(' "$file"
rg -n 'listServices' "$file"
rg -n 'transferOwnership' "$file"
rg -n 'getServiceOwner' "$file"

Length of output: 1759

Implement missing ServiceRegistryService V2 methods

  • ServiceRegistryService.ts (packages/sdk/src/services/ServiceRegistryService.ts) is missing createService(...) and transferOwnership(...) implementations.
  • listServices(...) currently only logs “not yet fully implemented” – replace the placeholder warning with full V2 logic.
🤖 Prompt for AI Agents 
In .taskmaster/tasks/tasks.json around lines 349 to 356, the task entry
documents that packages/sdk/src/services/ServiceRegistryService.ts is missing
implementations for createService(...) and transferOwnership(...), and
listServices(...) contains only a placeholder log; implement the full V2 logic
by adding createService to validate inputs, construct and persist the new
service entity (including status, owner, metadata, timestamps), integrate with
existing registry/storage and any blockchain call shims with proper error
handling and unit-test hooks; implement transferOwnership to verify permissions,
validate new owner, update ownership atomically, emit events/audit logs and
handle blockchain interactions and rollback on failure; replace the listServices
placeholder with a real V2 listing that supports filters, pagination, status
filtering, and maps storage/chain records to the V2 DTOs; ensure all methods
include TypeScript interfaces, comprehensive error handling,
permission/ownership checks, and unit tests/mocks to match the task's
testStrategy.

},
{
"id": 2,
"title": "Create ServiceSchema Interface and Zod Validation",
"description": "Design and implement comprehensive ServiceSchema interface with required and optional fields, along with Zod validation schemas for all service operations.",
"dependencies": [
"25.1"
],
"details": "Create ServiceSchema interface with required fields: id, name, description, category, owner, status, createdAt, updatedAt. Add optional fields: tags, metadata, pricing, requirements, capabilities, assignedAgents. Implement Zod validation schemas for service creation, updates, and queries. Support nested schema validation for complex service configurations. Create type-safe validation functions that can be used across the SDK. Include proper error messages and validation feedback for invalid schemas.",
"status": "done",
"testStrategy": "Validate ServiceSchema Zod validation with valid and invalid service data structures. Test nested schema validation for complex configurations. Verify type safety and error message clarity."
},
{
"id": 3,
"title": "Update Smart Contracts with V2 Functionality and Hybrid Storage",
"description": "Extend ServiceRegistry.sol smart contract with V2 functionality including ownership transfers, agent assignments, and hybrid storage pattern implementation.",
"dependencies": [
"25.2"
],
"details": "Extend ServiceRegistry.sol with V2 functionality including ownership transfers, agent assignments, and enhanced metadata support. Implement hybrid storage pattern storing core data on-chain (id, owner, status, assignedAgents) and metadata on IPFS. Add events for ServiceCreated, ServiceUpdated, ServiceDeleted, AgentAssigned, AgentUnassigned, OwnershipTransferred. Implement access control with onlyOwner modifiers and agent assignment permissions. Include gas optimization and proper event indexing for efficient querying.",
"status": "pending",
"testStrategy": "Smart contract unit tests for all new functions and access controls. Test hybrid storage pattern with IPFS integration. Verify event emissions and gas optimization. Test ownership transfers and agent assignment permissions."

@coderabbitai coderabbitai Bot Aug 28, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Smart contract V2 functionality still pending

Subtask 25.3 for updating smart contracts with V2 functionality is marked as "pending". This is critical for the full V2 implementation to work correctly.

The ServiceRegistry smart contract needs to be updated to support:

  • ID-based service management
  • Ownership transfers
  • Agent assignments
  • Hybrid storage pattern with IPFS

This is blocking full V2 functionality. The SDK implementation (ServiceRegistryService.ts) has placeholder error messages indicating the smart contract support is missing.

Would you like me to help implement the smart contract updates or create a detailed specification for the required contract methods?

🤖 Prompt for AI Agents 
In .taskmaster/tasks/tasks.json around lines 377-378, Subtask 25.3 is still
marked "pending" because the ServiceRegistry smart contract lacks V2 support
(ID-based service management, ownership transfers, agent assignments, and hybrid
IPFS storage), and the SDK has placeholder errors; update the project by (1)
adding new Solidity functions/events to ServiceRegistry: createService(id,
dataHash), updateService(id, dataHash), transferOwnership(id, newOwner),
assignAgent(id, agent, permissions), revokeAgent(id, agent), and events for
ServiceCreated/Updated/OwnershipTransferred/AgentAssigned; (2) implement hybrid
on-chain/off-chain storage by storing IPFS content hashes on-chain and full
payloads in IPFS, with access control checks in modifiers; (3) write
comprehensive unit tests for these new functions and gas/permission checks; and
(4) remove placeholder errors and implement corresponding methods in
ServiceRegistryService.ts to call the new contract functions and handle
errors/exceptions with proper logging.

},
{
"id": 4,
"title": "Implement Agent Assignment and IPFS Integration",
"description": "Add agent assignment capabilities and integrate IPFS client for metadata storage with automatic pinning and content verification.",
"dependencies": [
"25.3"
],
"details": "Implement agent assignment/unassignment methods: assignAgent(), unassignAgent(), getAssignedAgents(), getServicesByAgent() with proper validation and blockchain integration. Integrate IPFS client using ipfs-http-client for metadata storage. Implement automatic IPFS pinning for service metadata and large data objects. Create metadata synchronization between on-chain references and IPFS content. Add content addressing and integrity verification for IPFS stored data. Include retry logic and error handling for IPFS operations.",
"status": "pending",
"testStrategy": "Test agent assignment operations with ownership validation. Verify IPFS integration with metadata storage and retrieval. Test automatic pinning and content integrity verification. Validate synchronization between on-chain and IPFS data."
},
{
"id": 5,
"title": "Implement Advanced Discovery, Filtering, and CLI Integration",
"description": "Create advanced search and filtering capabilities with pagination, and integrate CLI service commands with interactive wizards and bulk operations.",
"dependencies": [
"25.4"
],
"details": "Implement advanced search with filters: category, status, owner, assignedAgent, tags, dateRange. Add pagination support with cursor-based navigation for large result sets. Implement sorting options: createdAt, updatedAt, name, category, status. Create full-text search capabilities for service names and descriptions. Add geolocation-based filtering if location metadata is available. Create 'ensemble services' command group with subcommands: create, list, get, update, delete, assign, unassign, transfer. Implement service-record.yaml configuration file support. Add interactive service creation wizard and support bulk operations.",
"status": "pending",
"testStrategy": "Test advanced filtering and search functionality with various query combinations. Validate pagination and sorting with large datasets. Test CLI commands with interactive wizards and configuration file parsing. Verify bulk operations and error handling."
}
]
Comment on lines +334 to +402

@coderabbitai coderabbitai Bot Aug 27, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

V2 task block looks comprehensive; add repo-level verification to ensure code parity.

Quickly validate that the SDK actually ships the listed V2 surface (methods, schemas, exports, CLI stubs). Run the script below from repo root.

Consider adding explicit acceptance criteria per subtask (inputs/outputs/preconditions) to tighten traceability from PRD → code → tests.

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== ServiceRegistryService V2 method presence =="
rg -nP --type=ts -C2 '(class\s+ServiceRegistryService\b)|\b(createService|updateService|deleteService|getService|listServices|assignAgent|unassignAgent|getAssignedAgents|getServicesByAgent|transferOwnership)\s*\(' packages | sed 's/^/  /'

echo "== Service V2 schemas and types =="
rg -nP --type=ts -n 'RegisterServiceParamsSchema|ServiceRecordSchema|ServiceMetadataSchema|ServiceOnChainSchema' packages/sdk/src/schemas/service.schemas.ts | sed 's/^/  /'
rg -nP --type=ts -n 'export\s+type\s+(RegisterServiceParams|ServiceRecord|Service\s*=|UpdateServiceParams|ServiceStatus|ServicePricing(Model)?)\b' packages/sdk/src/schemas/service.schemas.ts | sed 's/^/  /'

echo "== Barrel exports include service schemas =="
rg -nP --type=ts -n 'export .* from .*/schemas/service.schemas' packages/sdk/src/index.ts packages/sdk/src/types.ts | sed 's/^/  /'

echo "== New error types referenced by ServiceRegistryService =="
rg -nP --type=ts -n 'Service(NotFound|Ownership|Status|Validation|AgentAssignment)Error' packages | sed 's/^/  /'

echo "== CLI services command surface (if present) =="
rg -nP -n '\b(ensemble\s+services|\bservices\s+(create|list|get|update|delete|assign|unassign|transfer)\b)' packages | sed 's/^/  /'

Length of output: 7700

Missing V2 Surface in SDK — Critical Implementations Required

The repo-level verification shows that several V2 features outlined in .taskmaster/tasks/tasks.json are not yet present in the SDK. Before merging, the following must be added:

• In packages/sdk/src/services/ServiceRegistryService.ts
 – createService(...)
 – assignAgent(...), unassignAgent(...)
 – getAssignedAgents(...)
 – transferOwnership(...)

• Barrel exports (e.g. packages/sdk/src/index.ts or packages/sdk/src/types.ts) must re-export the service schemas and types from schemas/service.schemas.ts.

• Define and throw the new error classes referenced in the V2 spec (e.g. ServiceNotFoundError, ServiceOwnershipError, ServiceStatusError, ServiceValidationError, ServiceAgentAssignmentError).

• Add CLI stubs and command group under ensemble services with the subcommands: create, list, get, update, delete, assign, unassign, transfer.

Optional refactor: consider enriching each subtask with explicit acceptance criteria (inputs, outputs, and preconditions) to strengthen traceability from PRD → code → tests.

🤖 Prompt for AI Agents 
In .taskmaster/tasks/tasks.json around lines 334 to 402, the task outlines V2
SDK work but the SDK is missing the required surface; implement the following:
add createService(), assignAgent(), unassignAgent(), getAssignedAgents(),
transferOwnership() (and related CRUD/status methods if not present) to
packages/sdk/src/services/ServiceRegistryService.ts with proper validation and
error handling; add barrel exports in packages/sdk/src/index.ts (or types.ts) to
re-export service schemas and types from
packages/sdk/src/schemas/service.schemas.ts; create and export the new error
classes ServiceNotFoundError, ServiceOwnershipError, ServiceStatusError,
ServiceValidationError, ServiceAgentAssignmentError in the SDK error module and
update usages; and add CLI command stubs under the ensemble services group with
subcommands create, list, get, update, delete, assign, unassign, transfer so the
commands wire to the new service methods.

}
],
"metadata": {
"created": "2025-07-20T10:42:18.955Z",
"updated": "2025-08-22T06:26:14.340Z",
"updated": "2025-08-26T14:18:39.372Z",
"description": "Tasks for master context"
}
}
Expand Down
9 changes: 8 additions & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,4 +171,11 @@ task-master add-task # DON'T DO THIS
# ✅ CORRECT - Always work from project root for tasks
cd /Users/leon/workspace/ensemble/ensemble-framework
task-master add-task --prompt="CLI: Add new command for..."
```
```

## Project Documentation

### PRD File Location
The Project Requirements Document (PRD) is located at: `.taskmaster/docs/prd.txt`

When updating project specifications, features, or requirements, update the PRD file to maintain alignment between implementation and documentation.
Loading
Loading