Project Hub

The Project Hub is MeetLoyd's enterprise project command center. It brings together agents, teams, handoffs, workflows, processes, and human stakeholders into a single orchestration entity with formal governance, budget tracking, and a rich visual dashboard.

Why Projects?

In an enterprise setting, work rarely stays within a single team. A product launch might involve Marketing agents for campaign creation, Sales agents for outreach, Legal agents for compliance review, and Engineering agents for feature builds — each from different apps and teams.

Projects solve this by acting as the connective layer across your agent workforce:

Cross-team orchestration — Bring together agents and teams from multiple apps
RACI governance — Assign human stakeholders with formal accountability roles
Unified dashboard — See tasks, handoffs, workflows, and processes in one view
Budget control — Track spending across teams with category-level limits
Identity scoping — Project-scoped SPIFFE identities for agent authentication
Shared workspace — Auto-provision Google Drive or SharePoint for collaboration

Creating a Project

Navigate to Openspace and click New Project. You'll need:

Name and slug (URL-friendly identifier)
Goal — What this project aims to achieve
Apps — Which apps participate (SLIM auto-enables for 2+ apps)
Teams — Which teams are involved
Budget (optional) — Total budget with currency

Projects start in planning status. Add teams, agents, and members before transitioning to active.

Project Lifecycle

Planning → Active → Completed
              ↕
           Paused → Cancelled

Status	Description
Planning	Initial setup. Add teams, agents, milestones, members.
Active	Work in progress. All subsystems active.
Paused	Temporarily halted. Agents stop receiving project tasks.
Completed	Successfully finished. Read-only archive.
Cancelled	Terminated early. Read-only archive.

The 9-Tab Dashboard

When you open a project, you see a tabbed command center:

Dashboard (Tab 0)

The landing tab shows aggregated metrics at a glance:

Task metrics — Total, open, completed, overdue counts
Budget gauge — Visual utilization with color coding (green/yellow/red)
Activity feed — Recent project events (who did what, when)
Subsystem summaries — Handoff rules, active workflows, running processes

Board (Tab 1)

A drag-and-drop Kanban board with five columns:

Column	Task Status
Backlog	Pending
Todo	Pending Approval
In Progress	Running
Review	Under Review
Done	Completed

Drag cards between columns to update task status. Cards show assignee, priority, and deadline. Overdue tasks are highlighted in red.

Search tasks by name or description using the filter bar.

Milestones (Tab 2)

Track project milestones with:

Due dates and progress indicators
Deliverables checklist
Approval workflows (designated approver required)
Budget allocation per milestone
Dependency tracking between milestones

Processes (Tab 3)

View process definitions and active instances scoped to this project:

Segmented progress bars showing completed/current/pending phases
Status indicators (running, completed, failed)
Direct links to process details

Workflows (Tab 4)

See all workflow definitions associated with this project:

Workflow status (draft, active, paused)
Node count and version info
Quick visual cards for each workflow

Handoffs (Tab 5)

Monitor handoff rules and their execution history:

Rules table showing from/to agents, conditions, and trigger counts
Recent execution log with success/failure indicators
Agent flow visualization

Workspace (Tab 6)

Provision and manage a shared workspace for the project:

Google Shared Drive or SharePoint site auto-provisioning
Standard folder structure (Reports, Working, Shared, Archive)
Direct links to cloud workspace and folders
Role-based access (project lead gets organizer/owner role)

Click Provision Shared Workspace to create the workspace. Requires a Google Workspace or Microsoft 365 integration.

Members (Tab 7)

The RACI matrix assigns human stakeholders to the project with formal governance roles:

Role	Code	Responsibility
Responsible	R	Does the work — executes tasks
Accountable	A	Approves outcomes — ultimate decision maker
Consulted	C	Provides input — domain expertise
Informed	I	Kept in the loop — receives updates

Click a role chip to cycle through R → A → C → I. Add members with the Add Member button.

RACI roles drive notifications:

R receives task assignments and deadline reminders
A receives approval requests with approve/reject actions
C receives consultation requests with deep-links to threads
I receives FYI notifications for milestone and status changes

Settings (Tab 8)

Read-only view of project configuration:

General — Name, status, description, goal, dates
Budget — Total, spent, currency, spending policy
Autonomy — Mode (autonomous/supervised/manual) with explanation
SLIM — Cross-app communication status, connected organizations
Identity — Project's SPIFFE ID for agent authentication

Cross-App Communication (SLIM)

When a project spans 2 or more apps, SLIM (Secure Lightweight Inter-app Messaging) is automatically enabled. This creates a virtual team that allows agents from different apps to communicate securely within the project context.

Agent Identity

Each project gets a SPIFFE identity in the MeetLoyd trust domain:

spiffe://meetloyd.com/tenant/{tenantId}/project/{projectId}

Agents participating in the project receive project-scoped SPIFFE IDs:

spiffe://meetloyd.com/tenant/{tenantId}/project/{projectId}/agent/{agentId}

These identities enable:

Agent-to-agent authentication within the project
Token exchange for cross-service access
Tool-based access control scoped to project resources
Verifiable Credentials with project context badges

API Reference

All project endpoints are under /api/v1/projects.

Sub-Resources

# Tasks
GET    /projects/:id/tasks
POST   /projects/:id/tasks
GET    /projects/:id/tasks/summary

# Handoffs
GET    /projects/:id/handoffs
POST   /projects/:id/handoffs
GET    /projects/:id/handoffs/logs

# Workflows
GET    /projects/:id/workflows
POST   /projects/:id/workflows

# Processes
GET    /projects/:id/processes
GET    /projects/:id/processes/instances

# Members (RACI)
GET    /projects/:id/members
POST   /projects/:id/members
PATCH  /projects/:id/members/:userId
DELETE /projects/:id/members/:userId

# Workspace
GET    /projects/:id/workspace
POST   /projects/:id/workspace/provision

# Dashboard
GET    /projects/:id/dashboard

Create Task Example

curl -X POST /api/v1/projects/proj_abc123/tasks \
  -H "Authorization: Bearer ..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Review compliance report",
    "priority": "high",
    "assignedAgentId": "agent_xyz",
    "deadline": "2026-03-15T00:00:00Z"
  }'

Add RACI Member Example

curl -X POST /api/v1/projects/proj_abc123/members \
  -H "Authorization: Bearer ..." \
  -H "Content-Type: application/json" \
  -d '{
    "userId": "user_johndoe",
    "role": "accountable",
    "title": "Executive Sponsor"
  }'

Authorization

Project access is controlled via OpenFGA with the following permission model:

Permission	Who Can
`can_read`	Viewers, members, managers, owners
`can_write`	Members, managers, owners
`can_manage`	Managers, owners
`can_approve`	Managers, owners

Write operations (creating tasks, adding members, provisioning workspaces) require the teams:write permission scope.

Why Projects?​

Creating a Project​

Project Lifecycle​

The 9-Tab Dashboard​

Dashboard (Tab 0)​

Board (Tab 1)​

Milestones (Tab 2)​

Processes (Tab 3)​

Workflows (Tab 4)​

Handoffs (Tab 5)​

Workspace (Tab 6)​

Members (Tab 7)​

Settings (Tab 8)​

Cross-App Communication (SLIM)​

Agent Identity​

API Reference​

Sub-Resources​

Create Task Example​

Add RACI Member Example​

Authorization​