Projects — CCJV Core

The job. Deliver the work the organisation has taken on, with dates and owners that hold up under load.

How the work runs. A project holds tasks with due dates, milestones, subtasks, and dependencies — a task can wait on another, so the order of work is explicit. Assignees are picked from the HRM roster. The board shows the state of play; the Command Center pulls overdue and unowned work out of the list and puts it in front of you. Projects arrive from two directions: created directly, or converted from a won CRM deal with its context intact.

What it produces. A task board that reflects reality, milestone progress, and an exceptions list (overdue, unowned) that does not need to be hunted for.

Who works in it. The owner, project leads, and the seats doing the work.

Requirement. 1 CJV/month, held — not spent. Screen: /core-projects/

Proven today. Tasks, due dates, milestones, subtasks, dependencies, board view, HRM-picker assignment, CRM conversion intake. In build (D6). A close-out flow (review → close with Vault evidence) and a status report (milestone %, overdue tasks) generated from live state.

Next action. Connect Wallet → /erp-launcher/ → activate Projects.