Projects

A project is a logical container for participant data. It can represent a business process, enterprise project, customer workflow, regional operation, or another domain-specific boundary.

Responsibilities

Projects provide:

• routing context for resolve requests
• ownership boundaries for project owners
• grouping for participants, labels, metadata, and resolve history
• authorization scope for project reads and per-project management

Admins can manage all projects. Project owners can manage projects where they are assigned as owners.

Lifecycle Status

Each project has a status:

• draft: visible to admins and project owners only; excluded from Resolve.
• test: visible to admins and project owners only; can be resolved only with explicit project_id and mode: "test".
• live: visible according to read_access_mode and included in normal Resolve.
• archived: visible to admins and project owners only; excluded from Resolve.

Archiving is reversible by updating status. Deleting a project is separate and removes it from active use.

Read Access

Each project has a read_access_mode:

• authenticated_users: active authenticated users can read a live project, read participants and participant associations, inspect participant-scoped delegations, and include the project in Resolve.
• selected_members: only admins and project members can read and resolve a live project.

Project membership has two roles. owner can manage the project. member is read-only and exists for selected project access.

Naming

Use names that describe the workflow or operating context:

• Helios Vendor Renewal
• Nova Supplier Onboarding Review
• EMEA Revenue Operations

Project names can help the resolver distinguish similar participants across different workflows.

REST and MCP Surfaces

Projects are available through:

• REST: /api/v1/projects
• MCP: list_projects, get_project, create_project, update_project, delete_project
• Platform: project list and project management views